Project Members: Animesh Chaturvedi, Prof. Atul Gupta, and Prof. Dave Binkley

Changeability and evolvability analysis can aid an engineer tasked with a maintenance or an evolution task. This article applies change mining and evolution mining to evolving distributed systems. First, we propose a Service Change Classifier based Interface Slicing algorithm that mines change information from two versions of an evolving distributed system. To compare old and new versions, the following change classification labels are used: inserted, deleted, and modified. These labels are then used to identify subsets of the operations in our newly proposed Interface (WSDL) Slicing algorithm. Second, we proposed four Service Evolution Metrics that capture the evolution of a system’s Version Series VS = {V1, V2,…,VN}. Combined the two form the basis of our proposed Service Evolution Analytics model, which includes learning during its development phase. We prototyped the model in an intelligent tool named AWSCM (Automatic Web Service Change Management). Finally, we present results from experiments with two well-known cloud services: Elastic Compute Cloud (EC2) from the Amazon Web Service (AWS), and Cluster Controller (CC) from Eucalyptus. These experiments demonstrate AWSCM’s ability to exploit change and evolution mining.

We introduce Web Service Slicing, a technique that captures a functional subset of a large-scale web service using an interface slice captured as a WSDL slice (a subset of a service’s WSDL). An interface (WSDL) slice provides access to an interoperable slice, which is a functional subset of the service’s code. The technique uses intra-operational and inter-operational analysis to identify web service changes. With the aid of an associative code-test mapping, we leverage the identification of affected operations to reduce the cost of web-service regression testing by extracting a subset of the existing test cases. Used in conjunction with a web service slice, this subset reduces the cost of web-service regression testing by enabling the running of fewer tests. Furthermore, we exploit two approaches: Operationalized Regression Testing of Web Services (ORTWS) and Parameterized Regression Testing of Web Services (PRTWS). ORTWS effectively tests intra-operational changes at the WSDL and WS-code levels, while PRTWS tests inter-operational changes involving inter-operational dependencies due to primary parameters. Finally, we present results obtained using our prototype implementation, AWSCM (Automatic Web Service Change Management), in two case-study experiments that serve to illustrate the reduction potential of the technique using eight real-world web services.

One of the primary goals in Web Service (WS) maintenance and evolution is to reduce the effort required to test the changes. Traditionally, functional and non-functional testing of WS is performed by testing the operations listed in WS Description Language (WSDL). Further, the regression testing is done by identifying the changes made to the WS code and the WSDL specification.

Web Service (WS) analyzer requires automated approach to write and select test cases, which are more reliable and relevant. Analyzer needs to categorize WS, so that cost can be reduced by organizing the test scenarios. Emphasis of analyzer is to create and handle subset of code i.e. slice the WS code, which reduces human efforts in regression testing and re-engineering.

Automated Web Service Change Management (AWSCM) is a tool which constructs Subset WSDL (or WSDL Slice) based on change impact analysis of WSDL and code. AWSCM visualizes and captures changes in the form of intermediate artifacts during impact analysis. This video will describe the computation of change impact as well as mapping them to their test cases. We will see the construction of Subset WSDLs and reduce regression test suite. Automated Web Service Change Management (AWSCM) is a prototype tool, which is described as follows. 

Proposed terminologies:

• Difference WSDL (DWSDL): Difference WSDL feature takes two inputs: new and old version WSDL. AWSCM gathers operations that have undergone changes to construct DWSDL.

• Reduce WSDL (RWSDL): Reduce WSDL feature takes any WSDL as input to gather its operations, and then ask the user to select operations. Selected operations are used to construct the RWSDL.

• Unit WSDL (UWSDL): Unit WSDL feature takes three inputs: new, old  version code of operations and new version of WSDL. UWSDL is constructed according to the semantics of new version of WSDL with the operations that have gone through changes at the code level.

• Combined WSDL (CWSDL): Combined WSDL is constructed with the operations in (D/R/U) WSDL such that it contains only unique and non-redundant operations.

• Parameter WSDL (PWSDL): Parameter WSDL is constructed with the operations whose inter-procedure called operations/methods are affected from changes such that their called method, functions, and class have undergone changes. Inter-procedural called operations/methods can also be part of other WS i.e. this is also applicable in WS composition.

Tool requires JRE (1.4-1.7) and Window 7. The project was developed and experimented during 2011-2020.  There are following GitHub projects.

https://github.com/animesh88/WebServiceSlicing-ORTWS-PRTWS

https://github.com/animesh88/ServiceEvolutionAnalytics 

https://github.com/animesh88/ServiceEvolutionAnalytics 

https://github.com/animesh88/JMeterRTWS 

https://github.com/animesh88/SaaS 

Thesis: Animesh, Chaturvedi "Change Impact Analysis Based Regression Testing of Web Services" Cornell University Library arXiv preprint arXiv:1408.1600 (2014).  Download PDF.

1. DifferenceWSDL of AWSCM for EucalyptusCC

2. ReduceWSDL of AWSCM for Amazon WSDL

3. UnitWSDL  of  AWSCM  for  SaaS  operations  (editFile  and  Searching) modified at code to construct RRTS for JMeter old TS

4. Combined WSDL to construct RRTS for SaaS_3

5. AWSCM for construct RRTS of ‘BookService’ for operation ‘GetAbstractofChapter’

6.  Snapshot of prototype tool PRTWS for user selective test sequence/step inside test cases for a test suite of currency conversion.