US 10,503,632 B1Granted

Impact analysis for software testing

AssigneeAmazon Technologies, Inc.

InventorsSudhakar Sivanantham, Shweta Pednekar, Aaron Tang

Life of this patent

Estimating the term…

Loading patent…

Abstract

Devices and methods are provided for providing software developer-driven analysis for the expected impact that a proposed software modification may have on software programs and devices. A device may receive files including a first file including indications of: (i) a feature modified by one or more software modifications, (ii) a sub-feature associated with the feature and modified by the one or more software modifications, and (iii) first information associated with the feature, and a second file including indications of: (i) the feature, (ii) the sub-feature, and (iii) second information associated with the feature. The device may determine a record including indications of: (i) the feature, (ii) the sub-feature, (iii) the first information, and (iv) the second information. The device may determine a test plan including one or more tests performed based on the record. The device may execute at least a portion of the test plan.

Claims20

Dependent claims

A method, comprising:

receiving, at a first device, a first JIRA file including indications of a first software program and a first device type associated with executing the first software program, wherein the first JIRA file indicates that the first software program includes a first user interface software modification;
receiving a second JIRA file including an indication that the first software program includes a second user interface software modification;
receiving a third JIRA file indicating a second software program and a second device type associated with executing the second software program, wherein the second JIRA file indicates that the second software program includes a parental control software modification;
generating a list of received JIRA files including the first JIRA file, the second JIRA file, and the third JIRA file;
determining a first impact analysis record indicative of JIRA files that include modifications impacting the first software program, the first impact analysis record including indications of the first user interface software modification and the second user interface software modification;
determining a second impact analysis record indicative of JIRA files that include modifications impacting the second software program;
determining a user interface compatibility test program based on the first impact analysis record, wherein the user interface compatibility test program includes one or more tests to be performed on the first software program;
determining a parental control compatibility test program based on the second impact analysis record, wherein the parental control test program includes one or more tests to be performed on the second software program;
executing the user interface compatibility test program;
determining, based on output of the user interface compatibility test program, that the first user interface software modification is compatible with the first software program and the first device type;
executing the parental control compatibility test program;
and
determining, based on output of the parental control compatibility test program, that the parental control software modification is compatible with the second software program and the second device type.

10 more elements

A device comprising memory and at least one processor, the at least one processor configured to:

receive two or more files associated with one or more software modifications, the two or more files including:
a first file including indications of:
(i) first modifications to a software feature by the one or more software modifications, (ii) first modifications to a software sub-feature by the one or more software modifications, and (iii) a first device type associated with the one or more software modifications;
and
a second file including indications of:
(i) second modifications to the software feature by the one or more software modifications, (ii) second modifications to the software sub-feature by the one or more software modifications, and (iii) a second device type associated with the one or more software modifications;
determine a record based on the first file and the second file, wherein the record includes indications of:
(i) the software feature, (ii) the software sub-feature, (iii) the first device type, and (iv) the second device type;
determine a test plan, based on the record, wherein the test plan includes one or more computer-executable software tests performed on the software feature;
and
execute at least a portion of the test plan.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/146,648Filed 28 Sep 2018
Granted: 10 Dec 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification6 codes

G06F 11/3698
Prevention of errors by analysis, debugging or testing of software: environments for analysis, debugging or testing of software
G06F 11/3608
Analysis of software for verifying properties of programs: using formal methods, e.g. model checking, abstract interpretation
G06F 11/3684
Test management: for test design, e.g. generating new test cases
G06F 11/3688
Test management: for test execution, e.g. scheduling of test suites

Family

No related US applications are recorded in the indexed filing history.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key