System for creating, storing, and using customizable software test procedures

• US 20030159089A1
• Filed: 09/25/2002
• Published: 08/21/2003
• Est. Priority Date: 02/21/2002
• Status: Active Grant

• Current Assignee: Siemens Medical Solutions USA Incorporated (Siemens AG)
• Original Assignee: Siemens Medical Solutions Health Services Corporation (Siemens AG)
• Inventors: DiJoseph, Philip
• Granted Patent: US 7,055,067 B2
• Time in Patent Office: Days
• US Class Current: 714/38
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases

Abstract

A system and method for software test is disclosed that allows user management and adaptation of test procedures and the resulting test data. In an embodiment, the system and method provide a cross-platform user interface which allows testing to be conducted on a plurality of platforms, i.e. it is not integrated with a single platform or language (e.g., C++, Visual Basic, Java, or the like). The method further allows a user to customize a predetermined set of system characteristics relating to the stored test procedure. It is emphasized that this abstract is provided to comply with the rules requiring an abstract which will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope of meaning of the claims.

Claims

1. ) A software test method for managing user adaptable test procedures and resulting test data, comprising the steps of:

a. storing a first test procedure for use in user assisted testing of a set of functions of an executable application;

b. allowing a user to customize a predetermined set of system characteristics relating to the stored test procedure;

c. acquiring task data identifying task steps performed by the first test procedure and the user in the user assisted testing of the set of functions of the executable application;

d. generating an executable second test procedure corresponding to the first test procedure for automatically exercising the set of functions of the executable application without user assistance; and

e. acquiring result data derived from exercising the executable application by executing at least one of (i) the first test procedure or (ii) the second test procedure.

2. ) A method according to claim 1, wherein:

a. the predetermined set of system characteristics relating to the stored test procedure comprise at least one of (i) manipulating a field, (ii) manipulating a table, (iii) manipulating a report, and (iv) manipulating a user interface.

3. ) A method according to claim 2, wherein:

a. manipulating a field comprises at least one of (i) adding a field, (ii), deleting a field, and (iii) modifying a field attribute.

4. ) A method according to claim 2, wherein:

a. the user interface comprises at least one of (i) an appearance of a graphical interface, (ii) content of the graphical interface, (iii) an appearance of a menu, and (iv) content of the menu.

5. ) A method according to claim 1, wherein:

a. the step of acquiring task data includes;

i. observing and collating user initiated keyboard key strokes; and

ii. analyzing a detailed functional specification.

6. ) A method according to claim 1, wherein:

a. the step of acquiring task data includes the step of acquiring at least one of (i) test related timing data, (ii) memory usage related data, and (iii) command sequence data.

7. ) An executable application test method for managing user adaptable test procedures and reporting on user adaptable resulting test data, comprising the steps of:

a. providing a cross-platform user interface to a database, the user interface useful in customizing a predetermined set of database characteristics relating to a stored test procedure and a report of test results;

b. storing a test procedure in a test procedure repository of the database;

c. importing a requirement associatable with the test procedure from predetermined source of requirements;

d. creating an automated procedure placeholder, the procedure placeholder comprising a retrievable description in host automation language of an actual test step to be performed;

e. executing the test procedure;

f. entering a test result obtained from executing the test procedure into a test results repository in the database; and

g. creating a report reflective of the test result.

8. ) A method according to claim 7, wherein:

a. the stored test procedure is at least one of (i) a manual test procedure, (ii) an automated test procedure, and (iii) a combination of a partially manual and a partially automated test procedure.

9. ) A method according to claim 7, further comprising the steps of:

a. entering data related to a time of executing the test procedure; and

b. allowing the created report to reflect the data related to the time.

10. ) An executable application test method for managing test procedures and resulting test data, comprising the steps of:

a. storing a first test procedure for use in testing of a set of functions of an executable application;

b. associating the first test procedure with document information describing a test requirement of the executable application;

c. allowing a user to customize a predetermined set of system characteristics relating to the stored test procedure;

d. initiating execution of the first test procedure;

e. acquiring result data derived by execution of the first test procedure; and

f. recording test outcome related information based on the acquired test data.

11. ) A method according to claim 10, including the further step of:

a. providing user customizable report information, based on the recording test outcome related information and indicating whether individual requirements of the test requirements were met.

12. ) A method according to claim 11, including the further step of:

a. associating a function of the executable application to be exercised with a corresponding individual test procedure.

13. ) A method according to claim 11, wherein:

a. the report information supports certification by a standards associated organization including at least one of ((i) International Standards Organization (ISO), (ii) Capability Maturity Model (CMM), (iii) the United States of America Food and Drug Administration (FDA), and (iv) American National Standards Institute (ANSI).

14. ) A method according to claim 10, including the further step of:

a. collating and storing test failure data and associated test step timing information.

15. ) A method according to claim 10, including the further step of:

a. compiling linking information associating the first test procedure with individual elements of the executable application exercised by the first test procedure.

16. ) A method according to claim 15, wherein:

a. the individual elements of the executable application comprise at least one of (i) an executable procedure used by the executable application, (ii) a function implemented by the executable application, (iii) a user interface form used by the executable application, and (iv) a software object employed by the executable application.

17. ) A method for managing test procedures and resulting test data, comprising the steps of:

a. creating an entry in a database for a pre-existing requirement for executable application, the database being accessible using a second software application;

b. receiving customization data to customize a predetermined set of system characteristics relating to the stored test procedure in the database;

c. creating a test procedure for the requirement;

d. storing the test procedure in the database; and

e. linking the test procedure to the requirement in the database.

18. ) A method according to claim 17, wherein:

a. the second software application comprises a computer aided software engineering tool.

19. ) A method of creating and maintaining a test procedure for a software system, comprising:

a. initializing a software test tool;

b. determining a software test tool requirement;

c. modifying a predetermined set of elements of the software test tool based on the software test tool requirement;

d. modifying the software test tool to allow for at least one of (i) importation of data from an external software application and (ii) exportation of data to an external software application; and

e. modifying the software test tool to allow for meeting certification standards.

20. ) The method of creating and maintaining a test procedure for a software system of claim 19, wherein:

a. determining a software test tool requirement further comprises at least one of (i) reviewing an internal testing policy for a test requirement to be satisfied by the software test tool, (ii) reviewing an internal testing procedure for a test requirement to be satisfied by the software test tool, and (iii) reviewing an internal testing procedure for a test metric requirement needed to substantiate a testing effort of the software test tool.

21. ) The method of creating and maintaining a test procedure for a software system of claim 19, wherein:

a. the test tool elements comprise at least one of (i) a manipulatable field, (ii) a manipulatable table, (iii) a manipulatable report, and (iv) a manipulatable user interface.

22. ) The method of creating and maintaining a test procedure for a software system of claim 19, wherein:

a. the certification standards comprise a standard from at least one of (i) International Standards Organization (ISO), (ii) Capability Maturity Model (CMM), (iii) the United States Food and Drug Administration (FDA), and (iv) American National Standards Institute (ANSI).

23. ) A system for creating and maintaining test procedures, comprising:

a. a user customizable certification database, further comprising;

i. a requirement repository for an executable application; and

ii. a test procedure repository linked to the software application requirements repository; and

b. a user interface adapted to allow a user to customize a predetermined set of system characteristics relating to the database.

24. ) A system according to claim 23, wherein:

a. the predetermined set of system characteristics relating to the stored test procedure comprise at least one of (i) manipulating a field, (ii) manipulating a table, (iii) manipulating a report, and (iv) manipulating the user interface.

25. ) A system according to claim 23, wherein:

a. the test procedure repository comprises elements, the elements comprising at least one of (i) test requirements, (ii) test procedures, (iii) test results, and (iv) test references.

26. ) The system of claim 25, wherein:

a. each element in the test procedure repository is linked to at least one requirement in the software application requirements repository.