Test Driven Testing

In this talk I will explore applying the 3 laws of test driven development (TDD) to manual testing. TDD starts with an just an expectation, and then writing a test to verify that expectation and finally writing just enough code to allow the test to pass. The result is a tight feedback loop of expectation, implementation, verification.

Take unit tests out of the equation and think about the testing performed by dedicated manual testers. Unlike development testing is perceived as an art, rooted in ad-hoc and intuitive decisions.

I’ll establish a working definition of Test Driven Testing by replacing the developer-oriented laws of TDD with test centric alternatives:

  1. No testing until you have identified and defined an objective
  2. Test Only enough to Satisfy the Objective
  3. No Activities outside the objective
  4. Refactor Actions and Assumptions

Using these principles I will then step through applying a test-driven testing approach to a project, comparing it other traditional testing practices. I will make the case that test-driven testing provides testers with the same tight feedback loop and positive outcomes that TDD provides, while increasing acceptance and understanding across roles.

Session Takeaways:

  • The benefits for testers of conscious intent and a tight feedback loop
  • A basic understanding of TDD, its vocabulary and benefits
  • How the Red Green Refactor cycle can be applied to manual testing
  • How a common approach and vocabulary benefits testers cross team/role relationships

Strategy
Location: TBD Date: April 11, 2018 Time: - Brendan Connolly