Adaptive software testing

US10846206B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10846206-B2
Application numberUS-201715622851-A
CountryUS
Kind codeB2
Filing dateJun 14, 2017
Priority dateJun 14, 2017
Publication dateNov 24, 2020
Grant dateNov 24, 2020

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

In a software testing environment, a test script may be designed to search among outputs of an in-test target application for an expected output element having a specified property. A test execution engine executes the test script, and if such an output is not found, and the test script returns a “fail” result, the test execution engine revises the test script so that rather than searching for the originally specified property, the test script searches for a different property, where the different property is a property that the expected output element was observed to have during a previous execution of the test script. The test execution engine then executes the revised test script and reports its results.

First claim

Opening claim text (preview).

What is claimed is: 1. A method, comprising: obtaining a test script for a test case, wherein the test script is configured to (a) simulate user input to a target application, resulting in one or more application output elements, and (b) attempt to find an expected output element, among the one or more application output elements, that has a first property associated with a content of the expected output element; executing the test script against the target application to cause the target application to produce the one or more application output elements, wherein the test script is unable to find the expected output element among the one or more application output elements; determining whether the first property is a critical property; and if the first property is not a critical property then: identifying a second property, associated with the content of the expected output element, that the expected output element had during a previous execution of the test script, wherein the second property is different than the first property; revising the test script so that a revised test script attempts to find the expected output element by identifying one of the one or more application output elements that has the second property, wherein the revised test script comprises the second property; and executing the revised test script against the target application, wherein the revised test script is able to find the expected output element among the one or more application output elements. 2. The method of claim 1 , further comprising recording one or more additional properties, other than the first property, that the expected output element had during the previous execution of the test script, wherein the second property is one of the one or more additional properties. 3. The method of claim 1 , wherein identifying the second property comprises selecting the second property from among one or more additional properties, associated with the content of the expected output element, that the expected output element had during the previous execution of the test script. 4. The method of claim 3 , wherein the expected output element is a user interface element and the one or more additional properties include any one or more of the following properties associated with the content of the user interface element: content of the interface element; an output value of the interface element; a color of the interface element; text presented by the interface element; help text presented by the interface element; possible user selections that are available in the interface element; an icon presented by the interface element; a context menu presented by the interface element; a control presented by interface element; a default input value of the interface element; or a resource associated with the interface element. 5. The method of claim 1 , wherein the second property comprises a name or programmatic identifier that the expected output element had during the previous execution of the test script. 6. The method of claim 1 , wherein the second property comprises content of the expected output element during the previous execution of the test script. 7. The method of claim 1 , and further comprising: if the first property is a critical property then reporting a fail result for the test case. 8. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform actions comprising: obtaining a test script for a test case, wherein the test script is configured to attempt to find an expected output element, among one or more application output elements, that has a first property associated with a content of the expected output element; executing the test script, wherein the test script is unable to find the expected output element among the one or more application output elements; determining whether the first property is a critical property; and if the first property is not a critical property then: revising the test script so that it attempts to find the expected output element by identifying one of the one or more application output elements that has a second property associated with the content of the expected output element and that the content of the expected output element had during a previous execution of the test script, wherein the revised test script comprises the second property. 9. The one or more non-transitory computer-readable media of claim 8 , the actions further comprising recording one or more additional properties, other than the first property, of the expected output element during the previous execution of the test script, wherein the second property is one of the one or more additional properties. 10. The one or more non-transitory computer-readable media of claim 8 , wherein: the expected output element is a user interface element; the first property comprises a programmatic identifier of the user interface element; and the second property comprises a name that was associated with the content of the user interface element during a previous execution of the test script. 11. The one or more non-transitory computer-readable media of claim 8 , wherein the second property comprises content that the expected output element had during a previous execution of the test script. 12. The one or more non-transitory computer-readable media of claim 8 , the actions further comprising selecting the second property from among one or more additional properties that the expected output element had during the previous execution of the test script. 13. The one or more non-transitory computer-readable media of claim 12 , wherein the expected output element is a user interface element and the one or more additional properties include any one or more of the following properties associated with the content of the user interface element: content of the interface element; an output value of the interface element; a color of the interface element; text presented by the interface element; help text presented by the interface element; possible user selections that are available in the interface element; an icon presented by the interface element; a context menu presented by the interface element; a control presented by interface element; a default input value of the interface element; or a resource associated with the interface element. 14. The one or more non-transitory computer-readable media of claim 8 wherein, if the first property is a critical property, the actions further comprise: reporting a fail result for the test case. 15. A method, comprising: obtaining a test script for a test case, wherein the test script is configured to (a) provide input to a target application, resulting in one or more application output elements, and (b) attempt to find an expected output element, among the one or more application output elements, that has a first property associated with a content of the expected output element; executing the test script against the target application to cause the target application to produce the one or more application output elements, wherein the test script is unable to find the expected output element among the one or more application output elements; determining whether the first property is a critical property; and if the first property is not a critical property then: determining that a particular output element, among the one or more application output elements, is the expected output element, wherein the particular output element has a second proper

Assignees

Inventors

Classifications

  • Environments for analysis, debugging or testing of software · CPC title

  • for test execution, e.g. scheduling of test suites · CPC title

  • for test design, e.g. generating new test cases · CPC title

  • Physics · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10846206B2 cover?
In a software testing environment, a test script may be designed to search among outputs of an in-test target application for an expected output element having a specified property. A test execution engine executes the test script, and if such an output is not found, and the test script returns a “fail” result, the test execution engine revises the test script so that rather than searching for …
Who is the assignee on this patent?
T Mobile Usa Inc
What technology area does this patent fall under?
Primary CPC classification G06F11/3688. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Nov 24 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).