Testability depends on a number of attributes of the software. One of these attributes is the ability to observe the current state of the software being tested and the output it produces. Another point is making it clear the initial conditions under which a piece of software should run, and what are expected results.  All together, these attributes form the software contract of a class method. The software contract is based on preconditions, postconditions, and invariants—abstract formulas to express the “conditions of service” of a method. How would you code a software contract? You can code it manually or, if you’re using the newest C#, you can use the Code Contract API. In this session, we’ll take a tour of the Code Contract API and see a number of examples of how to use it to implement testability in your classes.


About the speaker:
Dino Esposito is a trainer and software consultant based in Rome, Italy. He is a member of the IDesign team. Dino specializes in Microsoft .NET technologies and spends most of his time teaching and consulting across Europe, Australia, and the United States.
Over the years, Dino developed hands-on experience and skills in architecting and building distributed systems for banking and insurance companies and, in general, in industry contexts where the demand for security, optimization, performance, scalability, and interoperability is dramatically high. Every month, at least five magazines and Web sites throughout the world publish Dino’s articles covering topics that range from Web development to workflow, and from software best practices to services.