ADOPTING AN EXISTING AUTOMATION SCRIPT TO A NEW FRAMEWORK

• US 20150074646A1
• Filed: 09/30/2013
• Published: 03/12/2015
• Est. Priority Date: 09/10/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mehra, Maneesh, Herrin, Bradley C.
• Granted Patent: US 9,411,711 B2
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3668 Software testing software testing in telephone exchanges H04M3/242, testing of hardware G06F11/22
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Arrangements described herein relate to adopting an existing automation script to a new framework. A first version of an automation script configured to execute in a first framework, and expected unit test results for the automation script, are received. A second version of the automation script is created from the first version of the automation script. The second version of the automation script is configured to execute in at least a second framework. The first version of the automation script is executed in the first framework to run a first version of a unit test and the second version of the automation script is executed in the second framework to run a second version of the unit test. Results generated by execution of the first and second versions of the automation script are analyzed to validate the second version of the automation script.

Claims

1. A system comprising:

a processor programmed to initiate executable operations comprising;

receiving a first version of an automation script configured to execute in a first framework and expected unit test results for the automation script;

automatically creating a second version of the automation script from the first version of the automation script, the second version of the automation script configured to execute in at least a second framework;

executing the first version of the automation script in the first framework to run a first version of a unit test and executing the second version of the automation script in the second framework to run a second version of the unit test;

comparing at least a first output generated by the first version of the automation script running the first version of the unit test and at least a second output generated by the second version of the automation script running the second version of the unit test to at least one expected unit test result to determine whether the first output and the second output correlate with the expected unit test result; and

responsive at least to the first output and the second output correlating with the expected unit test result, determining the second version of the automation script is valid.

2. The system of claim 1, the executable operations further comprising:

automatically creating the second version of the unit test from the first version of the unit test.

3. The system of claim 2, the executable operations further comprising:

responsive to determining the second version of the automation script is valid, outputting the second version of the automation script and the second version of the unit test.

4. The system of claim 1, wherein:

execution of the first version of the automation script in the first framework to run the first version of the unit test generates a first plurality of outputs;

execution of the second version of the automation script in the second framework to run the second version of the unit test generates a second plurality of outputs;

executing the first version of the automation script in the first framework to run the first version of the unit test and executing the second version of the automation script in the second framework to run the second version of the unit test comprises;

executing the first version of the automation script and executing the second version of the automation script in parallel; and

comparing at least the first output generated by the first version of the automation script running the first version of the unit test and at least the second output generated by the second version of the automation script running the second version of the unit test to at least one expected unit test result to determine whether the first output and the second output correlate with the expected unit test result comprises;

comparing each sequential one of the first plurality of outputs and a corresponding one of the second plurality of outputs to the expected unit test result as output pairs.

5. The system of claim 4, the executable operations further comprising:

when at least one output in a particular output pair does not correlate with the expected unit test result, identifying code in the first version of the automation script and code in the second version of the automation script that generate the respective outputs in the output pair.

6. The system of claim 1, the executable operations further comprising:

capturing a first state of a first system hosting the first framework post execution of the first version of the automation script;

capturing a second state of a second system hosting the second framework post execution of the second version of the automation script; and

comparing the second state of the second system to the first state of the first system to determine whether the second state correlates with the first state;

wherein determining the second version of the automation script is valid further is responsive to the second state correlating with the first state.

7. The system of claim 1, wherein the second version of the automation script is configured to execute in a plurality of frameworks.

8. A computer program product comprising a computer readable storage medium having program code stored thereon, the program code executable by a processor to perform a method comprising:

receiving, by the processor, a first version of an automation script configured to execute in a first framework and expected unit test results for the automation script;

automatically creating, by the processor, a second version of the automation script from the first version of the automation script, the second version of the automation script configured to execute in at least a second framework;

executing, by the processor, the first version of the automation script in the first framework to run a first version of a unit test and executing the second version of the automation script in the second framework to run a second version of the unit test;

comparing, by the processor, at least a first output generated by the first version of the automation script running the first version of the unit test and at least a second output generated by the second version of the automation script running the second version of the unit test to at least one expected unit test result to determine whether the first output and the second output correlate with the expected unit test result; and

responsive at least to the first output and the second output correlating with the expected unit test result, determining, by the processor, the second version of the automation script is valid.

9. The computer program product of claim 8, the method further comprising:

automatically creating the second version of the unit test from the first version of the unit test.

10. The computer program product of claim 9, the method further comprising:

responsive to determining the second version of the automation script is valid, outputting the second version of the automation script and the second version of the unit test.

11. The computer program product of claim 8, wherein:

execution of the first version of the automation script in the first framework to run the first version of the unit test generates a first plurality of outputs;

execution of the second version of the automation script in the second framework to run the second version of the unit test generates a second plurality of outputs;

executing the first version of the automation script in the first framework to run the first version of the unit test and executing the second version of the automation script in the second framework to run the second version of the unit test comprises;

executing the first version of the automation script and executing the second version of the automation script in parallel; and

comparing at least the first output generated by the first version of the automation script running the first version of the unit test and at least the second output generated by the second version of the automation script running the second version of the unit test to at least one expected unit test result to determine whether the first output and the second output correlate with the expected unit test result comprises;

comparing each sequential one of the first plurality of outputs and a corresponding one of the second plurality of outputs to the expected unit test result as output pairs.

12. The computer program product of claim 11, the method further comprising:

when at least one output in a particular output pair does not correlate with the expected unit test result, identifying code in the first version of the automation script and code in the second version of the automation script that generate the respective outputs in the output pair.

13. The computer program product of claim 8, the method further comprising:

capturing a first state of a first system hosting the first framework post execution of the first version of the automation script;

capturing a second state of a second system hosting the second framework post execution of the second version of the automation script; and

comparing the second state of the second system to the first state of the first system to determine whether the second state correlates with the first state;

wherein determining the second version of the automation script is valid further is responsive to the second state correlating with the first state.

14. The computer program product of claim 8, wherein the second version of the automation script is configured to execute in a plurality of frameworks.