TESTING SOFTWARE WITH A BUILD ENGINE
First Claim
1. At a build engine in a computerized environment, the build engine comprising one or more targets otherwise configured to build a software program when executed through the build engine, a method of testing a preliminary version of software without necessarily building an end-user version of the software, comprising the acts of:
- receiving one or more function calls for a project details target, the one or more project details target calls including at least an indication of software to be tested in a project file;
receiving one or more function calls for a pre-run target, the one or more pre-run target calls identifying one or more set up actions;
receiving one or more function calls for a scenario target, the one or more scenario target calls including a request for one or more actions to be executed by the software and one or more validations to be performed after executing the one or more actions;
receiving one or more function calls for a post-run target, the one or more post-run target calls identifying one or more finishing actions; and
upon executing the one or more function calls, generating a feedback report for the project file.
2 Assignments
0 Petitions
Accused Products
Abstract
Implementations of the present invention include use of a build engine as a test framework driver. Since the build engine can be used with a variety of test frameworks, new test drivers do not necessarily need to be continually created for new software programs. In addition, since the build engine can be configured to use objects, actions and validations can be written in a wide variety of languages, and can be easily reused. Furthermore, use of the build engine as a test framework driver, particularly within the context of XML, can allow complex scenarios and test cases to be readily automated, without the learning curve and compilation requirements typically associated therewith. In particular, a software tester simply visually compose an automated test case from a library of available tasks without having to write a test code or scripts.
32 Citations
20 Claims
-
1. At a build engine in a computerized environment, the build engine comprising one or more targets otherwise configured to build a software program when executed through the build engine, a method of testing a preliminary version of software without necessarily building an end-user version of the software, comprising the acts of:
-
receiving one or more function calls for a project details target, the one or more project details target calls including at least an indication of software to be tested in a project file; receiving one or more function calls for a pre-run target, the one or more pre-run target calls identifying one or more set up actions; receiving one or more function calls for a scenario target, the one or more scenario target calls including a request for one or more actions to be executed by the software and one or more validations to be performed after executing the one or more actions; receiving one or more function calls for a post-run target, the one or more post-run target calls identifying one or more finishing actions; and upon executing the one or more function calls, generating a feedback report for the project file. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. In a computerized environment comprising a build engine installed therein and a testing computer having access to the build engine, a method of testing a preliminary version of software through the testing computer system and the build engine without otherwise creating an end-user version of the software, comprising the acts of:
-
identifying one or more project details, the project details including a name of a project and a number of scenarios running in accordance with a project to test software of interest; identifying one or more components to be initiated in order to test the software of interest; identifying one or more scenarios that include a set of one or more actions and at least one validation to be performed for each set of one or more actions; generating a project file that includes a call to a target for each identified one or more project details, each identified one or more components to be initiated, and each identified scenario; and passing one or more instructions to execute the project file at a build engine. - View Dependent Claims (14, 15, 16, 17, 18, 19)
-
-
20. In a computerized environment that includes a build engine having one or more targets otherwise configured to build a software program when executed through the build engine, a computer program product having computer-executable code stored thereon that, when executed, cause one or more processors in a computer system to perform a method of testing a preliminary version of software without necessarily building an end-user version of the software, comprising the acts of:
-
receiving one or more function calls for a project details target, the one or more project details target calls including at least an indication of software to be tested in a project file; receiving one or more function calls for a pre-run target, the one or more pre-run target calls identifying one or more set up actions; receiving one or more function calls for a scenario target, the one or more scenario target calls including a request for one or more actions to be executed by the software and one or more validations to be performed after executing the one or more actions; receiving one or more function calls for a post-run target, the one or more post-run target calls identifying one or more finishing actions; and upon executing the one or more function calls, generating a feedback report for the project file.
-
Specification