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

  • Refactoring Coderetreats: In Search of Simple Design

    In cities all over the world, groups of software developers have been getting together at weekends repeatedly trying to write code for a given problem, but never completing a solution. At coderetreats, developers learn from each other and refine their software design skills. In this article David examines how they work? What do people say about them? How to make them even better?

  • Yes, Hardware Can Be Agile!

    “You can’t do 2-week iterations with hardware!” This is the first thing you’ll hear when talk turns to Agile methods in hardware-software product development. A mix of existing robust hardware development ideas, plus a few newly taken from Agile software are being used now by real teams, even to get around - or through - the challenge of doing fast iterations.

  • James Grenning on Technical Excellence

    At then recent Agile Singapore conference James Grenning presented two technically focused talks - one on the importance of technical excellence and the other teaching test driven development. He spoke to InfoQ about the importance of strong technical practices to enable true agility in software development.

  • Q&A about the book Common System and Software Testing Pitfalls

    The book Common System and Software Testing Pitfalls by Donald Firesmith provides descriptions of 92 pitfalls that make testing less efficient and effective. The descriptions explain what testers and stakeholders can do to avoid falling into the pitfalls and how to deal with the consequences when they have fallen into them.

  • The Life and Times of TDD

    Scott Ambler discusses a recent mini-survey designed to find out how TDD is being used in practice. He examines the state of practice and what techniques and tools are being used with TDD.

  • Agile Architecture Applied

    Agile is adaptive. When and how to apply architecture depends on the context. This article first explains why this is the case and then how you can still give proper attention to architecture in an agile setting. Adaptability and conversation are the essentials.

  • Taking Back Agile

    Tim Ottinger's blog post I want Agile back earlier this year led to discussions in the agile community about the way that organizations are adopting agile and the services that the industry provides to supports them. Together with Ruud Wijnands he started "take back agile" which focuses on technical practices and craftsmanship in agile.

  • *-Driven* do not change anything

    Michał Bartyzel challenges the need to master a *Driven* approach to be Software Professional. These might be: DDD, TDD, BDD, MDD or other frameworks. He maintains that they may be responsible for cognitive biases rather than playing a supporting role for broader and deeper skills.

  • Quality Code - Book Review and Interview

    Quality Code book, authored by Stephen Vance, covers the different aspects of software development lifecycle with focus on delivering quality product. In the book, Stephen discusses the practices for supporting software craftsmanship testing. InfoQ spoke with the author about the book and the best practices for testing application code.

  • 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.

BT