Automatically populating symptom databases for software applications
First Claim
1. A method, in a data processing system, for populating a symptom collection for a software application, the method comprises:
- performing a test of the software application for verifying a correctness of the software application, wherein;
the test includes a plurality of test cases,a subset of error test cases in the plurality of test cases verifies the correctness of the software application in non-allowable scenarios, wherein the non-allowable scenarios are scenarios indicative of end-user misuse,execution of an error test case in the subset of error test cases purposely induces a problem in the software application, andresponsive to an expected outcome in response to executing the error test case, identifying a symptom indicative of an undesired behavior and a test action of the error test case that caused the problem; and
populating the symptom collection according to a result of the error test case with the symptom and the test action that caused the problem.
1 Assignment
0 Petitions
Accused Products
Abstract
A solution is proposed for populating a symptom collection—such as a symptom database—for a software application. The symptom collection includes an indication of a set of symptoms; each symptom consists of an undesired behavior of the software application, which symptom is due to each one of a set of corresponding problems of the software application (resulting from a misuse thereof). The symptom database also includes an indication of an explanation of each problem. A corresponding method involves performing a test of the software application for verifying a correctness of the software application. The symptom collection is then populated according to a result of the test.
-
Citations
24 Claims
-
1. A method, in a data processing system, for populating a symptom collection for a software application, the method comprises:
-
performing a test of the software application for verifying a correctness of the software application, wherein; the test includes a plurality of test cases, a subset of error test cases in the plurality of test cases verifies the correctness of the software application in non-allowable scenarios, wherein the non-allowable scenarios are scenarios indicative of end-user misuse, execution of an error test case in the subset of error test cases purposely induces a problem in the software application, and responsive to an expected outcome in response to executing the error test case, identifying a symptom indicative of an undesired behavior and a test action of the error test case that caused the problem; and populating the symptom collection according to a result of the error test case with the symptom and the test action that caused the problem. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer program product for performing a method for populating a symptom collection for a software application comprising a non-transitory computer-usable medium embodying a computer readable program, wherein the computer readable program, when executed on a computing device, causes the computing device to:
-
perform a test of the software application for verifying a correctness of the software application, wherein; the test includes a plurality of test cases, a subset of error test cases in the plurality of test cases verifies the correctness of the software application in non-allowable scenarios, wherein the non-allowable scenarios are scenarios indicative of end-user misuse, execution of an error test case in the subset of error test cases purposely induces a problem in the software application, and responsive to an expected outcome in response to executing the error test case, identifying a symptom indicative of an undesired behavior and a test action of the error test case that caused the problem; and populate the symptom collection according to a result of the error test case with the symptom and the test action that caused the problem. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A system for populating a symptom collection for a software application, comprising:
-
a processor; and a memory coupled to the processor, wherein the memory comprises a computer program which configures the processor to; perform a test of the software application for verifying a correctness of the software application, wherein; the test includes a plurality of test cases, a subset of error test cases in the plurality of test cases verifies the correctness of the software application in non-allowable scenarios, wherein the non-allowable scenarios are scenarios indicative of end-user misuse, execution of an error test case in the subset of error test cases purposely induces a problem in the software application, and responsive to an expected outcome in response to executing the error test case, identifying a symptom indicative of an undesired behavior and a test action of the error test case that caused the problem; and populate the symptom collection according to a result of the error test case with the symptom and the test action that caused the problem. - View Dependent Claims (20, 21, 22)
-
-
23. A tool in a memory for populating a symptom collection for a software application, wherein the tool includes:
means for populating the symptom collection according to a result of a subset of error test cases with a symptom and a test action that caused a problem to occur in the software application being performed for a test for verifying a correctness of the software application, wherein; the test includes a plurality of test cases, the subset of error test cases in the plurality of test cases verifies the correctness of the software application in non-allowable scenarios, wherein the non-allowable scenarios are scenarios indicative of end-user misuse, execution of an error test case in the subset of error test cases purposely induces the problem in the software application, and responsive to an expected outcome in response to executing the error test case, identifying the symptom indicative of an undesired behavior and the test action of the test case that caused the problem. - View Dependent Claims (24)
Specification