Preliminary Analysis of the Effects of Pair Programming and Test-Driven Development on the External Code Quality

Authors:
Lech Madeyski
Affiliations:
Wroclaw University of Technology, Institute of Applied Informatics, Wyb. Wyspianskiego 27, 50-370 Wroclaw, Poland, e-mail: Lech.Madeyski@pwr.wroc.pl, http://madeyski.e-informatyka.pl
Venue:
Proceedings of the 2005 conference on Software Engineering: Evolution and Emerging Technologies
Year:
2005

Citing 11
Cited 13

The case for collaborative programming

Communications of the ACM
Pair Programming Illuminated

Pair Programming Illuminated
Test Driven Development: By Example

Test Driven Development: By Example
Using Students as Subjects—A Comparative Study ofStudents and Professionals in Lead-Time Impact Assessment

Empirical Software Engineering
Strengthening the Case for Pair Programming

IEEE Software
Assessing test-driven development at IBM

Proceedings of the 25th International Conference on Software Engineering
The collaborative software process(sm)

The collaborative software process(sm)
Test-Driven Development as a Defect-Reduction Practice

ISSRE '03 Proceedings of the 14th International Symposium on Software Reliability Engineering
An initial investigation of test driven development in industry

Proceedings of the 2003 ACM symposium on Applied computing
Are Reviews an Alternative to Pair Programming?

Empirical Software Engineering
Extreme Programming Explained: Embrace Change (2nd Edition)

Extreme Programming Explained: Embrace Change (2nd Edition)

Guest Editors' Introduction: TDD--The Art of Fearless Programming

IEEE Software
A survey of evidence for test-driven development in academia

ACM SIGCSE Bulletin
Capable Leader and Skilled and Motivated Team Practices to Introduce eXtreme Programming

Balancing Agility and Formalism in Software Engineering
The impact of Test-First programming on branch coverage and mutation score indicator of unit tests: An experiment

Information and Software Technology
Impact of test-driven development on productivity, code and tests: A controlled experiment

Information and Software Technology
A multiple comparative study of test-with development product changes and their effects on team speed and product quality

Empirical Software Engineering
Critical issues on test-driven development

PROFES'11 Proceedings of the 12th international conference on Product-focused software process improvement
The effectiveness of test-driven development: an industrial case study

Software Quality Control
The impact of pair programming and test-driven development on package dependencies in object-oriented design — an experiment

PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Is external code quality correlated with programming experience or feelgood factor?

XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in Software Engineering
On the effects of pair programming on thoroughness and fault-finding effectiveness of unit tests

PROFES'07 Proceedings of the 8th international conference on Product-Focused Software Process Improvement
The impact of test-driven development on software development productivity: an empirical study

EuroSPI'07 Proceedings of the 14th European conference on Software Process Improvement
Considering rigor and relevance when evaluating test driven development: A systematic review

Information and Software Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

Test-driven development (TDD) and pair programming (PP) are the key practices of eXtreme Programming methodology that have caught the attention of software engineers and researchers worldwide. One of the aims of the large experiment performed at Wroclaw University of Technology was to investigate the difference between test-driven development and the traditional, test-last develop-ment as well as pair programming and solo programming with respect to the external code quality. It appeared that the external code quality was lower when test-driven development was used instead of the classic, test-last software development approach in case of solo programmers (p=0.028) and pairs (p=0.013). There was no difference in the external code quality when pair programming was used instead of solo programming.