Editing Test-driven development (section)

== Test-driven work ==

TDD has been adopted outside of software development, in both product and service teams, as '''test-driven work'''.<ref>Leybourn, E. (2013) ''Directing the Agile Organisation: A Lean Approach to Business Management''. London: IT Governance Publishing: 176-179.</ref> For testing to be successful, it needs to be practiced at the micro and macro levels. Every method in a class, every input data value, log message, and error code, amongst other data points, need to be tested.<ref>{{Cite web |last=Mohan |first=Gayathri |title=Full Stack Testing |url=https://www.thoughtworks.com/en-us/insights/books/full-stack-testing |access-date=2022-09-07 |website=www.thoughtworks.com |language=en-US}}</ref> Similar to TDD, non-software teams develop [[quality control]] (QC) checks (usually manual tests rather than automated tests) for each aspect of the work prior to commencing. These QC checks are then used to inform the design and validate the associated outcomes. The six steps of the TDD sequence are applied with minor semantic changes:
# "Add a check" replaces "Add a test"
# "Run all checks" replaces "Run all tests"
# "Do the work" replaces "Write some code"
# "Run all checks" replaces "Run tests"
# "Clean up the work" replaces "Refactor code"
# "Repeat"