Abstract

To efficiently search for defects, system testing can be conducted when a single system function is developed. Finding defects at an early stage of work can reduce cost and time of the rework. In order to conduct testing while there are incomplete classes in a system, stubs and drivers are introduced to temporarily replace incomplete classes. Development of stubs and drivers can take time and effort as a result testers usually try to use tools to mitigate them. Luengruengroj and Suwannasart [1] proposed an automated stubs-and-drivers generator. However, their generator aimed to help testers during integration testing. Our study presents an approach to generate stubs and drivers for system testing. Our approach uses a class diagram, sequence diagrams, and a Requirements Traceability Matrix as input. Class diagram is used to indicate classes’ attributes and create a list of method signatures. Whereas sequence diagrams are used to indicate interaction between objects and produce a call graph. In addition, our approach uses the Requirements Traceability Matrix to discover system functions. After a call graph and the method signatures are extracted, they are used to generate classes of stubs and drivers along with test input values. Consequently, stubs and drivers are exported for system testing.

Full Text
Published version (Free)

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