Managing Object-Oriented Integration and Regression Testing
Mario Winter

TL;DR
This paper addresses the complexity of testing object-oriented software by proposing a dependency diagram, algorithms, and coverage criteria to improve integration and regression testing strategies during development.
Contribution
It introduces a novel dependency diagram and algorithms for identifying effective integration and regression test cases in object-oriented software.
Findings
A diagram capturing object interactions and dependencies
Algorithms for test case selection after modifications
Practical heuristics for testing in object-oriented development
Abstract
Systematic testing of object-oriented software turned out to be much more complex than testing conventional software. Especially the highly incremental and iterative development cycle demands both many more changes and partially implemented resp. re-implemented classes. Much more integration and regression testing has to be done to reach stable stages during the development. In this presentation we propose a diagram capturing all possible dependencies and interactions in an object-oriented program. Then we give algorithms and coverage criteria to identify integration resp. regression test strategys and all test cases to be executed after some implementation resp. modification activities. Finally, we summarize some practical experiences and heuristics.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSoftware Testing and Debugging Techniques · Software Engineering Research · Software Reliability and Analysis Research
