BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage TDD Content on InfoQ

  • Book Review: Test-Driven Infrastructure with Chef - Second Edition

    The second edition of Stephen Nelson-Smith's book "Test-Driven Infrastructure with Chef" covers the principles behind "Infrastructure as Code", provides an introduction to Ruby, Chef, and important Tools. The main part consists of detailed examples on how to use the tools required to write fully tested infrastructure code.

  • ATDD From the Trenches

    A concrete example of how to get started with acceptance-test driven development on an existing code base. It is part of the solution to technical debt.

  • Book Review: ATDD By Example

    “ATDD By Example” value proposition was to be an introductory hands-on guide to implementing and successfully applying Acceptance Test Driven Development (ATDD) from zero. Despite doing a reasonable job of summarizing and/or pointing to several test-related practices required for any successful agile tester, the book ends up trying and failing to be all things to all readers.

  • Metrics-Driven Development

    In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development: using metrics to drive the entire application development.

  • Virtual Panel: Code-to-Test Ratios, TDD and BDD

    In the last couple of months several online discussions took place about test first or test last, code-to-test ratios or whether BDD is really just TDD. InfoQ asked the opinion of BDD and TDD experts.

  • Feature Injection: three steps to success

    Often Customers provide half baked solutions with no linkage to value. An Agile team needs examples linked to the Business Value they provide. Feature Injection is a process that takes a half baked solution identifies the Business Value it provides and then produces a set of examples driven from that value.

  • Virtual Panel: Specification by Example, Executable Specifications, Scenarios and Feature Injection

    In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.

  • Using Coding Katas, BDD and VS2010 Project Templates: Part 3

    This is the third and final part of the late Jamie Phillip’s exploration into the world of coding kata’s and Behavior Driven Design. This part shows how to incorporate VS 2010 project templates into the testing process.

  • Using Coding Katas, BDD and VS2010 Project Templates: Part 2

    This is the second of a three-part series on how Jamie Phillips used a combination of coding katas, behavior driven development, and project templates to improve his development practices. In this part Jamie introduces the reader to behavior driven development and explains how it can improve the effectiveness of unit testing.

  • Using Coding Katas, BDD and VS2010 Project Templates: Part 1

    This three-part series on using coding katas in practice Behavior Driven Development was written by the late Jamie Phillips, a well-known member of Boston's Agile and .NET communities. When we saw the first draft of this article we were all eager to publish it, but he passed away before we could finish the editing process. With the permission of wife Diana, we proudly present his final work.

  • Introducing the Tellurium Automated Testing Framework

    Jian Fang describes the The Tellurium Automated Testing Framework he created which features a novel approach to automated, referred to as a UI module, to try and improve the often brittle state of automated web UI testing code.

  • The Limits of Agile

    The problems faced by teams that are attempting Agile in non-traditional settings aren't that Agile principles are inapplicable, nor that the feedback cycle is doomed to failure; but rather, outside of a certain Agile sweet-spot there are additional barriers and costs to applying Agile techniques. None of these obstacles prevents Agile in itself but each increases the cost of getting to Agile.

BT