Timeline for Can these unit tests be improved?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2012 at 2:55 | vote | accept | Kelly Sommers | ||
| Feb 2, 2012 at 8:30 | history | tweeted | twitter.com/#!/StackCodeReview/status/164988961633218560 | ||
| Feb 2, 2012 at 6:23 | answer | added | Srikanth Venugopalan | timeline score: 3 | |
| Feb 1, 2012 at 21:18 | answer | added | Mark Seemann | timeline score: 8 | |
| Feb 1, 2012 at 13:12 | comment | added | Tacoman667 | Each test should test only one "thing". So having a couple of Asserts in a test is actually fine. For example, it_should_return_empty_string() would be perfectly fine to have Assert.IsNotNull(result) and Assert.Equals(String.Empty, result). | |
| Feb 1, 2012 at 10:28 | answer | added | infinitary | timeline score: 6 | |
| Feb 1, 2012 at 10:07 | comment | added | John Ferguson | You're probably better at testing than me, but shouldn't there really only be one Assert per test method? | |
| Feb 1, 2012 at 6:52 | comment | added | Adam Dymitruk | I would not use MSTest. It's slower than the alternatives and has fewer features. | |
| Feb 1, 2012 at 6:18 | comment | added | Nikos Baxevanis | One improvement is to use xUnit.net instead of MSTest which integrates with AutoFixture and allows you to parameterize those tests via data theories. Once you have parameterized tests, AutoFixture can take care of the rest supplying the parameter values for you and even Auto-Mock them using FakeItEasy. :) | |
| Feb 1, 2012 at 5:49 | history | asked | Kelly Sommers | CC BY-SA 3.0 |