Abstract: The present invention provides a method of testing a hypertext document for compliance with a selected criterion. The method (200) provides user prompts (201) for accepting user selections (202) of parameters to test a web page (or web pages) for compliance with selected rules. The web page is obtained (203) and sent, with selected rules, to a rules engine (204) for an analysis based on the selected rules (206). The raw analysis data is generated and stored (208). The analysis data is compiled and presented (210) to a user for error tracking and/or correction (212).

Abstract: Function level ownership may be applied. First, in response to running a plurality of different test cases, metrics correspond to a plurality of traces may be received. Each of the plurality of traces may respectively correspond to a plurality of outputs respectively produced by running each of the plurality of different test cases. Next, ownership data may be received. The ownership data may indicate a testing entity responsible for losing at least one function corresponding to a software program that was tested as a result of running the plurality of different test cases, in addition, the ownership data may indicate a developing entity responsible for developing at least one function corresponding to the software. Then, the ownership data may be applied to the metrics corresponding to the plurality of traces.

Abstract: A plurality of different test cases may be run. Next, in response to running the plurality of different test cases, a plurality of traces may be received. Each of the plurality of traces may respectively correspond to a plurality of outputs respectively produced by each of the plurality of different test cases. Then, the plurality of traces may be saved in a database. Each of the saved plurality of tracts may respectively have a unique trace ID. The trace ID for each the plurality of traces may comprise a test case ID and a run ID. Next, an input may be received comprising the test case ID and the run ID. Then, based on the received input, the database may be queried for a first trace within the plurality of traces. The first trace may correspond to the input. Next the first trace may he transmitted to a requestor.

Abstract: Code coverage data may be collected and reported. First, in response to running a plurality of different test cases, a first plurality of traces may be received. Each of the first plurality of traces may respectively correspond to a first plurality of outputs respectively produced by running each of the plurality of different test cases on a software program. Next, in response to a plurality of users running the software program, a second plurality of traces may be received. Each of the second plurality of traces may respectively correspond to a second plurality of outputs produced by the users running the software program. Then, the first plurality of traces may be compared to the second plurality of traces. A report may be created showing the comparison.

Abstract: Redundant test cases may be identified. First, in response to running a plurality of different first test cases, a plurality of first traces may be received. Each of the plural of first traces may respectively correspond to a plurality of outputs respectively produced by running each of the plurality of different first test cases. Next, at least one redundant test case from the plurality of different first test cases may be determined. The at least one redundant test case may have a corresponding redundant trace from the plurality of first traces. The redundant trace may comprise code coverage data corresponding to code blocks covered by code coverage data included in the plurality of first traces exclusive of the redundant trace. Then, in response to determining the at least one redundant test case from the plurality of different first test cases, a report may be produced identifying the redundant test case.