We all agree that writing tests is helpful, recommended and even sexy. However, unless you associate it with some test-driven design methodology, writing tests risks being an end in itself. On one hand you have the classes to test; on the other hand, you have classes that promise to test other classes. And nothing in the middle that guarantees that tests are appropriate and meaningful. An approach that creates the environment for a much more effective refactoring, while not excluding unit testing, is based on software contracts. A software contract defines the terms and conditions for each method in each class. That gives you an optional run time checking mechanism as well as concrete guidance on how to refactor when you have to. Software contracts are not a new concept in software, but only now they have a widespread implementation in .NET. This webinar shows you why you should look seriously at software contracts—Code Contracts in the .NET jargon—and what’s the appropriate angle and perspective for that.
↧