Unit Testing, Agile Development, Leadership & .NET - By Roy Osherove
Last day at Barcelona, we still don't have wireless on Vista. We shot a few films that we will upload
I always consider my unit test code to be equally important as my production code. Therefore Therefore I include my assemblies that contain my tests in my FxCop projects. When using underscores in method names (the naming best practice you suggested), FxCop reports an issue on this. I like your naming standard for unit tests, but I like FxCop as well (considering test code == production code). What's your view on this matter?
Jan: I suggest creating a custom FxCop rule that disregrads methods with a test attribute, or somethign of the sort.
or even enforces that naming guideline on methods with the test attribute.
I will give it a try. Thanks for the input.