IP Library Granted Patent US 12688115
Granted Patent B2
US 12688115 · App. 18/378,453 · Granted Jul 21, 2026

Dynamic functional testing tool

Inventors: Bryson Greer (Smithfield, NC); Michael Furlong (Durham, NC)
Assignee: FMR LLC
G06F11/3698G06F11/3684
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12688115
App. No.
18/378,453
Granted
Jul 21, 2026
Kind
B2
Abstract

A computer-implemented method is provided for producing a test for a software application that is generated based on metadata. The method includes providing to the user a library of predefined test logic for testing multiple software components. Each software component is a reusable element comprising application logic, visual styling and user interface. The method also includes guiding the user to define (i) at least one execution path that specifies an order for testing one or more pages of the software application, and (ii) test instructions for one or more components on each of the one or more pages. The method further includes retrieving, from the library, predefined test logic for the one or more components if they are present in the library based on the test instructions supplied by the user, and automatically configuring a test file incorporating the predefined test logic in an order specified by the execution path.

Claims (24)

1 . A computer-implemented method for producing a test for a software application that is generated based on metadata, the method comprising:

providing to a user, by a computing device comprising a microprocessor, a library of predefined test logic for testing a plurality of software components, wherein each software component is a reusable element comprising of application logic, visual styling and user interface, and wherein each software component is configured to operate on user input;

guiding, by the computing device, the user to define (i) at least one execution path that specifies an order for testing one or more pages of the software application, and (ii) test instructions for one or more components on each of the one or more pages;

retrieving from the library, by the computing device, predefined test logic for the one or more components based on the test instructions supplied by the user, the predefined test logic for each of the one or more components comprising a components object with predefined steps of simulating user interaction with the component, wherein the components object specifies a value key defining at least one value to enter into the component for testing the component and a key specifying all test execution paths the component is used on;

automatically configuring, by the computing device, a test file incorporating the predefined test logic in an order specified by the at least one execution path; and

executing, by the computing device, the test file to test the software application by dynamically accessing the one or pages in the at least one execution path and testing the one or more components on each page following the test logic.

2 . The method of claim 1 , wherein in response to predefined test logic of one or more other components on a page not being found in the library:

receiving user-specified instructions for testing the one or more other components, and

storing the user-specified test instructions in the library for future testing of the one or more other components.

3 . The method of claim 2 , further comprising configuring the test file by combining the user-specified test instructions for the one or more other components with the test logic retrieved from the library for the one or more components.

4 . The method of claim 1 , wherein retrieving from the library predefined test logic comprises guiding, by the computer device, the user to select from the library the predefined test logic for testing at least one user interaction with respect to the one or more components.

5 . The method of claim 4 , wherein the at least one user interaction comprises clicking a button or opening or closing a modal.

6 . The method of claim 1 , wherein the test file is a JavaScript Object Notation (JSON) file.

7 . The method of claim 1 , wherein the component comprises a checkbox, a textbox or a menu.

8 . A computer-implemented system for producing a test for a software application that is generated based on metadata, the computer-implemented system comprising a computing device having a memory for storing instructions, wherein the instructions, when executed, configure the computer-implemented system to provide:

a library of predefined test logic for testing a plurality of software components, wherein each software component is a reusable element comprising of application logic, visual styling and user interface, and wherein each software component is configured to operate on user input;

a configuration module configured to allow the user to define (i) at least one execution path that specifies an order for testing one or more pages of the software application, and (ii) test instructions for one or more components on each of the one or more pages, the configuration module adapted to retrieve from the library predefined test logic for each of the one or more components that comprises a components object with predefined steps simulating user interaction with the component, wherein the components object specifies a value key defining at least one value to enter into the component for testing the component and a key specifying all test execution paths the component is used on,

wherein the configuration module is further configured to automatically generate a test file incorporating the test logic in an order specified by the at least one execution path; and

an execution module configured to execute the test file to test the software application by dynamically accessing the one or pages in the at least one execution path and testing the one or more components on each page following the test logic.

9 . The computer-implemented system of claim 8 , wherein if testing of the one or more components on a page is not defined in the library, the configuration module is configured to receive user-specified instructions for testing the one or more components, and the library is configured to store the user-specified test instructions for future testing of the one or more components.

10 . The computer-implemented system of claim 8 , wherein the configuration module is further configured to guide the user to select from the library the predefined test logic for testing at least one user interaction with respect to the one or more components.

11 . The computer-implemented system of claim 10 , wherein the at least one user interaction comprises clicking a button or opening or closing a modal.

12 . The computer-implemented system of claim 8 , wherein the test file is a JavaScript Object Notation (JSON) file.

13 . The computer-implemented system of claim 8 , wherein the component comprises a checkbox, a textbox or a menu.