Method and framework for test case management
In accordance with an embodiment of the present invention, a method may include obtaining a list of active life cycle test objects in a test run from a life cycle test object controller, and obtaining a list of active central activity test objects in the test run from a central activity test object controller. While a test period remains in the test run, the method may continue selecting a next test period, requesting the test step initialization controller initialize the next test period, requesting all central activity test objects associated with the next test period to execute their beginning central activities, requesting all life cycle test objects associated with the next test period to execute their test activities, and requesting all central activity test objects associated with the next test period to execute their ending central activities.
Latest SAP AG Patents:
- Systems and methods for augmenting physical media from multiple locations
- Compressed representation of a transaction token
- Accessing information content in a database platform using metadata
- Slave side transaction ID buffering for efficient distributed transaction management
- Graph traversal operator and extensible framework inside a column store
The field of the invention relates to software application testing and, in particular to methods of and a framework for the automatic testing of multiple independent test cases in complex software applications.
BACKGROUNDCurrently test programs for testing complex software applications, for example, applications for complex business processes, are themselves complex and frequently very large in size, since they not only have to model the applications, but also all of the constituent sub-processes and associated data. For example, these software applications usually implement generic business processes, which model industry operations. The software applications must be customized to fit each customer's role in the marketplace and to fit the customer's specific data. As a result, the complexity and size of each test program can increase dramatically where some or all of a number of test cases for the application must run in parallel, since this scenario must also be programmed into the test program. For example, in a banking environment, a test case defines the activities that occur in an account (e.g., opening the account, depositing funds, withdrawing funds, closing the account, etc.) over a period of time.
In general, the test cases that must run in parallel are independent of each other, (for example, each test case represents activities that occur in different accounts), but, at some select points, called “sync points” (i.e., “synchronization points”) in the test cases, the flow of the test cases must be interrupted and a “central activity,” for example, a central test activity, must be performed. For example, in the banking environment, the central activity can be an activity that occurs at a specified time, e.g., at the beginning of a day, at the end of the day, at the end of a month, at the end of a reporting period, etc. The central (or global) activity, generally, exerts an influence on all or almost all of the test cases. After the central activity has been performed, the individual test cases may continue to be executed. The test program continues until all of the test cases and central activities have been executed for some predetermined time period.
The current general architecture is used in transaction banking to test business cases of core banking functionality for long time periods and where the central activities can include “end of the day processing” jobs, which are set to run every night. Unfortunately, if changes/additions need to be made to the test cases, currently, the entire test program must be edited to incorporate the changes and/or additions. For example, in the banking scenario, a customer's checking and savings accounts are programmed as separate accounts, since they operate independently of each other. However, if the two accounts are to be associated to enable transfers between the accounts, the test program will have to be modified to include this functionality by deleting the separate code sections for each type of account and adding new code directed to a hybrid test case where the customer's checking and savings accounts are handled in the single test case. This is not an insignificant change and it can be a time consuming and costly process.
Therefore, an efficient and easily modifiable test architecture to permit the addition and removal of test cases without having to change existing test cases is highly desirable.
Embodiments of the present invention provide improved methods of and infrastructures, for example, frameworks, for the automatic testing of multiple independent test cases in complex software applications. In general, a framework is a standard, generic software architecture on which components of multiple applications may be instantiated/implemented to provide cross-application compatibility. In accordance with an embodiment of the present invention, a method for the automatic testing of complex software applications having multiple, independent test cases, may include obtaining test initialization information and determining a first test period from the test initialization information. The method may also include executing one or more beginning central test activities, if the one or more beginning central test activities are associated with the first test period; executing activities for at least one of a plurality of independent test cases associated with the first test period in the test framework; and executing one or more ending central test activities, if the one or more ending central test activities are associated with the first test period. The method may further include determining that subsequent test periods exist and then for each determined subsequent test period, initializing the subsequent test period; executing a subsequent beginning central test activity, if the subsequent beginning central test activity is associated with the subsequent test period; and executing activities for at least one of the plurality of independent test cases associated with the subsequent test period in the test framework; and executing a subsequent ending central test activity, if the subsequent ending central test activity is associated with the subsequent test period. The method may also include storing results of all of the executions from all of the test periods.
In
In
In
In another embodiment of the present invention, although not shown in
The advantage of test framework 100, in
In
In
In
In
In
In
In test framework architecture 200 of
In general, in
In another embodiment of the present invention, in
In general, TRC 210 may determine that the execution of a test run is complete when one of the following conditions occurs: a last “global test element” has been executed; a user starting TRC 210 explicitly set a “max number of global test elements” and the maximum number of global test elements have been performed; or an error has occurred in one of CATOs 260-1 to 260-n.
During the execution of a test case, in test framework architecture 200 of
-
- a global test element;
- an activity to be performed at the beginning or end of this global test element;
- a CATO-ID; and
- an activity-ID.
In accordance with another embodiment of the present invention, the determination of the global test activities that are needed may be accomplished by having each LCTO 250-1 to 250-m implement a service to determine the next central activities that may be needed. For example, the service may receive as an input a global test element and may output the next global test element that is greater than or equal to the input global test element for which each LCTO may need global test activities. A list of test activities for each global test element 111, 112 may identify:
-
- whether an activity should be performed at the beginning or end of the global test element;
- a CATO-ID; and
- an activity-ID.
Although, TRC 210 may call every LCTO 250-1 to 250-m at the beginning of every global test element, TRC 210 may call at the end of every global test element only those LCTOs for which global test activities have been performed in the global test element.
In accordance with an embodiment of the present invention, a test case may be defined by the definition of a LCTO, which may describe the complete test scenario and may be internally structured by test elements. As a result, each test activity of the LCTO may be assigned to exactly one test element.
In the test execution phase, TRC 210 may be responsible for executing the test. The main object used in executing the tests is the “test element”. This means that TRC 210 may loop at all relevant test elements and in each loop it may call all LCTOs 250-1 to 250-m to perform the test activities belonging only to this test element.
Integration of central activities. In
Test framework architecture 200, in
-
- Alternative 1: Run the complete test
- Alternative 2: Run the tests from the beginning until a special “global test element”
- Alternative 3: Continue a test run which was interrupted in a previous run (by choosing alternative 2)
Where, alternative 2 may be useful in the following cases: - Performing a software upgrade between alternative 2 and alternative 3
- Making some detailed manual checks after the tests performed by alternative 2
Behavior after an error. In
In
In
In
In another embodiment of the present invention, although not shown in
The advantage of test framework 300, in
In
In
In
In another embodiment of the present invention, although not shown in
The advantage of test framework 300, in
In
In
In
In
In
In general, there may be only one instance of a CATO in accordance with an embodiment of the present invention in
In
In test framework architecture 400 of
In general, in
In another embodiment of the present invention, in
In general, TRC 410 may determine that the execution of a test run is complete when one of the following conditions occurs: a last “global test element” has been executed; a user starting TRC 410 explicitly set a “max number of global test elements” and the maximum number of global test elements have been performed; or an error has occurred in one of CATOs 460-1 to 460-n.
During the execution of a test case, in test framework architecture 400 of
-
- a global test element;
- an activity to be performed at the beginning or end of this global test element;
- a CATO-ID; and
- an activity-ID.
In accordance with another embodiment of the present invention, the determination of the global test activities that are needed may be accomplished by having each LCTO 450-1 to 450-m implement a service to determine the next central activities that may be needed. For example, the service may receive as an input a global test element and may output the next global test element that is greater than or equal to the input global test element for which each LCTO may need global test activities. A list of test activities for each global test element 311, 312 may identify:
-
- whether an activity should be performed at the beginning or end of the global test element;
- a CATO-ID; and
- an activity-ID.
Although, TRC 410 may call every LCTO 450-1 to 450-m at the beginning of every global test element, TRC 410 may call at the end of every global test element only those LCTOs for which global test activities have been performed in the global test element.
A “test element” may represent one system date. For every system date a “bank working day” may be determined. CATO 460 may perform only test activities, if the actual system date is also a valid bank working day.
In accordance with an embodiment of the present invention, a test case may be defined by the definition of a LCTO, which may describe the complete test scenario and may be internally structured by test elements. As a result, each test activity of the LCTO may be assigned to exactly one test element.
In the test execution phase, TRC 410 may be responsible for executing the test. The main object used in executing the tests is the “test element”. This means that TRC 410 may loop at all relevant test elements and in this loop it may call all LCTOs 450-1 to 450-m to perform the test activities belonging only to this test element.
Integration of central activities. In
Test framework architecture 400, in
-
- Alternative 1: Run the complete test
- Alternative 2: Run the tests from the beginning until a special “global test element”
- Alternative 3: Continue a test run which was interrupted in a previous run (by choosing alternative 2)
Where, alternative 2 may be useful in the following cases: - Performing a software upgrade between alternative 2 and alternative 3
- Making some detailed manual checks after the tests performed by alternative 2
Behavior after an error. In
In
-
- Test element 1 of this LCTO (this test element, for example, may be assigned to the date 25, Aug. 2004) may include:
- Create a business partner
- Create an account
- Create a standing order, monthly, executed on the first of the month
- Make postings on the account
- Test element 2 of this LCTO (this test element, for example, may be assigned to the date 25, Sep. 2004) may include:
- Verify the execution of the standing order (stored in database?)
- Is the amount on the account correct
In addition, CATO 460 may be needed for the execution of the “standing order” and CATO 460 may run in a test step, which may be assigned to the first of September 2004 (01, Sep. 2004).
- Test element 1 of this LCTO (this test element, for example, may be assigned to the date 25, Aug. 2004) may include:
In
In
Several embodiments of the present invention are specifically illustrated and described herein. However, it will be appreciated that modifications and variations of the present invention are covered by the above teachings and come within the purview of the appended claims without departing from the spirit and intended scope of the invention.
Claims
1. A computer-implemented method for testing software applications using a plurality of test cases representing different practical scenarios, comprising:
- reading, by the computer, object data defining a plurality of test cases, each test case identifying unique object(s) corresponding to the test case, each test case further identifying central test activities to be performed by a test program upon all objects of the test cases and individual test activities to be performed by the test program upon the objects corresponding to the respective test case, execution of each individual test activity within a specific test case being independent of execution of individual test activities of any other test cases so that an addition of a new test case does not affect any existing test cases;
- scheduling, by the computer, execution of the central test activities and the individual test activities by: scheduling execution of central test activities of a first set of test cases; scheduling execution of the individual test activities of the first set of test cases according to their positions with respect to the central test activities within the respective the first set of test cases, wherein execution of an individual test activity of a first test case within the first set of test cases occurs concurrently with execution of another individual test activity of a second test case within the first set of test cases; scheduling execution of central test activities of a second set of test cases; scheduling execution of the individual test activities of the second set of test cases according to their positions with respect to the central test activities within the respective the second set of test cases, wherein execution of an individual test activity of a first test case within the second set of test cases occurs concurrently with execution of another individual test activity of a second test case within the second set of test cases; and
- executing the central test activities and the individual test activities of the first set of test cases as scheduled; and
- executing the central test activities and the individual test activities of the second set of test cases as scheduled,
- wherein each central test activity is only executed once at a synchronization point for all of concurrently executing test cases.
2. The method of claim 1 wherein the reading the object data comprises:
- obtaining a listing of all of the plurality of independent test cases; and
- obtaining a listing of all beginning and ending central test activities.
3. The method of claim 2 wherein the obtaining the listing of all of the plurality of independent test cases comprises:
- obtaining a listing of all life cycle test objects for each of the plurality of independent test cases.
4. The method of claim 3 wherein the obtaining the listing of all life cycle test objects for each of the plurality of independent test cases comprises:
- obtaining a listing of actions associated with each of the life cycle test objects for each test period for each of the plurality of independent test cases.
5. The method of claim 4 wherein at least one of the test periods has actions associated with at least one life cycle test object.
6. The method of claim 5 wherein the reading the object data comprises:
- determining a first test period with the beginning central test activity.
7. The method of claim 5 wherein the reading the object data comprises:
- determining a first test period with an activity associated with the at least one of the plurality of independent test cases.
8. The method of claim 2 wherein the obtaining the listing of all beginning and ending central test activities comprises:
- obtaining a listing of all beginning central test activities associated with each test period; and
- obtaining a listing of all ending central test activities associated with each test period.
9. The method of claim 8 wherein at least one test period is associated with beginning central test activities.
10. The method of claim 8 wherein at least one test period is associated with ending test activities.
11. The method of claim 1 wherein the executing the beginning comprises:
- determining execution of all other test activities has stopped; and
- executing the beginning central test activity.
12. The method of claim 1 wherein the executing individual test activities for at least one of a plurality of independent test cases associated with the first test period comprises:
- determining execution of the beginning one of the plurality of central test activities has stopped; and
- executing the individual test activities for the at least one plurality of independent test cases associated with the first test period.
13. The method of claim 1 wherein the executing an ending one of the plurality of central test activities comprises:
- determining execution of all test activities associated with the plurality of independent test cases has stopped; and
- executing the ending central test activity.
14. The method of claim 1 further comprising:
- storing results of all of the execution from all test periods,
- wherein the results are stored in a single data object.
15. The method of claim 14 wherein the storing the results in a single data object comprises:
- storing error messages in the single data object; and
- storing results from correctly executing test activities.
16. The method of claim 1 wherein a first test period represents a first specific time period within each of the test cases.
17. The method of claim 1 wherein the independent test cases run in parallel.
18. The method of claim 1 wherein the central test activity exerts an influence on all of the test cases.
19. The method of claim 1 wherein a number count of the individual test activities associated with the first test case within a same set of test cases is different from a number count of the individual test activities associated with the second test case within the same set of test cases.
20. The method of claim 1 wherein the individual test activities associated with the first test case within a same set of test cases are same as the individual test activities associated with the second test case within the same set of test cases.
21. The method of claim 1 wherein the individual test activities associated with the first test case within a same set of test cases are different from the individual test activities associated with the second test case within the same set of test cases.
22. The method of claim 1 wherein a first time duration starts according to business days.
23. The method of claim 1 wherein a first time duration starts monthly.
24. The method of claim 1 wherein the beginning one of the central test activities is executed according to a predetermined schedule.
25. The computer-implemented method of claim 1, wherein the testing is executed through a plurality of synchronization points, and wherein each of the central test activities is executed at a synchronization point.
26. A non-transitory machine-readable medium having stored thereon a plurality of executable instructions to perform a method for testing software applications using a plurality of test cases representing different practice scenarios, comprising:
- reading object data defining a plurality of test cases, each test case identifying unique object(s) corresponding to the test case, each test case further identifying central test activities to be performed by a test program upon all objects of the test cases and individual test activities to be performed by the test program upon the objects corresponding to the respective test case, execution of each individual test activity within a specific test case being independent of execution of individual test activities of any other test cases so that an addition of a new test case does not affect any existing test cases;
- scheduling, by the computer, execution of the central test activities and the individual test activities by: scheduling execution of central test activities of a first set of test cases; scheduling execution of the individual test activities for the first set of test cases according to their positions with respect to the central test activities within the respective the first set of test cases, wherein execution of an individual test activity of a first test case within the first set of test cases occurs concurrently with execution of another individual test activity of a second test case within the first set of test cases; scheduling execution of central test activities of a second set of test cases; scheduling execution of the individual test activities of the second set of test cases according to their positions with respect to the central test activities within the respective the second set of test cases, wherein execution of an individual test activity of a first test case within the second set of test cases occurs concurrently with execution of another individual test activity of a second test case within the second set of test cases; and
- executing the central test activities and the individual test activities of the first set of test cases as scheduled; and
- executing the central test activities and the individual test activities of the second set of test cases as scheduled,
- wherein each central test activity is only executed once at a synchronization point for all of the concurrently executing test cases.
27. The non-transitory machine-readable medium of claim 26 wherein the reading the object data comprises:
- obtaining a listing of all of the plurality of independent test cases; and
- obtaining a listing of all beginning and ending central test activities.
28. The non-transitory machine-readable medium of claim 27 wherein the obtaining the listing of all of the plurality of independent test cases comprises:
- obtaining a listing of all life cycle test objects for each of the plurality of independent test cases.
29. The non-transitory machine-readable medium of claim 28 wherein the obtaining the listing of all life cycle test objects for each of the plurality of independent test cases comprises:
- obtaining a listing of actions associated with each of the life cycle test objects for each test period for each of the plurality of independent test cases.
30. The non-transitory machine-readable medium of claim 29 wherein at least one of the test periods has actions associated with at least one life cycle test object.
31. The non-transitory machine-readable medium of claim 30 wherein at least one test period is associated with the beginning test activities.
32. The non-transitory machine-readable medium of claim 30 wherein at least one test period is associated with the ending test activities.
33. The non-transitory machine-readable medium of claim 27 wherein the obtaining the listing of all beginning and ending central test activities comprises:
- obtaining a listing of all beginning central test activities associated with each test period; and
- obtaining a listing of all ending central test activities associated with each test period.
34. The non-transitory machine-readable medium of claim 33 wherein the reading the object data comprises:
- determining a first test period with the beginning central test activity.
35. The non-transitory machine-readable medium of claim 33 wherein the reading the object data comprises:
- determining a first test period with an activity associated with the at least one of the plurality of independent test cases.
36. The non-transitory machine-readable medium of claim 26 wherein the executing the beginning central test activity comprises:
- determining execution of all other test activities has stopped; and
- executing the beginning central test activity.
37. The non-transitory machine-readable medium of claim 26 wherein the executing individual test activities for at least one of a plurality of independent test cases associated with the first test period comprises:
- determining execution of the beginning one of the plurality of central test activities has stopped; and
- executing the individual test activities for the at least one plurality of independent test cases associated with the first test period.
38. The non-transitory machine-readable medium of claim 26 wherein the executing the ending central test activity comprises:
- determining execution of all test activities associated with the plurality of independent test cases has stopped; and
- executing the ending central test activity.
39. The non-transitory machine-readable medium of claim 26 further comprising:
- storing results of all of the execution from all test periods,
- wherein the results are stored in a single data object.
40. The non-transitory machine-readable medium of claim 39 wherein the storing the results in a single data object comprises:
- storing error messages in the single data object; and
- storing results from correctly executing test activities.
41. A non-transitory machine-readable medium having stored thereon a plurality of executable instructions encoding a test framework, the test framework comprising:
- a test run controller;
- at least one life cycle test object registered to the test run controller, wherein each of the at least one life cycle test object is independent of any other, each life cycle test object including at least one life cycle test object activity to be executed during a predetermined test period;
- a life cycle test object controller registered to the test run controller and the at least one life cycle test object, the life cycle test object controller to maintain a list of the at least one life cycle test object;
- at least one central activity test object registered to the test run controller, each central activity test object to be executed during a test period without any life cycle test object activities being executed;
- a central activity test object controller registered to the test run controller and the at least one central activity test object, the central activity test object controller to maintain a list of the at least one central activity test object;
- a test period initialization controller registered to the test run controller, the test period initialization controller to read object data defining a plurality of test cases, each test case identifying unique object(s) corresponding to the test case, each test case further identifying the at least one life cycle object corresponding individual test activities and the at least one central activity test object corresponding central test activities to be performed by the test run controller upon all objects of the test cases, and to schedule execution of the central test activities and the individual test activities, wherein execution of an individual test activity of a first test case occurs concurrently with execution of another individual test activity of a second test case;
- an application to be tested, the application connected to the test period initialization controller, the at least one life cycle test object and the at least one central activity test object; and
- a test result controller to receive results from the test run controller, the life cycle test object controller, the central activity test object controller, the test period initialization controller, the at least one life cycle test object, and the at least one central activity test object,
- wherein execution of each individual test activity within a specific test case is independent of execution of individual test activities of any other test cases so that an addition of a new test case does not affect any existing test cases, and
- wherein the each central test activity is only executed once at a synchronization point for all concurrently executing test cases.
42. The non-transitory machine-readable medium of claim 41 wherein each life cycle test object controls the life cycle of an associated single application object.
43. The non-transitory machine-readable medium of claim 42 wherein execution of each life cycle test object only effects the single application object associated with the life cycle test object.
44. The non-transitory machine-readable medium of claim 41 wherein the test run controller comprises:
- a master test object to control execution of a test run including a plurality of test periods.
45. The non-transitory machine-readable medium of claim 44 wherein the master test object is to instruct life cycle test objects associated with a test period to execute during the test period and to instruct central activity test objects associated with the test period to execute during the test period.
46. The non-transitory machine-readable medium of claim 45 wherein the master test object is to determine which life cycle test objects are associated with a given test period by requesting the list of the at least one life cycle test object from the life cycle test object controller.
47. The non-transitory machine-readable medium of claim 45 wherein the master test object is to determine which central activity test objects are associated with a given test period by requesting the list of the at least one central activity test object from the central activity test object controller.
48. The non-transitory machine-readable medium of claim 44 wherein the master test object is to:
- obtain the list of active life cycle test objects in the test run from the life cycle test object controller;
- obtain the list of active central activity test objects in the test run from the central activity test object controller; and
- while a test period remains in the test run select a time duration of a next test period, request the test step initialization controller initialize the next test period, request all central activity test objects associated with the next test period to execute their beginning central test activities, request all life cycle test objects associated with the next test period to execute their test activities, and request all central activity test objects associated with the next test period to execute their ending central test activities.
49. The non-transitory machine-readable medium of claim 48 wherein the test run is to terminate upon an error occurring during execution of one of the central activity test objects.
50. The non-transitory machine-readable medium of claim 48 wherein the test run is to pause execution after a predetermined test period, receive an upgrade of the application, and resume execution of the test run using the upgraded application.
51. The non-transitory machine-readable medium of claim 48 wherein the test run controller is to determine which central activity test objects are associated with each test period from the life cycle test objects associated with the test period.
52. The non-transitory machine-readable medium of claim 48 wherein each life cycle test object is to determine which central activity test objects are associated with the test period associated with the life cycle test object.
53. A non-transitory computer-readable medium having stored thereon a plurality of executable instructions to perform a method of managing operations of a test program to test functionality of an application program, comprising:
- reading, by the computer, object data defining a plurality of test cases, wherein the object data is a data structure comprising fields for: a plurality of test cases, each test case identifying object(s) managed by the computer application to which the respective test case relates, each test case storing: first fields for storage of identifiers representing central test activities common to all the test cases, the central test activity identifiers identifying respective test operations to be performed by the test program upon all objects of the test cases, the first fields identifying a time when the respective central test operation is to be performed during execution of the test cases; second fields for storage of identifiers representing individual test activities unique to the respective test case, the individual test activity identifiers identifying respective test operations to be performed by the test program upon the objects of the respective test case, the second fields identifying a time when the respective individual test activity is to be performed during execution of the respective test cases,
- scheduling, by the computer, execution of the central test activities and the individual test activities by: scheduling execution of the central test activities upon the objects of all the test cases to occur simultaneously, scheduling execution of the individual test activities of the respective test cases according to their position with respect to the central test activities within the respective test cases, wherein execution of an individual test activity of a first test case occurs concurrently with execution of another individual test activity of a second test case, wherein execution of each individual test activity within a specific test case is independent of execution of individual test activities of any other test cases so that an addition of a new test case does not affect any existing test cases, and executing the central test activities and the individual test activities as scheduled, wherein each central test activity is only executed once at a synchronization point for all of the concurrently executing test cases.
54. A computer-implemented method of managing operations of a test program to test functionality of an application program, comprising:
- reading, by the computer, object data defining a plurality of test cases, each test case identifying unique object(s) corresponding to the test case, each test case further identifying central test activities to be performed by the test program upon all objects of the test cases and individual test activities to be performed by the test program upon the objects corresponding to the respective test case, execution of each individual test activity within a specific test case being independent of execution of individual test activities of any other test cases so that an addition of a new test case does not affect any existing test cases;
- scheduling, by the computer, execution of the central test activities and the individual test activities by: scheduling execution of the central test activities upon the objects of all the test cases to occur simultaneously, scheduling execution of the individual test activities of the respective test cases according to their position with respect to the central test activities within the respective test cases, wherein execution of an individual test activity of a first test case occurs concurrently with execution of another individual test activity of a second test case; and
- executing the central test activities and the individual test activities as scheduled,
- wherein each central test activity is only executed once at a synchronization point for all of the concurrently executing test cases.
55. The computer-implemented method of claim 54, wherein the test program is executed through a plurality of synchronization points, and wherein each of the central test activities is executed at a synchronization point.
56. The computer-implemented method of claim 55, further comprising:
- registering, by the computer, each of the objects with the test program to inform the test program about the central test activities at the sync points and the individual test activities of the test case identified by the object.
57. The computer-implemented method of claim 54, further comprising:
- updating the object data with a new plurality of test cases.
58. The computer-implemented method of claim 57, wherein the update includes adding at least one new test case to the existing plurality of test cases.
59. The computer-implemented method of claim 54, wherein the object data is stored as a data structure, the data structure including:
- the plurality of test cases, each test case identifying the object(s) to which the respective test case relates, the each test case storing: first fields for storage of identifiers representing the central test activities, the first fields identifying synchronization points at which the central test activities are to be performed; second fields for storage of identifiers representing the individual test activities unique to the respective test case, the first fields identifying a time during execution of the respective test case when the respective test activity is to be performed.
5634098 | May 27, 1997 | Janniro et al. |
5655072 | August 5, 1997 | Wolff |
5671351 | September 23, 1997 | Wild et al. |
5751941 | May 12, 1998 | Hinds et al. |
5974569 | October 26, 1999 | Nickles |
6002869 | December 14, 1999 | Hinckley |
6002871 | December 14, 1999 | Duggan et al. |
6031990 | February 29, 2000 | Sivakumar et al. |
6058493 | May 2, 2000 | Talley |
6304982 | October 16, 2001 | Mongan et al. |
6408403 | June 18, 2002 | Rodrigues et al. |
6601018 | July 29, 2003 | Logan |
6654911 | November 25, 2003 | Miles |
6662312 | December 9, 2003 | Keller et al. |
6701514 | March 2, 2004 | Haswell et al. |
6718537 | April 6, 2004 | Miles |
6889158 | May 3, 2005 | Penov et al. |
7020797 | March 28, 2006 | Patil |
7089534 | August 8, 2006 | Hartman et al. |
7113883 | September 26, 2006 | House et al. |
7159021 | January 2, 2007 | Boldman et al. |
7165256 | January 16, 2007 | Boudnik et al. |
7373636 | May 13, 2008 | Barry et al. |
20020124042 | September 5, 2002 | Melamed et al. |
20030056173 | March 20, 2003 | Copenhaver et al. |
20030208351 | November 6, 2003 | Hartman et al. |
20040015846 | January 22, 2004 | Haisraeli |
20040107415 | June 3, 2004 | Melamed et al. |
20040243381 | December 2, 2004 | Kuturianu et al. |
20060020920 | January 26, 2006 | Septon |
Type: Grant
Filed: Jun 17, 2004
Date of Patent: Sep 14, 2010
Patent Publication Number: 20050283761
Assignee: SAP AG (Walldorf)
Inventor: Rolf W. Haas (Schramberg)
Primary Examiner: Lewis A Bullock, Jr.
Assistant Examiner: Jue Wang
Attorney: Kenyon & Kenyon LLP
Application Number: 10/868,896
International Classification: G06F 9/44 (20060101);