Yup.  So if you wanted to grab the outcome of the fixture as a whole you
could check it in Dispose or TestFixtureTearDown.
 
Anyways, I'm curious what your use-case is.  Several people have asked for
similar features to manipulate parts of the test report during test
execution.  We do have a separate "test runner extension" mechanism whereby
you can extend the behavior of the test runner to upload results into a test
database or perform other tasks of that sort.
 
Jeff.

  _____  

From: [email protected] [mailto:[email protected]] On
Behalf Of Bruno Wouters
Sent: Monday, June 29, 2009 11:41 PM
To: [email protected]
Subject: MbUnit Re: Test count



Hi Jeff,

 

Thanks for the fast response!

Isn't the dispose method called when the fixture is disposed? (So not after
every test?)

 

Greets,

Bruno

 

 

From: [email protected] [mailto:[email protected]] On
Behalf Of Jeff Brown
Sent: maandag 29 juni 2009 18:09
To: [email protected]
Subject: MbUnit Re: Test count

 

You can only get Statistics and other Report objects from the context of the
test runner itself, not from within the tests.

 

However within the tests you can read TestContext.Current.Outcome during
TearDown or Dispose to determine whether the test passed or failed.

 

Jeff.

 

  _____  

From: [email protected] [mailto:[email protected]] On
Behalf Of Bruno Wouters
Sent: Monday, June 29, 2009 2:39 AM
To: 'MbUnit.User'
Subject: MbUnit Test count

Hi all,

 

I'm trying to get the test count (excl skipped) when my custom log4net
appender is being closed. I saw that there is a Statistics class but how can
I access the instance of it?

 

Thanks!

 

Greets,

Bruno

<BR






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

Reply via email to