Systems and methods for testing software and for storing and tracking test assets with the software

• US 9,009,666 B1
• Filed: 05/30/2008
• Issued: 04/14/2015
• Est. Priority Date: 05/30/2008
• Status: Active Grant

• Current Assignee: United Services Automobile Association
• Original Assignee: United Services Automobile Association
• Inventors: Wiradarma, Andre, Ensminger, John, Martindale, Bradley L.
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): UNG, LANNY N
• Application Number:
  US12/130,114
• Time in Patent Office: 2,510 Days
• Field of Search: 717/122
• US Class Current: 717/122
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version

Abstract

A test for a piece of software may be created, and stored with the software. The software and the test may be stored in a code repository, where the test appears in a dependency graph, and is subject to version tracking, in a manner similar to other components of the software. These mechanisms may be used to determine whether a test is current relative to the software component that the test is used to evaluate. Tests may be developed by the software developers, by test developers, or by anyone else. Tests may be specified in a generic format, such as an eXtensible Markup Language (XML) format that meets some schema. The generic format test may be converted into a script that is usable with various script engines, thereby allowing tests to be developed in a test-engine-independent manner.

Claims

1. A non-transitory computer-readable medium comprising computer-readable instructions for testing and implementing software, the computer-readable instructions comprising:

instructions that store a code component in a repository wherein plurality of code components that make up the software includes the code component;

instructions that store, in said repository, a specification of a first test of said code component, said repository maintaining a dependency graph that indicates a dependency between said specification and said code component;

instructions that receive a request to perform a second test on the software, wherein the software makes use of the code component;

instructions that determine that said specification having the dependency with said code component is up to date relative to said code component by comparing a date associated with said specification and a date associated with said code component;

instructions that test the code component included in the software based on the up to date specification; and

instructions that provide one version of the code component if a first release of the software is called for implementation and provide another version of the code component if a second release of the software is called for implementation.

2. The computer-readable medium of claim 1, wherein the code component included in the software is tested using a test engine, and wherein the computer-readable instructions further comprise:

instructions that convert said specification into a language used by said test engine.

3. The computer-readable medium of claim 1, wherein the computer-readable instructions further comprise:

instructions that store, in said repository, version information about said code component and said specification.

4. The computer-readable medium of claim 1, wherein said date associated with said code component is a date on which said code component was last updated, and wherein date associated with said specification is a date on which said specification was last updated.

5. The computer-readable medium of claim 1, wherein said specification is in an eXtensible Markup Language (XML) format, and wherein the computer-readable instructions further comprise:

instructions that use an XML schema to interpret said specification.

6. The computer-readable medium of claim 1, wherein said request is received from a test server, wherein said code component included in the software is tested on said test server, and wherein the computer-readable instructions further comprise:

instructions that deliver said code and said specification to said test server.

7. The computer-readable medium of claim 1, wherein said specification indicates a variable to be used in testing the code component included in the software, and wherein the computer-readable instructions further comprise:

instructions that retrieve, from a data store, a value to be substituted in place of said variable; and

instructions that provide said value as input to the software.

8. A system for testing and implementing software, comprising:

a computer system including a processor; and

non-transitory computer-readable medium storing instructions executable by the processor to;

store a code component in a repository wherein a plurality of code components that make up the software includes the code component;

store, in said repository, a specification of a first test of said code component, said repository maintaining a dependency graph that visually indicates a dependency between said specification and said code component;

receive a request to perform a second test on the software, wherein the software makes use of the code component;

determine that said specification having the dependency with said code component is up to date relative to said code component by comparing a last modified date associated with said specification and a last modified date associated with said code component;

test the code component included in the software based on the up to date specification; and

provide one version of the code component if a first release of the software is called for implementation and provide another version of the code component if a second release of the software is called for implementation.

9. The system of claim 8, wherein the code component included in the software is tested using a test engine, and wherein the system further comprises a converter that converts said specification into a language used by said test engine.

10. The system of claim 8, further comprising

instructions executable by the processor to store in said repository, version information about said code component and said specification.

11. The system of claim 8,

wherein the last modified date associated with said code and the last modified date associated with said specification are stored in said repository.

12. The system of claim 8, wherein said specification is in an eXtensible Markup Language (XML) format, and wherein the system further comprises a converter that:

uses an XML schema to interpret said specification.

13. The system of claim 8, wherein said request is received from a test server, wherein said code component included in the software is tested on said test server, and wherein the system further included instructions executable by the processor that:

deliver said code and said specification to said test server.

14. The system of claim 8, wherein said specification indicates a variable to be used in testing code component included in the software, and wherein the system further comprises instructions executable by the processor that:

retrieve, from a data store, a value to be substituted in place of said variable; and

provide said value as input to the software.

15. A method of testing and implementing software, the method comprising:

storing a code component in a repository wherein a plurality of code components that make up the software includes the code component;

storing, in said repository, a specification of a first test of said code component, said repository maintaining a dependency graph that indicates a dependency between said specification and said code component;

receiving a request to perform a second test on the software, wherein the software makes use of the code component;

determining that said specification having the dependency with said code component is up to date relative to said code component by comparing a last modified date associated with said specification and a last modifies date associated with said code component;

testing the code component included in the software based on the up to date specification; and

providing one version of the code component if a first release of the software is called for implementation and provide another version of the code component if a second release of the software is called for implementation.

16. The method of claim 15, wherein the code component included in the software is tested using a test engine, and wherein the method further comprises:

converting said specification into a language used by said test engine.

17. The method of claim 15, further comprising:

storing, in said repository, version information about said code component and said specification.

18. The method of claim 15, wherein said specifications in an eXtensible Markup Language (XML) format, and wherein the method further comprises:

using an XML schema to interpret said specification.

19. The method of claim 15, wherein said request is received from a test server, wherein said code component included in the software is test on said test server, and wherein the method further comprises:

delivering said code and said specification to said test server.

20. The method of claim 15, wherein said specification indicates a variable to be used in testing said code component included in the software, and wherein the method further comprises:

retrieving, from a data store, a value to be substituted in place of said variable; and

providing said value as input to the software.