Abstract

The software requirements are modelled using UML state machine diagram and UML sequence diagram. The different features of both the diagrams are combined and an intermediate graph, i.e., state sequence graph (SSG) is generated. The affected nodes, due to different changes in the past versions of the applications are stored for further analysis. Whenever, a new version of the software is developed, and it is under regression testing, test scenario prioritisation is carried out by finding the frequent pattern from the stored modification history. Different other factors like number of message passing, number of state changes etc. also contribute in prioritising the test cases. The proposed approach is applied on different case studies and the results are recorded. This approach is found to be very efficient when evaluated using prioritisation metric and compared with other related work.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.