Abstract: A system and method for self-learning and self-validating declarative testing are provided. In example embodiments, a user experience module identifies a declarative test representing a user experience being tested. A test execution module simulates a client machine including a client machine environment and executes the declarative test using the simulated client machine and the user behavior data of the specific user to generate test results. A validation module validates the test results by invoking at least one of plurality of validators, including at least one client-side validator and at least one server-side validator.

Abstract: A system and method for self-learning and self-validating declarative testing are provided. In example embodiments, a user experience module identifies a declarative test representing a user experience being tested. A test execution module simulates a client machine including a client machine environment and executes the declarative test using the simulated client machine and the user behavior data of the specific user to generate test results. A validation module validates the test results by invoking at least one of plurality of validators, including at least one client-side validator and at least one server-side validator.

Abstract: Described herein is a new approach for testing in which tests are instrumented and exposed as addressable resources using a REST-ful approach. With this new approach, instrumentation, provisioning and execution of tests are de-coupled, which is not the case with current, traditional testing approaches.

Abstract: A method for analyzing a test coverage of a software application specification by a test suite is provided. The method includes reading an assertion document for a specification. The assertion document has a corresponding tagged assertion for each assertion in the specification. Each tagged assertion is defined in a markup language. The method also includes reading a static file for defining tests of the test suite. The static file is defined in the markup language. The test suite is divided into tests and each test is divided into test cases. The static file is configured to include an entry for each test case and each entry is configured to include tagged assertions tested by the test case. Also included in the method is correlating each of the tagged assertions in the assertion document with the test cases in the static file so as to determine test coverage of the specification.

Abstract: A method for maintaining standardized test results is provided. The method includes executing a test suite that includes embedded reporter codes and generating uniform test results using the embedded reporter codes. The embedded reporter codes are configured to include data as to anticipated test results and rationale supporting the anticipated test results. The method also includes storing the uniform test results so as to allow viewing of the uniform test results.

Abstract: A method for maintaining standardized test results is provided. The method includes executing a test suite that includes embedded reporter codes and generating uniform test results using the embedded reporter codes. The embedded reporter codes are configured to include data as to anticipated test results and rationale supporting the anticipated test results. The method also includes storing the uniform test results so as to allow viewing of the uniform test results.

Abstract: A method for analyzing a test coverage of a software application specification by a test suite is provided. The method includes reading an assertion document for a specification. The assertion document has a corresponding tagged assertion for each assertion in the specification. Each tagged assertion is defined in a markup language. The method also includes reading a static file for defining tests of the test suite. The static file is defined in the markup language. The test suite is divided into tests and each test is divided into test cases. The static file is configured to include an entry for each test case and each entry is configured to include tagged assertions tested by the test case. Also included in the method is correlating each of the tagged assertions in the assertion document with the test cases in the static file so as to determine test coverage of the specification.

Abstract: A method for tracking assertions in an application is provided. The method includes providing a specification for the application, identifying each assertion in each chapter of the specification, and generating a markup language document. The specification is divided into chapters, which define functional aspects of the application. The markup language document has an associated tagged entry for each of the identified assertions. Each tagged entry has an identifier tag which correlates the tagged entry to a specific chapter of the specification.