Comparative Study of Test Driven Development with Traditional Techniques
Shaweta Kumar1, Sanjeev Bansal2

1Shaweta Kumar working as System Analyst at Aon Hewitt, is currently pursuing M.Tech Computer Science, ASET, Amity University, Noida, India.
2Professor Dr Sanjeev Bansal, Guide, Amity Business School, Amity University, Noida, India.
Manuscript received on February 08, 2013. | Revised Manuscript received on February 28, 2013. | Manuscript published on March 05, 2013. | PP: 352-360 | Volume-3 Issue-1, March 2013. | Retrieval Number: A1351033113/2013©BEIESP
Open Access | Ethics and Policies | Cite
© The Authors. Published By: Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC BY-NC-ND license (

Abstract: Test-Driven Development is the evolutionary approach in which unit test cases are incrementally written prior to code implementation. In our research, we will be doing comparative study of Test Driven development with traditional techniques through literature study as well as industrial survey. Through this research, we would like to find out the factors encouraging the use of Test Driven Development and also the obstacles that are limiting the adoption of Test Driven Development in the industry. The TDD method is radically different from the traditional way to create software. In traditional software development models, the tests are written after the code is implemented, in other words we could refer it as test-last. This does not drive the design of the code to be testable. Defining the tests with the requirements, rather than after, and using those tests to drive the development effort, gives us much more clearly picture and share focus on the goal. If tests are written after the implementation, there is a risk that tests are written to satisfy the implementation, not the requirements. An important rule in TDD is: “If you can’t write test for what you are about to code, then you shouldn’t even be thinking about coding.
Keywords: Extreme programming, refactoring, test driven development, test-first methodology, test-last methodology.