IP Library › Granted Patent US 10,642,717
Granted Patent B2
US 10,642,717 · App. 16/028,637 · Granted May 5, 2020

Application user interface testing system and method

Inventors: John Girata, Jr. (Raleigh, NC); Bryan R. Florkiewicz (Durham, NC); Martin Presler-Marshall (Chapel Hill, NC)
Assignee: International Business Machines Corporation
G06F11/3664G06F8/38G06F11/3676G06F11/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 10,642,717
App. No.
16/028,637
Granted
May 5, 2020
Kind
B2
Abstract

A method, computer program product, and computing system device for monitoring a plurality of individual actions executed on at least a portion of a software application. It may be determined whether the plurality of individual actions executed on the at least a portion of the software application complete at least one test case of a plurality of test cases. The at least one test case may be marked as completed based upon, at least in part, determining that the plurality of individual actions executed on the at least a portion of the software application complete the at least one test case of the plurality of test cases.

Claims (32)

1. A computer-implemented method comprising:

monitoring, at a computing device, a plurality of individual actions executed by a user on at least a portion of a software application;

determining whether the plurality of individual actions executed on the at least a portion of the software application is completed for at least one test case of a plurality of test cases;

for each time that the plurality of individual actions is completed for the at least one test case, determining a number of successful executions performed for the at least one test case; and

as a result of the number of successful executions being a predefined number of times, the predefined number of times being greater than one, marking the at least one test case as completed.

2. The computer-implemented method of claim 1 , further comprising:

defining a test case of the plurality of test cases as a plurality of individual actions executed on the at least a portion of the software application.

3. The computer-implemented method of claim 2 , wherein defining the test case includes defining the test case as a predefined sequence of individual actions executed on the at least a portion of the software application.

4. The computer-implemented method of claim 2 , wherein defining the test case includes inserting a plurality of code hooks into code associated with the at least a portion of the software application.

5. The computer-implemented method of claim 1 , wherein monitoring the plurality of individual actions includes associating one or more individual actions of the plurality of individual actions with a specific user from a plurality of users.

6. The computer-implemented method of claim 1 , wherein determining whether the plurality of individual actions executed on the at least a portion of the software application complete at least one test case of a plurality of test cases includes recording each completion of the at least one test case of the plurality of test cases.

7. A computer program product comprising a non-transitory computer readable storage medium having a plurality of instructions stored thereon, which, when executed by a processor, cause the processor to perform operations comprising:

monitoring a plurality of individual actions executed by a user on at least a portion of a software application;

determining whether the plurality of individual actions executed on the at least a portion of the software application is completed for at least one test case of a plurality of test cases;

for each time that the plurality of individual actions is completed for the at least one test case, determining a number of successful executions performed for the at least one test case; and

as a result of the number of successful executions being at least a predefined number of times, the predefined number of times being greater than one, marking the at least one test case as completed.

8. The computer program product of claim 7 , further comprising instructions for:

defining a test case of the plurality of test cases as a plurality of individual actions executed on the at least a portion of the software application.

9. The computer program product of claim 8 , wherein defining the test case includes defining the test case as a predefined sequence of individual actions executed on the at least a portion of the software application.

10. The computer program product of claim 8 , wherein defining the test case includes inserting a plurality of code hooks into code associated with the at least a portion of the software application.

11. The computer program product of claim 7 , wherein monitoring the plurality of individual actions includes associating one or more individual actions of the plurality of individual actions with a specific user from a plurality of users.

12. The computer program product of claim 7 , wherein determining whether the plurality of individual actions executed on the at least a portion of the software application complete at least one test case of a plurality of test cases includes recording each completion of the at least one test case of the plurality of test cases.

13. A computing system including one or more processors and one or more memories configured to perform operations comprising:

monitoring a plurality of individual actions executed by a user on at least a portion of a software application;

determining whether the plurality of individual actions executed on the at least a portion of the software application is completed for at least one test case of a plurality of test cases;

for each time that the plurality of individual actions is completed for the at least one test case, determining a number of successful executions performed for the at least one test case; and

as a result of the number of successful executions being at least a predefined number of times, the predefined number of times being greater than one, marking the at least one test case as completed.

14. The computing system of claim 13 , wherein the operations further comprise:

defining a test case of the plurality of test cases as a plurality of individual actions executed on the at least a portion of the software application.

15. The computing system of claim 14 , wherein defining the test case includes defining the test case as a predefined sequence of individual actions executed on the at least a portion of the software application.

16. The computing system of claim 14 , wherein defining the test case includes inserting a plurality of code hooks into code associated with the at least a portion of the software application.

17. The computing system of claim 13 , wherein monitoring the plurality of individual actions includes associating one or more individual actions of the plurality of individual actions with a specific user from a plurality of users.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 6, 2018
From: GIRATA, JOHN, JR.; FLORKIEWICZ, BRYAN R.; PRESLER-MARSHALL, MARTIN J.
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 046279/0082 →
Continuity (1)
Related Publication 20200012587A1 · Jan 9, 2020