Test-driven development concepts, taxonomy, and future direction

Janzen, David S.; Saiedian, Hossein

doi:10.1109/mc.2005.314

Cited by 239 publications

(107 citation statements)

References 12 publications

Supporting

Mentioning

104

Contrasting

Unclassified

Order By: Relevance

“…Testing on the CI is a surrogate for testing in the IDE for getting quick feedback. One of the core ideas of developer testing is to provide quick feedback to developers [14,15]. Yet, in a recent study on how 416 software developers test in their Integrated Development Environments (IDEs) [16], we could not explain the "testing paradox": developers spent a substantial 25% of their time working on tests, yet rarely executed them in their IDE.…”

Section: P4 Test Integration In Different Environments Is Valuablementioning

confidence: 99%

Oops, my tests broke the build: An analysis of Travis CI builds with GitHub

Beller

Gousios

Zaidman

2016

Preprint

View full text Add to dashboard Cite

Continuous Integration (CI) has become a best practice of modern software development.At present, we have a shortfall of insight into the testing practices that are common in CIbased software development. In particular, we seek quantifiable evidence on how central testing really is in CI, how strongly the project language influences testing, whether different integration environments are valuable and if testing on the CI can serve as a surrogate to local testing in the IDE. In an analysis of 2,640,825 Java and Ruby builds on Travis CI, we find that testing is the single most important reason why builds fail.Moreover, the programming language has a strong influence on both the number of executed tests, their test run time and proneness to fail. The use of multiple integration environments leads to 10% more failures being caught at build time. However, testing in the CI does not seem to be a good surrogate for running tests in the IDE.

show abstract

Section: P4 Test Integration In Different Environments Is Valuablementioning

confidence: 99%

Oops, my tests broke the build: An analysis of Travis CI builds with GitHub

Beller

Gousios

Zaidman

2016

Preprint

View full text Add to dashboard Cite

show abstract

“…It could be that the effect of the testing frequency is more important than when the tests are written. Thus deep exploratory studies on testing methods are required in order to identify confounding factors [15].…”

Section: Test First (Tf) Is An Established Development Technique Whicmentioning

confidence: 99%

What Makes Testing Work: Nine Case Studies of Software Development Teams

Thomson

Holcombe

Simons

2009

2009 Testing: Academic and Industrial Conference - Practice and Research Techniques

View full text Add to dashboard Cite

Abstract-Recently there has been a focus on test first and test driven development; several empirical studies have tried to assess the advantage that these methods give over testing after development. The results have been mixed. In this paper we investigate nine teams who tested during coding to examine the effect it had on the external quality of their code. Of the top three performing teams two used a documented testing strategy and the other an ad-hoc approach to testing. We conclude that their success appears to be related to a testing culture where the teams proactively test rather than carry out only what is required in a mechanical fashion.Testing; test first; test driven development; extreme programming;emprical; qualitative; testing culture.

show abstract

“…While some practitioners have applied some form of TDD for several decades [11], aca demic and industry studies have only more recently emerged [9]. These studies have exam ined the effects of TDD on external quality and programmer productivity with somewhat mixed results.…”

Section: : Related Workmentioning

confidence: 99%