phuccaoca123 / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

Assertion count is unreliable #36

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
All assertions should call IncrementAssertCount() (see this thread 
http://groups.google.co.uk/group/MbUnitDev/browse_thread/thread/ff931231b08
0f9e9/4ca0d484fb17c6b1?lnk=gst&q=assertcount&rnum=1#4ca0d484fb17c6b1 ), 
this is not currently done in a consistent manner. The assert tests should 
also be modified to check the assert count before and after each test. 
Also, a lot of assertions call other assertions internally which 
artificially inflates the assertion count - in my opinion if you call one 
assert in your test code the count should increase by one.

Original issue reported on code.google.com by astopf...@gmail.com on 31 Aug 2007 at 1:38

GoogleCodeExporter commented 9 years ago
This will be handled very differently in Gallio.  Dunno how much it matters in 
v2.4.2.

Original comment by jeff.br...@gmail.com on 3 Sep 2007 at 9:41

GoogleCodeExporter commented 9 years ago
MbUnit v3 has a much more stringent pattern for reporting assertions.  This 
produces
significantly more reliable assert counts.

Original comment by jeff.br...@gmail.com on 11 Nov 2008 at 8:34