InfoQ

InfoQ

Topic/Tag specific view

Design by Contract Content on InfoQ


Latest featured content about Design by Contract

Design by Contract (DbC)

Topics
.NET

Joël Hébert introduces and demoes Design by Contract’s main concepts –preconditions, postconditions, object invariants- showing their benefits in creating more robust code.

Code Contracts in C#

Topics
Unit Testing,
Design,
.NET

This article discusses the concepts and ideas of Code Contracts and the way they are handled in C#. Unless you happen to have used a language supporting Design by Contract before, you may sometimes find yourself unsure of how to proceed with Code Contracts. If you're using it in conjunction with Test Driven Development, what should you write first - the contract or the implementation?

TDD in a DbC World

Topics
.NET,
Design,
Methodologies,
Architecture

After presenting some basics of Design by Contract using Microsoft’s SpecSharp framework, Greg Young explains how we can keep the Test First mentality in a Contract First world.

News about Design by Contract

Code Contracts are Making Slow Progress

Topics
.NET,
Code Analysis

Code Contracts are making slow progress towards being ready for production use. While the technology still shows a lot of initial promise, it doesn’t take long to run into a road block or six that makes them unusable in their current form.

Details on Using Code Contracts

Topics
.NET Framework,
.NET,
Unit Testing,
Programming,
Software Testing

InfoQ has informed on the availability of Code Contracts for .NET. This time we want to offer more details on using Code Contracts, an important addition to .NET.

Code Contracts for .NET Is Available for Download

Topics
.NET Framework,
.NET,
Unit Testing,
Programming,
Software Testing

Code Contracts is the .NET implementation of the Design by Contract concept. While it was supposed to be delivered with .NET 4.0, Code Contracts is already available for download from DevLabs. Contracts impose certain restrictions on using APIs, making programming safer, having more validations and resulting in fewer unexpected errors during runtime.

"Classic" versus "Mockist" TDD, Distinction Real?

Topics
Software Craftsmanship,
Agile,
Unit Testing,
Software Testing

Hot in the TDD Yahoo group is a discussion concerning the perceived continuum between the "Classic" and "Mockist" TDD. Steve Freeman, Nat Pryce, Michael Feathers, Dale Emery, and many more discuss terminology and describe their approaches. The discussion also debates whether there even really exists such a continuum, and if so, what distinguishes the approaches that represent it's extremes?