Comments on: My Unit Testing Idea : Facilitating Multiple Assertions http://averyblog.com/net/my-unit-testing-idea-facilitating-multiple-assertions/ This is not the greatest tagline in the world... this is just a tribute. Mon, 11 Jan 2010 16:36:16 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: One Assert vs. Multiple Asserts « Clackwell’s Weblog http://averyblog.com/net/my-unit-testing-idea-facilitating-multiple-assertions/comment-page-1/#comment-2018 One Assert vs. Multiple Asserts « Clackwell’s Weblog Wed, 29 Oct 2008 03:57:46 +0000 http://averyblog.infozerk.net/?p=579#comment-2018 <strong>RE: My Unit Testing Idea : Facilitating Multiple Assertions</strong> <p>Pingback from One Assert vs. Multiple Asserts « Clackwell’s Weblog</p> RE: My Unit Testing Idea : Facilitating Multiple Assertions

Pingback from One Assert vs. Multiple Asserts « Clackwell’s Weblog

]]> By: astopford@gmail.com http://averyblog.com/net/my-unit-testing-idea-facilitating-multiple-assertions/comment-page-1/#comment-2015 astopford@gmail.com Wed, 04 Oct 2006 09:01:15 +0000 http://averyblog.infozerk.net/?p=579#comment-2015 <p>Hi James,<br /><br />Although not quite what you describe here, MbUnit can allow you to pump in a range of selected data to a single assert.<br /><br />http://www.mertner.com/confluence/display/MbUnit/CombinatorialTestAttribute<br /><br />Here you can make use of the combintional and factory fixtures to define the data used for testing across an asssert. The row testing that you have shown here before allows you to create a range of tests between values. The combintional test lets you define your test values based on the object your testing. It's not quite what your looking for but might help.<br /><br />Andy</p> Hi James,

Although not quite what you describe here, MbUnit can allow you to pump in a range of selected data to a single assert.

http://www.mertner.com/confluence/display/MbUnit/CombinatorialTestAttribute

Here you can make use of the combintional and factory fixtures to define the data used for testing across an asssert. The row testing that you have shown here before allows you to create a range of tests between values. The combintional test lets you define your test values based on the object your testing. It’s not quite what your looking for but might help.

Andy

]]> By: Eber Irigoyen http://averyblog.com/net/my-unit-testing-idea-facilitating-multiple-assertions/comment-page-1/#comment-2016 Eber Irigoyen Tue, 03 Oct 2006 22:53:34 +0000 http://averyblog.infozerk.net/?p=579#comment-2016 <p>it seems MBUnit is far better suited for what you want<br /><br />...and commenting in your blog sucks really bad in IE7</p> it seems MBUnit is far better suited for what you want

…and commenting in your blog sucks really bad in IE7

]]> By: Brian Broom http://averyblog.com/net/my-unit-testing-idea-facilitating-multiple-assertions/comment-page-1/#comment-2017 Brian Broom Mon, 02 Oct 2006 14:14:03 +0000 http://averyblog.infozerk.net/?p=579#comment-2017 <p>One thing you might take a look at, is in the first test, building up the expected collection as its own List<Book> and then just assert the two collections are equal. This may or may not make things more readable, but would reduce the number of asserts.<br /><br />In general, though, I agree that it would be nice if asserts after the fail were still run.<br /><br />I also tend to not follow the 'one assert per test' thing unless it really does make sense for that particular test.</p> One thing you might take a look at, is in the first test, building up the expected collection as its own List<Book> and then just assert the two collections are equal. This may or may not make things more readable, but would reduce the number of asserts.

In general, though, I agree that it would be nice if asserts after the fail were still run.

I also tend to not follow the ‘one assert per test’ thing unless it really does make sense for that particular test.

]]>