After running a bunch of tests from a single test assembly I get the
following output.  The generated XML report is missing a whole bunch of
those tests too.  Hundreds of them!  Funny thing is, it was working just
fine a couple of days ago.  I'd get reports with 805 tests in them.

Any ideas what's up here?  It appears that some of my tests that do .Net
remoting started failing.  Looks like they might be messing up MbUnit
and causing it to abort execution prematurely though I don't see any
direct evidence of that in the console output.

[info] Loading test assemblies
[info] Starting execution
[info] Sorting assemblies by dependencies
[info] etting up fixture colors
[info] Loading Platform.Framework.Tests
[info] Found 805 tests
[info] Running fixtures.
[info] Tests finished: 805 tests, 157 success, 5 failures, 0 ignored
[info] All Tests finished: 166 tests, 161 success, 5 failures, 0 ignored
in 73.3129692 seconds
[info] Creating reports in
C:\RelEng\Projects\KeenDev-Trunk-Tests\Work\Temp\TestResults
[info] Created xml report
C:\RelEng\Projects\KeenDev-Trunk-Tests\Work\Temp\TestResults\Platform.Fr
amework.Tests.mbunit.xml
[info] MbUnit execution finished in 82.2817766s.

Jeff.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to