Kent Beck, author of 'Test Driven Development by Example', discusses Canon TDD. They explore adapting TDD to individual needs and the importance of creating test lists for expected behaviors. The conversation delves into test list conversion, managing new tests, and the significance of refactoring in the testing process.
Canon TDD workflow outlines structured TDD process with incremental testing and refactoring steps.
Initial analysis and test case listing followed by code modifications and continuous testing essential for TDD success.
Deep dives
The Canon TDD Workflow by Kent Beck
Kent Beck's Canon TDD workflow outlines the structured process of test-driven development. The first step involves creating a list of test scenarios to cover, followed by turning one item into a concrete test, making the test and previous ones pass by changing the code, optionally refactoring for improved design, and repeating until the list is empty. Beck emphasizes the importance of adhering to this workflow for effective TDD implementation.
Key Steps in Test-Driven Development
In test-driven development, the process begins by analyzing expected behavior changes and listing corresponding test cases. Subsequently, each test is transformed into a concrete test to ensure incremental progress. Following this, code modifications are made to pass the tests, avoiding common mistakes like deleting assertions or copying computed values. The workflow also includes optional refactoring and continuous testing until all scenarios are covered.
In 2002, Kent Beck released a book called "Test Driven Development by Example". In December of 2023, Kent wrote an article called "Canon TDD". With Kent's permission, this episode contains the full content of the article.
Brian's commentary is saved for a followup episode.