Test-driven development in large projects

Research output: Contribution to journalReview article

16 Citations (Scopus)

Abstract

Test-driven development (TDD) is a key practice for agile developers because it involves writing test cases ahead of the code which can improve design. The TDD process works well for projects in which a collocated team develops a small to medium system, and the developers must take care of account for its focus on unit testing and its failure to address communication issues during system and integration testing. The developers must write codes and additional test cases with the TDD process. The TDD improves the code quality by identifying likely breaking points early, and can help with building a testing suite. TDD results in a high ratio of test to production code and therefore any system change is likely to affect the test code.

Original languageEnglish (US)
Article number1717338
Pages (from-to)25-29
Number of pages5
JournalIT Professional
Volume8
Issue number5
DOIs
StatePublished - Sep 1 2006

Fingerprint

Integration testing
Testing
Communication

All Science Journal Classification (ASJC) codes

  • Computer Science(all)

Cite this

@article{78361012180a495ba7d8c9db73fd5174,
title = "Test-driven development in large projects",
abstract = "Test-driven development (TDD) is a key practice for agile developers because it involves writing test cases ahead of the code which can improve design. The TDD process works well for projects in which a collocated team develops a small to medium system, and the developers must take care of account for its focus on unit testing and its failure to address communication issues during system and integration testing. The developers must write codes and additional test cases with the TDD process. The TDD improves the code quality by identifying likely breaking points early, and can help with building a testing suite. TDD results in a high ratio of test to production code and therefore any system change is likely to affect the test code.",
author = "Sangwan, {Raghvinder S.} and Laplante, {Phillip A.}",
year = "2006",
month = "9",
day = "1",
doi = "10.1109/MITP.2006.122",
language = "English (US)",
volume = "8",
pages = "25--29",
journal = "IT Professional",
issn = "1520-9202",
publisher = "IEEE Computer Society",
number = "5",

}

Test-driven development in large projects. / Sangwan, Raghvinder S.; Laplante, Phillip A.

In: IT Professional, Vol. 8, No. 5, 1717338, 01.09.2006, p. 25-29.

Research output: Contribution to journalReview article

TY - JOUR

T1 - Test-driven development in large projects

AU - Sangwan, Raghvinder S.

AU - Laplante, Phillip A.

PY - 2006/9/1

Y1 - 2006/9/1

N2 - Test-driven development (TDD) is a key practice for agile developers because it involves writing test cases ahead of the code which can improve design. The TDD process works well for projects in which a collocated team develops a small to medium system, and the developers must take care of account for its focus on unit testing and its failure to address communication issues during system and integration testing. The developers must write codes and additional test cases with the TDD process. The TDD improves the code quality by identifying likely breaking points early, and can help with building a testing suite. TDD results in a high ratio of test to production code and therefore any system change is likely to affect the test code.

AB - Test-driven development (TDD) is a key practice for agile developers because it involves writing test cases ahead of the code which can improve design. The TDD process works well for projects in which a collocated team develops a small to medium system, and the developers must take care of account for its focus on unit testing and its failure to address communication issues during system and integration testing. The developers must write codes and additional test cases with the TDD process. The TDD improves the code quality by identifying likely breaking points early, and can help with building a testing suite. TDD results in a high ratio of test to production code and therefore any system change is likely to affect the test code.

UR - http://www.scopus.com/inward/record.url?scp=33750845106&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=33750845106&partnerID=8YFLogxK

U2 - 10.1109/MITP.2006.122

DO - 10.1109/MITP.2006.122

M3 - Review article

VL - 8

SP - 25

EP - 29

JO - IT Professional

JF - IT Professional

SN - 1520-9202

IS - 5

M1 - 1717338

ER -