Auto-executing tool for developing test harness files
AssigneeAlcatel-Lucent USA Inc.
InventorsMan K. Kwong, Roberta C. Kwong, Lai-Cherng Suen, Chen-Wan Wang
Life of this patent
Estimating the term…
Abstract
A test harness development component streamlines the design of regression test harnesses for testing text-based software. An auto-recording tool to automatically record the input and output data in an actual run of the testing session and to automatically generate a test harness. The test harness development component provides an auto-executing tool to automatically run the test harness in subsequent regression tests. The test harness language is used to specify the tests, validation rules of the results, and any other rules for running the test of a test harness. The test harness language is human-readable and emulates the manual test procedures with very little overhead.
Claims24
A method, comprising the steps of:
- reading, without user intervention, an automatic regression test of a test harness file;
- reading non-graphical software to be tested;
- executing, without user intervention, the automatic regression test and producing test results from the non-graphical software;
- and
- determining, without user intervention, whether the test results pass or fail by their comparison to contents of a benchmark file, if the benchmark file is associated with the test harness file;
- tabulating, without user intervention, pass/fail statistics;
- recording, without user intervention, the pass/fail statistics;
- displaying at least a portion of the test results if the benchmark file is associated with the test harness;
- displaying complete test results to the user if no benchmark file is associated with the test harness;
- and
- masking a time-stamp portion of the test results through employment of a subroutine that converts the time-stamp portion of the test results to a pre-determined string prior to comparing the results to the contents of the benchmark file.
A method, comprising the steps of:
- reading, without user intervention, an automatic regression test of a named test harness file;
- reading non-graphical software to be tested;
- executing, without user intervention, the automatic regression test and producing test results from the non-graphical software;
- determining, without user intervention, whether the test results pass or fail by their comparison to contents of a benchmark file;
- if a benchmark file is associated with the named test harness file, determining, without user intervention, whether the test results pass or fail by their comparison to contents of the benchmark file associated with the test harness file;
- if no benchmark file is associated with the named test harness file, capturing the test results and saving the test results to a benchmark file associated with the named test harness file;
- displaying at least a portion of the test results if a benchmark file is associated with the test harness;
- displaying complete test results to the user if no benchmark file is associated with the test harness;
- and
- masking a time-stamp portion of the test results through employment of a subroutine that converts the time-stamp portion of the test results to a pre-determined string prior to comparing the results to the contents of the benchmark file.
A method, comprising the steps of:
- receiving a user command to generate a benchmark file, using a named test harness file;
- reading, without user intervention, automatic regression tests of a named test harness file;
- reading, without user intervention, non-graphical software to be tested;
- executing, without user intervention, the automatic regression tests and producing test results from the non-graphical software;
- capturing, without user intervention, the test results;
- saving, without user intervention, the test results in a benchmark file;
- and
- masking a time-stamp portion of the test results through employment of a subroutine that converts the time-stamp portion of the test results to a pre-determined string prior to comparing the results to the contents of the benchmark file.
Dependencies are inferred from the claim text.