Friday, October 05, 2007
Posted on Friday, October 05, 2007 9:21:56 PM (Mountain Daylight Time, UTC-06:00)  Comments [1] | 
Categories: ArcGIS Devt | Devt Tools | Unit Testing | Visual Studio 2005

I just finished off some burly refactoring of our security management code base so that it could be better unit tested. This subsystem essentially controls what tools a user has access to, as well as what layers / features a user can edit, so it's a pretty critical part of the infrastructure.

I'm working on some posts about how I did this, and should get them out next week, but for now, I'll just show this...

tests

Although there are only 16 tests listed, many of these methods actually contain a number of individual test assertions, and there are more than 80 tests that are actually run.

Friday, October 05, 2007 5:50:03 PM (Mountain Daylight Time, UTC-06:00)
I guess there are two questions to be asked here:
1. Should you really have multiple test assertions in the same test? (I know is convinient to do, but also very messy from a testdriven development perspective).
2. What is the code coverage of the unit tests.
Morten
Comments are closed.