Thank you Alex!
On Tue, May 27, 2014 at 7:23 AM, Alex Crichton <a...@crichton.co> wrote: > The test runner captures stdout by default and prints it at the end of > the test run, but only if the test failed. This is intended to turn > down the noise of successful tests, especially the failing ones. > > If you pass the --nocapture option to the test binary, it will disable > this behavior and println will print to the terminal by default. > > On Mon, May 26, 2014 at 10:21 PM, Urban Hafner <cont...@urbanhafner.com> > wrote: > > Hey everyone, > > > > still me, the Rust newbie ;) > > > > Coming from Ruby I use TDD quite heavily. For my toy rust project I've > setup > > my Makefile in such a way that it first compiles and runs a test build > > before compiling the real executable. When trying to debug a failing > test I > > tried putting println! statements into the code under test. Apart from > the > > fact that I should probably start using a debugger instead I'd like to > know > > why the output doesn't show up. Does the test runner swallow it? Is > there a > > way to write to stdout or stderr during the test runs? > > > > Urban > > -- > > Freelancer > > > > Available for hire for Ruby, Ruby on Rails, and JavaScript projects > > > > More at http://urbanhafner.com > > > > _______________________________________________ > > Rust-dev mailing list > > Rust-dev@mozilla.org > > https://mail.mozilla.org/listinfo/rust-dev > > > -- Freelancer Available for hire for Ruby, Ruby on Rails, and JavaScript projects More at http://urbanhafner.com
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
