Round 2: LX offense, compile defending
VS2005 comes with three frameworks for testing:
- Unit testing (in assembly Microsoft.VisualStudio.QualityTools.UnitTestFramework)
- Web testing (in assembly Microsoft.VisualStudio.QualityTools.WebTestFramework)
- Load testing (in assembly Microsoft.VisualStudio.QualityTools.LoadTestFramework)
Since I already said we where only going to focus on unit testing, I’ll only look at the unit testing framework. Let’s see what the NUnit framework does against all of Microsoft’s goodness.
Extra attribute goodness
- Tests can have a timeout. Use TimeoutAttribute to indicate the timeout in milliseconds.
- You can extend the metadata on tests by specifying the TestPropertyAttribute.
- Add descriptions to your tests.
- You are able to prioritize your tests with the PriorityAttribute.
This attributed information is viewable from both the Test View window and the Properties window for a selected test.
Tight integration with Team Foundation Server
- Unit tests can be associated with one or more Team Foundation Server workitem (with WorkItemAttribute).
- You can create workitems right from the test results.
- Tests can be part of an iteration or project area. (See also: Properties window above)
So, let Dennis sweat for a while and see what he makes of this. I didn’t even whip out the big guns yet. Other colleague Mike Glaser already commented on this in the previous round. Your turn, Dennis. 😛