Developing an object-oriented software testing and maintenance environment
Communications of the ACM - Special issue on object-oriented experiences and future trends
A safe, efficient regression test selection technique
ACM Transactions on Software Engineering and Methodology (TOSEM)
A technique for the selective revalidation of OO software
Journal of Software Maintenance: Research and Practice
Corrective maintenance maturity model (CM3): maintainer's education and training
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Executable UML: A Foundation for Model-Driven Architectures
Executable UML: A Foundation for Model-Driven Architectures
Computer
Integrating White- and Black-Box Techniques for Class-Level Regression Testing
COMPSAC '01 Proceedings of the 25th International Computer Software and Applications Conference on Invigorating Software Development
Specification-based regression test selection with risk analysis
CASCON '02 Proceedings of the 2002 conference of the Centre for Advanced Studies on Collaborative research
Testing of Object-Oriented Programs Based on Finite State Machines
APSEC '95 Proceedings of the Second Asia Pacific Software Engineering Conference
Maintaining Evolving Component-Based Software with UML
CSMR '03 Proceedings of the Seventh European Conference on Software Maintenance and Reengineering
Automating Impact Analysis and Regression Test Selection Based on UML Designs
ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
Model Based Regression Test Reduction Using Dependence Analysis
ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
Regression Test Selection Based on Version Changes of Components
APSEC '03 Proceedings of the Tenth Asia-Pacific Software Engineering Conference Software Engineering Conference
Model-Based Testing and Maintenance
ISMSE '04 Proceedings of the IEEE Sixth International Symposium on Multimedia Software Engineering
Regression Testing of Classes Based on TCOZ Specification
ICECCS '05 Proceedings of the 10th IEEE International Conference on Engineering of Complex Computer Systems
On OO Design Consistency in Iterative Development
ITNG '06 Proceedings of the Third International Conference on Information Technology: New Generations
Automated impact analysis of UML models
Journal of Systems and Software
Regression Testing UML Designs
ICSM '06 Proceedings of the 22nd IEEE International Conference on Software Maintenance
Regression test selection for c# programs
Advances in Software Engineering
Evolution of security requirements tests for service-centric systems
ESSoS'11 Proceedings of the Third international conference on Engineering secure software and systems
Analysis of model based regression testing approaches
ACELAE'11 Proceedings of the 10th WSEAS international conference on communications, electrical & computer engineering, and 9th WSEAS international conference on Applied electromagnetics, wireless and optical communications
Regression testing minimization, selection and prioritization: a survey
Software Testing, Verification & Reliability
Regression test suite prioritization using system models
Software Testing, Verification & Reliability
Hi-index | 0.00 |
Model-based regression testing is an important activity that ensures the reliability of evolving software. One of the major issues in this type of testing is the optimal selection of test-cases to test the affected portion of the software. In this paper, we present a UML based selective regression testing strategy that uses state machines and class diagrams for change identification. We identify the changes using the UML 2.1 semantics of state machines and class diagram. The changes are classified as Class-driven (obtained from class diagram) and State-driven (obtained from state machine). The Class-driven changes are important as these changes are not reflected on the state machines and they might be helpful in identifying some fault-revealing test cases. With the help of the identified changes, we classify the test cases of the test suite as Obsolete, Reusable, and Retestable. We apply the approach on a case study to demonstrate its validity.