Discussion of Story-Test Driven Development (STDD). STDD provides a business side perspective of tests that are developed prior to coding and utilized to ensure the business logic/rules as described in the Stories are correctly implemented. As with TDD, STDD provides IT (developers and QA) with a deeper understanding of the system prior to any actual coding.

Test-driven programming is one aspect of XP that baffles programmers. Many of us make incorrect assumptions about what it means and how to do it. This month, XP coach and Java developer Roy Miller talks about what test-driven programming is about, why it can revolutionize your productivity and quality as a programmer, and the mechanics of writing tests. For the last fifty years, testing has been viewed as something that gets done toward the end of a project. Sure, there may be integration testing while the project is going on, and testing doesn't usually start after all the coding is done, but it's usually in a later phase. However, proponents of XP suggest that this model is completely backwards. As a programmer, you should write tests before you write code, then write just enough code to get the tests to pass. Doing that will help you keep your system as simple as possible.

Test automation is software development. Some people learn this the hard way. But if we take this sentence seriously, wouldn’t it mean that we have to use the same practices to develop our automation code that we use to write our production code? That would mean that we should use continuous integration, code metrics, as well as design patterns. But foremost doesn’t that mean that we should use test-driven development to develop it?

This article gives you 12 practical ways to start writing tests, and keep writing tests, regardless of your development process. The first two techniques play off of things you're probably already doing, so you don't have to move too far out of your comfort zone. The next two challenge you to wade deeper into the pool to realize the benefits of test-driven development. The remaining techniques round out the regimen to keep you testing effectively all year. You'll be well on your way to fulfilling your new year's resolutions. Caution: contents have been known to be infectious!

Acceptance test-driven development is what helps developers build high-quality software that fulfills the business’s needs as reliably as TDD helps ensure the software’s technical quality.

Have you ever been in a situation, where a simple change of code broke a few hundred tests? Have you ever had the idea that tests slow you down, inhibit your creativity, make you afraid to change the code? If you had, it means you've entered the Dungeon-of-very-bad-tests, the world of things that should not be. I've been there. I've built one myself. And it collapsed killing me in the process. I've learned my lesson. So here is the story of a dead man. Learn from my faults with Test-Driven Development (TDD) or be doomed to repeat them.

Article on how Behavior Driven Development relates to C#. It explains the value of “context” and “behavior”.

In this article Rainer Stropek and Karin Huber show how Test Driven Development (TDD) works in practice. They start with a general overview about quality assurance and testing in software development. After that they implement an end-to-end solution using the TDD philosophy. Karin and Rainer do not only use unit tests for validating the data access and business layer. They also demonstrate how the popular open source tool WatiN can be used to test-driven develop a web user interface. The sample uses Microsoft Visual Studio 2008, C# 3.0, Linq-to-SQL, Linq-to-Objects, Visual Studio Unit Tests, ASP.NET and WatiN.

Because the ASP.NET Web API leverages the fundamental building blocks of the HTTP protocol, it can provide a way of refactoring your existing ASP.NET applications into an AJAX-enabled, Test Driven Development world.

This paper gives a complete description of code coverage analysis (test Applying Mock objects effectively is a key factor when performing Test Driven Development (TDD). In this article I'll introduce the basics of using JMock, a Mock object framework, in conjunction with Test-Driven Development. To illustrate the technique I will work through a case study, the creation of a cache component by means of test-first development with JMock.