Greetings, We run our tests mainly through the command line locally, and solely from the command line on the build machine. We output our reports in text format verbosity normal.
Recently we happened upon a situation where some of our tests weren't running on the build machine. I was finally able to reproduce the problem, and while ultimately it boiled down to a development issue it was confusing how MbUnit handled this situation. In the Test Fixture setup we had some code that was hard coded to work on the local dev environment and not the build box. So locally all these tests were working and green, but the Test Fixture setup threw an exception during the setup which seems to cause Icarus and Echo to ignore the Fixture. The only way I was able to see this was through Icarus and was only able to see the actual exception in the html report. As mentioned above we output the text report which did not contain this, in our opinion, vital information. So my questions are: - Why would Echo not report these as failed tests? - Is there anything we can do to avoid this situation in the future? Thanks for any help, as we do a fair amount of test fixture setup this seems like quite a hole in our testability. Mike Brown
-- You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mbunituser?hl=en.
