Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Extreme programming explained: embrace change
Extreme programming explained: embrace change
An encompassing life cycle centric survey of software inspection
Journal of Systems and Software
Case study: extreme programming in a university environment
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Pair Programming Illuminated
Test Driven Development: By Example
Test Driven Development: By Example
Strengthening the Case for Pair Programming
IEEE Software
Extreme Programming from a CMM Perspective
IEEE Software
Assessing test-driven development at IBM
Proceedings of the 25th International Conference on Software Engineering
IEEE Software
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
On the Effectiveness of the Test-First Approach to Programming
IEEE Transactions on Software Engineering
XUnit Test Patterns: Refactoring Test Code
XUnit Test Patterns: Refactoring Test Code
Two controlled experiments concerning the comparison of pair programming to peer review
Journal of Systems and Software
Design and code inspections to reduce errors in program development
IBM Systems Journal
A systematic mapping study on the combination of static and dynamic quality assurance techniques
Information and Software Technology
Hi-index | 0.00 |
Testing is an essential part of an agile process as test is automated and tends to take the role of specifications in place of documents. However, whenever test cases are faulty, developers' time might be wasted to fix problems that do not actually originate in the production code. Because of their relevance in agile processes, we posit that the quality of test cases can be assured through software inspections as a complement to the informal review activity which occurs in pair programming. Inspections can thus help the identification of what might be wrong in test code and where refactoring is needed. In this paper, we report on a preliminary empirical study where we examine the effect of conducting software inspections on automated test code. First results show that software inspections can improve the quality of test code, especially the repeatability attribute. The benefit of software inspections also apply when automated unit tests are created by developers working in pair programming mode.