What Is TDD (Test Driven Development)?
by Nataliia Vasylyna | January 19, 2016 12:09 pm
TDD is an abbreviation for test driven development. It is the special practice of the code creation used by developers. Not all development teams practice TDD.
One may think that only developers should be aware of TDD, as it does not concern software testing[1]. It is not really so. Test driven development helps the specialists from software testing company to better understand the software and associated tests. It simplifies the execution of acceptance testing[2].
It is important to clarify what specialists take part in TDD and define the main steps of this practice.
Who Is Involved in TDD?
- Developer
- Tester
- Customer
Every expert plays his own role and performs the defined tasks of the TDD Cycle.
What Are the TDD Steps?
- A failing test is defined and created.
- Developer writes the amount of the product code which will be enough for making the test pass.
- The code is refactored according to the existing standards with the aim of making it clean and more efficient.
TDD provides the immediate feedback on the code functioning. This quick feedback loop can be used by testers. In general, test driven development concerns the design of the code.
To perform mobile testing[3], website testing or any other software product testing, the specialists should apply different principles and use various techniques in their work.
Learn more from QATestLab
Related Posts:
- software testing: https://qatestlab.com/services/We-Are-Professionals-in/software-product-testing/
- acceptance testing: https://qatestlab.com/services/Step-by-Step/acceptance-testing/
- mobile testing: http://mobile.qatestlab.com/en/
- Automated Testing During Test-Driven Development: https://blog.qatestlab.com/2015/06/16/automation-during-tdd/
- Five reasons why developers are not good testers: https://blog.qatestlab.com/2020/02/18/developers-versus-testers/
- How to save money for buying a new car by measuring code coverage: https://blog.qatestlab.com/2019/10/10/measure-code-coverage/
Source URL: https://blog.qatestlab.com/2016/01/19/test-driven-development/