Relay and metering test instrument
US-11886324-B2 · Jan 30, 2024 · US
US9411711B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9411711-B2 |
| Application number | US-201314042437-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 30, 2013 |
| Priority date | Sep 10, 2013 |
| Publication date | Aug 9, 2016 |
| Grant date | Aug 9, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 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; generating a first plurality of outputs by executing the first version of the automation script in the first framework to run a first version of a unit test and, in parallel with executing the first version of the automation script, generating a second plurality of outputs by executing the second version of the automation script in the second framework to run a second version of the unit test; comparing each sequential one of the first plurality of outputs generated by the first version of the automation script running the first version of the unit test and a corresponding one of the second plurality of outputs generated by the second version of the automation script running the second version of the unit test, as output pairs, 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 one output in a particular output pair not correlating 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. 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: outputting the second version of the automation script and the second version of the unit test. 4. 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. 5. The system of claim 1 , wherein the second version of the automation script is configured to execute in a plurality of frameworks. 6. 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; generating a first plurality of outputs by 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, in parallel with executing the first version of the automation script, generating a second plurality of outputs by 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, each sequential one of the first plurality of outputs generated by the first version of the automation script running the first version of the unit test and a corresponding one of the second plurality of outputs generated by the second version of the automation script running the second version of the unit test, as output pairs, 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 one output in a particular output pair not correlating with the expected unit test result, identifying, by the processor, 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. 7. The computer program product of claim 6 , the method further comprising: automatically creating the second version of the unit test from the first version of the unit test. 8. The computer program product of claim 7 , the method further comprising: outputting the second version of the automation script and the second version of the unit test. 9. The computer program product of claim 6 , 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. 10. The computer program product of claim 6 , wherein the second version of the automation script is configured to execute in a plurality of frameworks.
for test version control, e.g. updating test cases to a new software version · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
for test design, e.g. generating new test cases · CPC title
Testing of software · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.