program selection system

Do you have a preferred way to write unit tests?

Could you describe it to your pairing partner? Could you describe it to your team? Could you intentionally adjust it to suit a particular testing context?

If your team does not have a shared, explicit unit testing philosophy you’re not getting full value from your testing efforts.

In this tutorial you will learn a simple, powerful technique to describe your unit test philosophy.

It’s easy to write software. It’s harder to write software that’s simple, elegant, working and important. Examples help to drive conversation, avoid ambiguity, eliminate waste, make estimates more accurate, clarify design and produce software that matters. Participants will develop a small game in a Renga (taking it in turns), adding examples of desired application behaviour at both a system and unit level, while learning BDD concepts.

Continuous Testing (CT) is a developer practice that involves automatically running tests after every change, even so much as a single statement. It gives you instant feedback about the semantic correctness of your code, just as modern IDE’s give you instant feedback about syntax errors. CT has a profound impact on the way we use TDD. This session will cover the history, theory, practice, and daily application of CT to real-world projects.