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

摘要

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.

主权项

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.