Ordering broken unit tests for focused debugging

IEEE International Conference on Software Maintenance, ICSM

Volumn , Issue , 2004, Pages 114-123

  Gälli, Markus ^a   Lanza, Michele ^a   Nierstrasz, Oscar ^a   Wuyts, Roel ^b  

^a UNIVERSITY OF BERN   (Switzerland)

^b UNIVERSITÉ LIBRE DE BRUXELLES   (Belgium)

Author keywords

Debugging; Unit testing

Indexed keywords

DEBUGGING; DEBUGGING PHASES; SOFTWARE DEVELOPERS; UNIT TESTING;

ERROR DETECTION; FAILURE ANALYSIS; HIERARCHICAL SYSTEMS; JAVA PROGRAMMING LANGUAGE; PROBLEM SOLVING; SOFTWARE ENGINEERING;

PROGRAM DEBUGGING;

EID: 18044377224     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (20)

1. K. Beck. Test Driven Development: By Example. Addison-Wesley, 2003.
2. K. Beck and E. Gamma. Test infected: Programmers love writing tests. Java Report, 3(7):51-56, 1998.
3. J. Bible, G. Rothermel, and D. Rosenblum. A comparative study of coarse- and fine-grained safe regression test selection. ACM TOSEM, 10(2): 149-183, Apr. 2001.
4. J. Brant, B. Foote, R. Johnson, and D. Roberts. Wrappers to the Rescue. In Proceedings ECOOP '98, volume 1445 of LNCS, pages 396-417. Springer-Verlag, 1998.
5. H. Cleve and A. Zeller. Finding failure causes through automated testing. In Proceedings of the Fourth International Workshop on Automated Debugging, Aug. 2000.
6. S. Ducasse, M. Lanza, and S. Tichelaar. The moose reengineering environment. Smalltalk Chronicles, Aug. 2001.
7. S. G. Elbaum, A. G. Malishevsky, and G. Rothermel. Prioritizing test cases for regression testing. In International Symposium on Software Testing and Analysis, pages 102-112. ACM Press, 2000.
8. T. Gîrba, S. Ducasse, and M. Lanza. Yesterday's weather: Guiding early reverse engineering efforts by summarizing the evolution of changes. In 20th International Conference on Software Maintenance (ICSM 2004), 2004.
9. R. Hirschfeld. Aspects - aspect-oriented programming with squeak. In M. Aksit, M. Mezini, and R. Unland, editors, Objects, Components, Architectures, Services, and Applications for a Networked World, International Conference NetObjectDays 2002, pages 216-232, Erfurt, 2003. Springer.
10. D. Ingalls, T. Kaehler, J. Maloney, S. Wallace, and A. Kay. Back to the future: The story of Squeak, A practical Smalltalk written in itself. In Proceedings OOPSLA '97, pages 318-326. ACM Press, Nov. 1997.
11. G. Kiczales, E. Hilsdale, J. Hugunin, M. Kersten, J. Palm, and W. G. Griswold. An overview of AspectJ. In Proceeding ECOOP 2001, 2001.
12. M. Lanza. Codecrawler - lessons learned in building a software visualization tool. In Proceedings of CSMR 2003, pages 409-418. IEEE Press, 2003.
13. I. Moore. Jester - a junit test tester. In M. Marchesi, editor, Proceedings of the 2nd International Conference on Extreme Programming and Flexible Processes (XP2001). University of Cagliari, 2001.
14. A. Parrish, J. Jones, and B. Dixon. Extreme unit testing: Ordering test cases to maximize early testing. In M. Marchesi, G. Succi, D. Wells, and L. Williams, editors, Extreme Programming Perspectives, pages 123-140. Addison-Wesley, 2002.
15. L. Renggli. Smallwiki: Collaborative content management. Informatikprojekt, University of Bern, 2003.
16. G. Rothermel, S. Elbaum, A. Malishevsky, P. Kallakuri, and B. Davia. The impact of test suite granularity on the cost-effectiveness of regression testing. In Proceedings ICSE-24, pages 230-240, May 2002.
17. G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8):529-551, 1996.
18. G. Rothermel, R. H. Untch, C. Chu, and M. J. Harrold. Test case prioritization: An empirical study. In Proceedings ICSM 1999, pages 179-188, Sept. 1999.
19. W. E. Wong, J. R. Horgan, S. London, and H. Agrawal. A study of effective regression testing in practice. In Proceedings of the Eighth International Symposium on Software Reliability Engineering, pages 230-238, Nov. 1997.
20. A. Zeller and R. Hildebrandt. Simplifying and isolating failure-inducing input. IEEE Transactions on Software Engineering, SE-28(2): 183-200, Feb. 2002.