IP Library Granted Patent US 8,910,123
Granted Patent B2
US 8,910,123 · App. 13/413,461 · Granted Dec 9, 2014

Automated validation of generated test cases following changes to the underlying test model

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 8,910,123
App. No.
13/413,461
Granted
Dec 9, 2014
Kind
B2
Abstract

Automated checking of test cases when the underlying test model has been modified includes verifying the structure of the original test cases against the new (modified) test model. Verified test cases are assessed by manipulating the new test model to produce corresponding manipulated test models. A test case is still valid for the new test model if a test case can be generated from its corresponding manipulated test model.

Claims (35)

1. A method of operating a computer system to validate test cases for test models comprising operating the computer system to perform steps of:

receiving information for a first state transition diagram representative of a first test model that models a system under test (SUT);

generating first test cases from the first test model using a test generator, each test case comprising a plurality of states in the first state transition diagram and a plurality of transitions between the states;

receiving information for a second state transition diagram representative of a second test model that models a new version of the SUT; and

for each test case among some of the first test cases:

generating a third test model corresponding to said each test case using information for the second test model, including modifying a copy of the second test model by removing edges in the copy of the second test model that are not in said each test case, and copying and inserting edges and vertices that are traversed more than once in order to obtain the same test sequence as in said each test case; and

designating said each test case as being valid or invalid for the second test model depending on whether or not the test generator can generate any test cases from the third test model.

2. The method of claim 1 wherein if said each test case is associated a data constraint, then generating the third test model includes incorporating the data constraint.

3. The method of claim 1 further comprising eliminating one or more test cases from among the first test cases.

4. The method of claim 3 wherein eliminating one or more test cases from among the first test cases includes comparing each first test case with the second test model, wherein said each first test case is deemed eliminated depending on the comparison.

5. The method of claim 4 wherein the comparison includes comparing a structure of said each first test case with a structure of the second test model.

6. A system for validating test cases for test models comprising:

a processor; and

a data store having stored thereon executable program code configured to caused the processor to:

receive information for a first state transition diagram representative of a first test model that models a system under test (SUT);

generate first test cases from the first test model using a test generator, each test case comprising a plurality of states in the first state transition diagram and a plurality of transitions between the states;

receive information for a second state transition diagram representative of a second test model that models a new version of the SUT; and

for each test case among some of the first test cases:

generate a third test model corresponding to said each test case using information for the second test model, including modifying a copy of the second test model by removing edges in the copy of the second test model that are not in said each test case, and copying and inserting edges and vertices that are traversed more than once in order to obtain the same test sequence as in said each test case; and

designate said each test case as being valid or invalid for the second test model depending on whether or not the test generator can generate any test cases from the third test model.

7. The system of claim 6 wherein if said each test case is associated a data constraint, then the third test model incorporates the data constraint.

8. The system of claim 6 further comprising eliminating one or more test cases from among the first test cases.

9. The system of claim 8 wherein the one or more test cases are eliminated from among the first test cases based on a comparison of each first test case with the second test model.

10. The system of claim 9 wherein the comparison includes a comparison of a structure of said each first test case with a structure of the second test model.

11. A non-transitory computer-readable storage medium having stored thereon computer executable program code comprising program code configured to cause a computer to perform steps of:

receiving information for a first state transition diagram representative of a first test model that models a system under test (SUT);

generating first test cases from the first test model using a test generator, each test case comprising a plurality of states in the first state transition diagram and a plurality of transitions between the states;

receiving information for a second state transition diagram representative of a second test model that models a new version of the SUT; and

for each test case among some of the first test cases:

generating a third test model corresponding to said each test case using information for the second test model, including modifying a copy of the second test model by removing edges in the copy of the second test model that are not in said each test case, and copying and inserting edges and vertices that are traversed more than once in order to obtain the same test sequence as in said each test case; and

designating said each test case as being valid or invalid for the second test model depending on whether or not the test generator can generate any test cases from the third test model.

12. The non-transitory computer-readable storage medium of claim 11 wherein the third test model includes a data constraint associated with said each test case.

13. The non-transitory computer-readable storage medium of claim 12 wherein the computer executable program code further comprises program code configured to cause a computer to perform steps of eliminating one or more test cases from among the first test cases.

14. The non-transitory computer-readable storage medium of claim 13 wherein eliminating one or more test cases from among the first test cases includes comparing each first test case with the second test model, wherein said each first test case is deemed eliminated depending on the comparison.

15. The non-transitory computer-readable storage medium of claim 14 wherein the comparison includes comparing a structure of said each first test case with a structure of the second test model.

Assignments (2)
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 6, 2012
From: WIECZOREK, SEBASTIAN; ROTH, ANDREAS
To: SAP AG
Reel/Frame 027815/0396 →