On the effects of pair programming on thoroughness and fault-finding effectiveness of unit tests

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 4589 LNCS, Issue , 2007, Pages 207-221

  Madeyski, Lech ^a  

^a WROCLAW UNIVERSITY OF TECHNOLOGY   (Poland)

Author keywords

[No Author keywords available]

Indexed keywords

CODES (SYMBOLS); COMPUTER PROGRAMMING; PROJECT MANAGEMENT; STUDENTS;

PAIR PROGRAMMING; PROGRAMMING METHODOLOGY;

SOFTWARE TESTING;

EID: 35148833554     PISSN: 03029743     EISSN: 16113349     Source Type: Conference Proceeding    
DOI: 10.1007/978-3-540-73460-4_20     Document Type: Conference Paper

References (45)

1. Williams, L., Kessler, R.: Pair Programming Illuminated. Addison-Wesley, London (2002)
2. Beck, K., Andres, C.: Extreme Programming Explained: Embrace Change, 2nd edn. Addison-Wesley, London (2004)
3. Williams, L., Kessler, R.R., Cunningham, W., Jeffries, R.: Strengthening the Case for Pair Programming. IEEE Software 17(4), 19-25 (2000)
4. Williams, L.A., Kessler, R.R.: All I really need to know about pair programming I learned in kindergarten. Communications of the ACM 43(5), 108-114 (2000)
5. Arisholm, E., Gallis, H., Dybâ, T., Sjøberg, D.I.K.: Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise. IEEE Transactions on Software Engineering 33(2) 65-86 (2007)
6. Beck, K.: Test Driven Development: By Example. Addison-Wesley, London (2002)
7. Kobayashi, O., Kawabata, M., Sakai, M., Parkinson, E.: Analysis of the Interaction between Practices for Introducing XP Effectively. In: ICSE '06: Proceeding of the 28th International Conference on Software Engineering, New York, NY, USA, ACM Press, pp. 544-550 (2006)
8. Marick, B.: How to Misuse Code Coverage. In: Proceedings of the 16th International Conference on Testing Computer Software (1999), http://www. testing.com/writings/coverage.pdf
9. Kaner, C.: Software Negligence and Testing Coverage. In: STAR 96: Proceedings the 5th International Conference, Software Testing, Analysis and Review, pp. 299-327 (1996)
10. Cai, X., Lyu, M.R.: The Effect of Code Coverage on Fault Detection under Different Testing Profiles. SIGSOFT Softw. Eng. Notes 30(4), 1-7 (2005)
11. Cornett, S.: Code Coverage Analysis (Retrieved 2006), http://www.bullseye.com/coverage.html
12. DeMillo, R.A., Lipton, R.J., Sayward, F.G.: Hints on Test Data Selection: Help for the Practicing Programmer. IEEE Computer 11(4), 34-41 (1978)
13. Hamlet, R.G.: Testing Programs with the Aid of a Compiler. IEEE Transactions on Software Engineering 3(4), 279-290 (1977)
14. Offutt, A.J., Untch, R.H.: Mutation 2000: Uniting the Orthogonal. In: Mutation testing for the new century, pp. 34-44. Kluwer Academic Publishers, Norwell, MA, USA (2001)
15. Zhu, H., Hall, P.A.V., May, J.H.R.: Software Unit Test Coverage and Adequacy. ACM Computing Surveys 29(4), 366-427 (1997)
16. Walsh, P.J.: A Measure of Test Case Completeness. PhD thesis, Univ. New York (1985)
17. Frankl, P.G., Weiss, S.N., Hu, C.: All-Uses vs Mutation Testing: An Experimental Comparison of Effectiveness. Journal of Systems and Software 38(3), 235-253 (1997)
18. Offutt, A.J., Pan, J., Tewary, K., Zhang, T.: An Experimental Evaluation of Data Flow and Mutation Testing. Software Practice and Experience 26(2), 165-176 (1996)
19. Venners, B.: Test-Driven Development. A Conversation with Martin Fowler, Part V (Retrieved 2007), http://www.artima.com/intv/testdrivenP.html
20. Moore, I.: Jester a JUnit test tester. In: Marchesi, M., Succi, G. (eds.) XP 2001: Proceedings of the 2nd International Conference on Extreme Programming and Flexible Processes in Software Engineering pp. 84-87 (2001)
21. Gamma, E., Beck, K.: JUnit Project Home Page (Retrieved 2006), http://www.junit.org/
22. Offutt, J., Ma, Y.S., Kwon, Y.R.: An Experimental Mutation System for Java. SIGSOFT Software Engineering Notes 29(5), 1-4 (2004)
23. Ma, Y.S., Offutt, J., Kwon, Y.R.: MuJava: A Mutation System for Java. In: ICSE '06: Proceeding of the 28th International Conference on Software Engineering, New York, NY, USA, pp. 827-830. ACM Press, New York (2006)
24. Chevalley, P., Thévenod-Fosse, P.: A mutation analysis tool for Java programs. International Journal on Software Tools for Technology Transfer (STTT) 5(1), 90-103 (2003)
25. Madeyski, L., Radyk, N.: Judy mutation testing tool project (Retrieved 2007), http://www.e-informatyka.pl/sens/Wiki. jsp?page=Projects.Judy
26. Offutt, A.J., Lee, A., Rothermel, G., Untch, R.H., Zapf, C.: An Experimental Determination of Sufficient Mutant Operators. ACM Transactions on Software Engineering and Methodology 5(2), 99-118 (1996)
27. Ammann, P., Offutt, J.: Introduction to Software Testing. (In progress) (2008)
28. Ma, Y.S., Harrold, M. J., Kwon, Y.R.: Evaluation of Mutation Testing for ObjectOriented Programs. In: ICSE '06: Proceeding of the 28th International Conference on Software Engineering, New York, NY, USA, pp. 869-872. ACM Press, New York (2006)
29. Nosek, J.T.: The Case for Collaborative Programming. Communications of the ACM 41(3), 105-108 (1998)
30. Nawrocki, J.R., Wojciechowski, A.: Experimental Evaluation of Pair Programming. In: ESCOM '01: European Software Control and Metrics, pp. 269-276 (2001)
31. Nawrocki, J.R., Jasiòski, M., Olek, L., Lange, B.: Pair Programming vs. Sideby-Side Programming. In: Richardson, I., Abrahamsson, P., Messnarz, R. (eds.) EuroSPI 2005. LNCS, vol. 3792, pp. 28-38. Springer, Heidelberg (2005)
32. Hulkko, H., Abrahamsson, P.: A Multiple Case Study on the Impact of Pair Programming on Product Quality. In: Inverardi, P., Jazayeri, M. (eds.) ICSE 2005, pp. 495-504. ACM Press, New York (2006)
33. Müller, M.M.: Are Reviews an Alternative to Pair Programming? Empirical Software Engineering 9(4), 335-351 (2004)
34. Madeyski, L.: Preliminary Analysis of the Effects of Pair Programming and TestDriven Development on the External Code Quality. In: Zieliáski, K., Szmuc, T. (eds.) Software Engineering: Evolution and Emerging Technologies Frontiers in Artificial Intelligence and Applications. Frontiers in Artificial Intelligence and Applications, vol. 130, pp. 113-123. IOS Press, Amsterdam (2005)
35. Madeyski, L.: The Impact of Pair Programming and Test-Driven Development on Package Dependencies in Object-Oriented Design -An Experiment. In: Munch, J., Vierimaa, M. (eds.) PROFES 2006. LNCS, vol. 4034, pp. 278-289. Springer, Heidelberg (2006)
36. Wohlin, C., Runeson, P., Host, M., Ohlsson, M.C., Regnell, B., Wesslén, A.: Experimentation in Software Engineering: An Introduction. Kluwer Academic Publishers, Norwell, MA, USA (2000)
37. Madeyski, L.: Is External Code Quality Correlated with Programming Experience or Feelgood Factor? In: Abrahamsson, P., Marchesi, M., Succi, G. (eds.) XP 2006. LNCS, vol. 4044, pp. 65-74. Springer, Heidelberg (2006)
38. Shadish, W.R., Cook, T.D., Campbell, D.T.: Experimental and QuasiExperimental Designs for Generalized Causal Inference. Houghton Mifflin (2002)
39. Cenqua Pty Ltd: Clover project (Retrieved 2006), http://www.cenqua.com/ clover/
40. Cook, T.D., Campbell, D.T.: Quasi-Experimentation: Design and Analysis Issues. Houghton Mifflin Company (1979)
41. Sørumgard, L.S.: Verification of Process Conformance in Empirical Studies of Software Development. PhD thesis, The Norwegian University of Science and Technology (1997)
42. Kitchenham, B., Pfleeger, S.L., Pickard, L., Jones, P., Hoaglin, D.C., Emam, K.E., Rosenberg, J.: Preliminary Guidelines for Empirical Research in Software Engineering. IEEE Transactions on Software Engineering 28(8), 721-734 (2002)
43. Host, M., Regnell, B., Wohlin, C.: Using Students as Subjects -A Comparative Study of Students and Professionals in Lead-Time Impact Assessment. Empirical Software Engineering 5(3), 201-214 (2000)
44. Tichy, W.F.: Hints for Reviewing Empirical Work in Software Engineering. Empirical Software Engineering 5(4), 309-312 (2000)
45. American Psychological Association: Publication manual of the American Psychological Association (2001)