System and method for developing test cases using a test object library

Abstract

A method, apparatus, article of manufacture, and a memory structure for generating a test code for an automatic procedure is disclosed. The method comprises the steps of defining a source file having a plurality of tags associated with a member of a library of executable code objects defining a set of instructions for performing a portion of the automatic test procedure, generating a test plan in a conventional language from the source file, and generating an automated test code for the automated test procedure from the source file. In one embodiment, a test index identifying system elements tested by the test code is generated and incorporated into the test plan, allowing the user to verify that all desired system elements are exercised by the automated test code. The article of manufacture comprises a data storage device tangibly embodying instructions to perform the method steps described above. The apparatus comprises means for defining a source file having a plurality of tags, wherein each tag is associated with a member of a library of executable code objects defining a set of instructions for performing a portion of an automatic test procedure, means for generating a test plan in a conversational language from the source file, and means for generating an automated test code for the automatic test procedure from the source file.

Description

[0001] This application is related to the following co-pending and commonly assigned patent application, which application are incorporated by reference herein:[0002] Application Ser. No. ______, entitled "GRAPHICAL USER INTERFACE FOR DEVELOPING TEST CASES USING A TEST OBJECT LIBRARY," filed on same date herewith, by Thomas J. Pavela, attorney's docket number ST9-98-108.[0003] 1. Field of the Invention[0004] The present invention relates to systems and methods of generating test cases, and in particular to a method and system for generating test cases using a test object library.[0005] 2. Description of the Related Art[0006] The past two decades have seen a rapid proliferation of computer application programs. To be competitive, software applications must be responsive to customer's rapidly evolving needs, and must be as bug-free as possible. One method of assuring that a software release is bug free by testing the software with a wide variety of test cases, carefully chosen to test...

AI Technical Summary

Benefits of technology

[0089] The present invention allows users to rapidly generate and debug self-documenting test cases. This is accomplished by providing the user with a library of test objects, each of which is associated with a tag. The user creates a source file using the tags to refer to the desired test objects. To further assist the user, a test case GUI is supplied that presents a visual representation of the test objects in the library and a listing of the source code. The user can compose the source code by selecting the proper location in the source code file, and selecting the appropriate test code object. The user is prompted to choose between a selection of test code object parameters, eliminating the possibility that the user will select test object parameters that do not exist or are out of range. The GUI's user prompts are also context-sensitive in that the options presented to the user can be a function of the test objects and parameter selections currently in the source code.

Problems solved by technology

In such cases, the individuals writing the test cases should be familiar the operating system, communication protocols for all of the elements in the system, but unfortunately, there are few individuals with all of the skills necessary to write a complete test program.

The development and execution of software test cases also takes an large investment of time and resources, and can delay the timely introduction of a software product to the marketplace.

Invariably, the test code does not function as desired, and changes must be made to the code, often implicating major changes in the test plan as well.

However, in the rush to bring the software product to market, it often occurs that the test plan is never updated to reflect the new test procedures.

Even if the exigencies of the situation permit the test plan to be updated, this effort usually involves a significant amount of time and money.

Images