10241808

Determining Test Application Effectiveness

PublishedMarch 26, 2019
Assigneenot available in USPTO data we have
Technical Abstract

Patent Claims
15 claims

Legal claims defining the scope of protection, as filed with the USPTO.

1

1. A system for evaluating test application effectiveness, comprising: a display engine, to provide a graphic user interface and cause a display of a plurality of factors to be considered by a user in evaluating a test application via the interface, the test application to test a software program; an evaluation data engine, to receive via the interface user-assigned ratings for test application evaluation factors including a documentation test quality factor, a product-general test quality factor, a product-specific test quality factor, and a defect severity factor; and a rating engine to determine, based upon the rating, an overall test effectiveness rating for the test application.

2

2. The system of claim 1 , wherein the rating engine is to cause a display of the overall test effectiveness rating via the graphic user interface.

3

3. The system of claim 1 , wherein the rating for the documentation test quality factor includes an evaluation of an extent to which the test application documentation includes at least one of a stated goal for the test application, an explanatory title, stated test steps, stated expected test results, and stated expected test behaviors.

4

4. The system of claim 1 , wherein rating for the product-general test quality factor includes an assessment of the test application testing of at least of one of an installation task, an uninstallation task, a use case task, an internationalization task, and a localization task.

5

5. The system of claim 1 , wherein the rating for the product-general test quality factor includes an assessment of the test application testing at least one of a document file, a log file, and a configuration file.

6

6. The system of claim 1 , wherein the rating for the product-specific test quality factor includes an assessment of the test application testing at least one of a named document, a named program function, a named program class, a named program library, and a named program object.

7

7. The system of claim 1 , wherein the rating for the defect severity factor includes an assessment of impact to a user or stakeholder if the test application indicates an unsatisfactory behavior of the software program.

8

8. The system of claim 1 , wherein the evaluation data engine is to receive via the interface, a user-assigned weightage rating for the product-general test quality factor and the product-specific test quality factor, and wherein the rating engine is to determine the overall test effectiveness rating based upon the weightage rating.

9

9. The system of claim 1 , wherein the evaluation data engine is to receive via the interface, a user-assigned designation of at least one of a positive case, negative case, boundary case, edge case, and corner case, and the overall test effectiveness rating is determined based upon the designation.

10

10. The system of claim 1 , wherein the test application is a subject test application, and further comprising a missed test identifier engine, to access data indicative of evaluation of a plurality of test applications relating to the software program, the plurality including the subject test application, and to provide a recommendation or alert responsive to determining a product-general test quality factor or a product-specific test quality factor is not tested by any of the plurality of test applications.

11

11. The system of claim 1 , wherein the test application is a subject test application, and further comprising an under-focused test identifier engine, to access data indicative of evaluation of a plurality of test applications relating to the software program, the plurality including the subject test application, and to provide a recommendation or alert responsive to determining that a product-general test quality factor or a product-specific test quality factor is not directly tested by one of the plurality of test applications.

12

12. The system of claim 1 , further comprising an improvement priority engine to determine an improvement priority rating based upon at least two of the user-assigned documentation test quality factor rating, the user-assigned product-general test quality factor rating, the user-assigned product-specific test quality factor rating, the user-assigned defect severity factor rating, and the determined overall test effectiveness rating, and to provide a recommendation or alert responsive to determining the improvement priority rating exceeds a threshold rating.

13

13. A memory resource storing instructions that when executed cause a processing resource to implement a system to evaluate effectiveness of a test application, the instructions comprising: a display module, to provide a graphic user interface and cause a display of a documentation test quality factor, a product-general test quality factor, a product-specific test quality factor, and a defect severity factor to be considered by a user in evaluating a test application via the interface, the test application to test a software program; an evaluation data module, to receive via the interface, as test application evaluation data for the application, user-assigned ratings for the documentation test quality factor, the product-general test quality factor, the product-specific test quality factor, and the defect severity factor, wherein the documentation test quality factor includes at least one of a stated goal for the test application, an explanatory title, stated test steps, and stated expected test results or behaviors, the product-general test quality factor includes at least one of an installation task, an uninstallation task, a use case task, an internationalization, and a localization task, the product-specific test quality factor includes at least one of a code specifying at least one of a named document, a named program function, a named program class, a named program library, and a named program object, and defect severity factor includes an impact to a user or stakeholder if the software program fails upon execution of the test application; and a rating module, to determine, in consideration of the ratings, an overall test effectiveness rating for the test application and cause a display of the ratings via the interface.

14

14. The memory resource of claim 13 , wherein the rating for the product-specific test quality factor includes an assessment of the test application testing a specified code set of the test application.

15

15. A test application evaluation method, comprising: providing a graphic user interface and causing a display via the interface of a plurality of factors to be considered by a user in evaluating a subject test application for testing a software program; receiving via the interface evaluation data for the subject test application, the evaluation data including user-assigned ratings for a documentation test quality factor, a product-general test quality factor, a product-specific test quality factor, and a defect seventy factor; determining, based upon the ratings, and providing via the interface an overall test effectiveness rating for the subject test application; determining an improvement priority rating based upon at least two of the user-assigned documentation test quality factor rating, the user-assigned product-general test quality factor rating, the user-assigned product-specific test quality factor rating, the user-assigned defect severity factor rating, and the determined overall test effectiveness rating, and providing a recommendation or alert responsive to determining the improvement priority rating is above a threshold rating; accessing data indicative of evaluation of a plurality of test applications for testing the software program, the plurality including the subject test application; and providing a recommendation or alert responsive to determining, that a product-specific test quality factor is not directly tested by one of the plurality of test applications.

Patent Metadata

Filing Date

Unknown

Publication Date

March 26, 2019

Inventors

Mallikarjuna Reddy Kolagatla
Narasimhamurthy M R
Padmini R
Narayana Rao SVN

Want to explore more patents?

Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.

Citation & reuse

Analysis on this page is generated by Patentable — an AI-powered patent intelligence platform. AI-generated summaries, explanations, and analysis may be reused with attribution and a visible link back to the canonical URL below. Patent abstracts and claims are USPTO public domain.

Cite as: Patentable. “DETERMINING TEST APPLICATION EFFECTIVENESS” (10241808). https://patentable.app/patents/10241808

© 2026 Patentable. All rights reserved.

Patentable is a research and drafting-assistant tool, not a law firm, and does not provide legal advice. Documents we generate are drafts for review by a licensed patent attorney.