Automated quality assurance testing of browser-based applications

Patent metadata

Field	Value
Publication number	US-9928161-B1
Application number	US-201615260247-A
Country	US
Kind code	B1
Filing date	Sep 8, 2016
Priority date	Sep 8, 2016
Publication date	Mar 27, 2018
Grant date	Mar 27, 2018

Abstract

Methods and apparatuses are described for intelligent automation of computer software test scripts and code requirements. A server generates a baseline test script for a plurality of browser-based applications with a sequence of action steps having one or more empty user interface component values. The server performs a first execution of the baseline test script against each of the browser-based applications to extract one or more expected values associated with user interface components that correspond to the empty user interface component values, and stores the expected values. The server performs a second execution of the baseline test script against the browser-based applications to extract one or more actual values associated with user interface components that correspond to the empty user interface component values. The server compares the actual values against the expected values, and if the values do not match, the server generates a message indicating a test failure.

First claim

What is claimed is:

1. A computerized method for automated quality assurance testing of browser-based applications, the method comprising:
generating, by a server computing device, a baseline test script for a plurality of browser-based applications, wherein the baseline test script comprises a sequence of action steps having one or more empty user interface component attribute values;
performing, by the server computing device, a first execution of the baseline test script in a learning mode against an intended version of each of the plurality of browser-based applications to extract, for the intended version of each browser-based application, one or more expected attribute values associated with user interface components in the intended version of the browser-based application that correspond to the empty user interface component attribute values in the baseline test script, the expected attribute values extracted from a code file of a webpage in the intended version of the browser-based application in which the user interface component is located;
storing, by the server computing device, the expected attribute values for each intended version of the browser-based applications in a repository;
performing, by the server computing device, a second execution of the baseline test script in a testing mode against an in-development version of each of the plurality of browser-based applications to extract, for each in-development version of the browser-based application, one or more actual attribute values associated with user interface components in the in-development version of the browser-based application that correspond to the empty user interface component attribute values in the baseline test script, the actual attribute values extracted from a code file of a webpage in the in-development version of the browser-based application in which the user interface component is located;
comparing, by the server computing device, the actual attribute values associated with user interface components in the in-development version of each browser-based application against the corresponding expected attribute values associated with user interface components in the intended version of the browser-based application; and
if one or more of the actual attribute values does not match one or more of the expected attribute values, generating, by the server computing device, a notification message indicating a test failure and transmitting the notification message to a remote computing device.

2. The method of claim 1 , wherein at least a portion of the intended version of the plurality of browser-based applications and at least a portion of the in-development version of the plurality of browser-based applications comprise one or more different layouts for a single browser software platform.

3. The method of claim 1 , wherein at least a portion of the intended version of the plurality of browser-based applications and at least a portion of the in-development version of the plurality of browser-based applications comprise one or more different browser software platforms executing on a single hardware platform.

4. The method of claim 1 , wherein the expected attribute values associated with user interface components comprise values corresponding to visual characteristics of the user interface components.

5. The method of claim 1 , wherein the expected attribute values associated with user interface components comprise values corresponding to positional characteristics of the user interface components.

6. The method of claim 1 , wherein the expected attribute values associated with user interface components comprise values associated with textual information within the user interface components.

7. The method of claim 1 , wherein the first execution of the baseline test script is performed before the second execution of the baseline test script.

8. The method of claim 1 , wherein when performing the first execution of the baseline test script and reaching an action step having an empty user interface component value, the server computing device recognizes a pattern in the code file of the webpage in the intended version of the browser-based application in which the user interface component is located and extracts the expected attribute values based upon the recognized pattern.

9. A system for automated quality assurance testing of browser-based applications, the system comprising a server computing device configured to:
generate a baseline test script for a plurality of browser-based applications, wherein the baseline test script comprises a sequence of action steps having one or more empty user interface component attribute values;
perform a first execution of the baseline test script in a learning mode against an intended version of each of the plurality of browser-based applications to extract, for the intended version of each browser-based application, one or more expected attribute values associated with user interface components in the intended version of the browser-based application that correspond to the empty user interface component attribute values in the baseline test script, the expected attribute values extracted from a code file of a webpage in the intended version of the browser-based application in which the user interface component is located;
store the expected attribute values for each intended version of the browser-based applications in a repository;
perform a second execution of the baseline test script in a testing mode against an in-development version of each of the plurality of browser-based applications to extract, for each in-development version of the browser-based application, one or more actual attribute values associated with user interface components in the in-development version of the browser-based application that correspond to the empty user interface component attribute values in the baseline test script, the actual attribute values extracted from a code file of a webpage in the in-development version of the browser-based application in which the user interface component is located;
compare the actual attribute values associated with user interface components in the in-development version of each browser-based application against the corresponding expected attribute values associated with user interface components in the intended version of the browser-based application; and
if one or more of the actual attribute values does not match one or more of the expected attribute values, generate a notification message indicating a test failure and transmitting the notification message to a remote computing device.

10. The system of claim 9 , wherein at least a portion of the intended version of the plurality of browser-based applications and at least a portion of the in-development version of the plurality of browser-based applications comprise one or more different browser software platforms executing on a single hardware platform.

11. The system of claim 9 , wherein at least a portion of the intended version of the plurality of browser-based applications and at least a portion of the in-development version of the plurality of browser-based applications comprise one or more different browser software platforms executing on a single hardware platform.

12. The system of claim 9 , wherein the expected attribute values associated with user interface components comprise values corresponding to visual characteristics of the user interface components.

13. The system of claim 9 , wherein the expected attribute values associated with user interface components comprise values corresponding to positional characteristics of the user interface components.

Assignees

• Fmr Llc

Inventors

• Costello Robert
• Alves Lafayette Wallis
• Babbar Manisha
• Dey Abhisek
• Lingala Sadasiva

Classifications

• G06F11/3688 Primary

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

• G06F11/3696

  Methods or tools to render software testable · CPC title

• G06F11/3684 Primary

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