Abstract
Composite services evolve for various reasons. Test case selection in the regression testing is an effective technique to ensure the correctness of modified versions meanwhile to reduce the cost of testing. However, few work has studied the test case selection problem based on the data flow testing criteria. In addition, there are three observable kinds of changes during the evolution, including Process change, Binding change and Interface change, which all bring impact to the data flow. To address these issues, a test case selection approach is proposed for regression testing of BPEL (Business Process Execution Language) composite service where all-uses criterion is satisfied and all the three change types are involved. BPEL composite service is modeled with a two-level model in which XCFG (eXtended Control Flow Graph) describes the behavior of BPEL process in the first level and WSDM (Web Service Description Model) depicts the interface information of composite service and partner services in the second level. Change impact analysis is performed to identify the affected definition-use pairs by comparing and analyzing two-level models of the baseline and evolved versions. And testing paths are generated to cover the affected definition-use pairs and select test cases based on the path condition analysis. Empirical result shows that the proposed approach is effective.
Highlights
With the development of cloud computing, service-oriented workflow has become a mainstream application to offer more complicated functions [1]
In order to perform change impact analysis on composite service rather than just the process, we propose the two-level model, which is composed of the revised XCFG and WSDMs
We proposed an all-use criterion based test case selection approach for BPEL composite service
Summary
With the development of cloud computing, service-oriented workflow has become a mainstream application to offer more complicated functions [1]. The rest of the paper is organized as follows: Section 2 introduces WSDL (Web Service Description Language) and BPEL and gives a motivating example used to illustrate our idea; Section 3 introduces the classifications of composite service evolution and the impact types they bring to the data flow, and gives an overview of our approach; Section 4 illustrates the definition and construction of the two-level model for describing BPEL composite service; Section 5 discusses how to identify the affected def-use pairs by change impact analysis; Section 6 discusses how to performs test case selection for the affected def-use pairs; Section 7 performs some experiment and evaluation of our approach using the motivating example and its four modified versions; Section 8 compares the related works; Section 9 concludes the paper
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
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 callDisclaimer: 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.
