TestWeaver is a tool for automated test and validation of control functions. TestWeaver generates, runs and evaluates thousands of test scenarios automatically. Each test scenario is a sequence of inputs over time, automatically performed using simulationduring simulations. TestWeaver generates the tests in a reactive, informed way, trying to learn the system behavior from the results of the past previous simulations, in order to increase state coverage and to actively worsen sub-optimal scenarios until the system behavior is really bad, i.e. a bug or a design flaw has been found. TestWeaver also supports as well classical test automation methods, based on:
Run and export experiments as JUnit XML
TestWeaver can export the experiment results as reports in the JUnit XML format. This format is easy to integrate in Jenkins. TestWeaver will run in an automation mode that does not require any user interaction. After the export is finished TestWeaver closes automatically.
- To start TestWeaver you are required to set the path to the TestWeaver project, the experiment names to be run and the path to the location where to export the JUnit XML result file. The experiment names can be specified using the wildcard syntax.
- This starts automatically one or more experiments from automatically from the named project one after the other. Before being started, any existing scenarios of the selected experiments are deleted, so that the test results will be computed from scratch and are therefore up-to date.
- Optionally, you can activate the generation of HTML reports of the executed experiments by setting the path to the directory where to store the HTML reports.
Optionally, you can specify a file with configuration parameters that have to be used for the current test and a file with silver parameters.
- After the experiments are finished their results are exported in the JUnit XML format in a file called
unit-test.xmlin the named
- In case you are using TestWeaver LIGHT the automatic scenario generation that can be performed by TestWeaver is disabled. In this case the experiments run user defined scripts and test databases, only. Besides Additionally to the test exported test cases exported for the user defined scripts and test databases, an additional test case will be reported for the consistency of the used SUT Configuration Parameters.
- default export view: this exports the user defined scripts and the scenarios from the test databases individually as test cases. In addition, the following properties are mapped to test cases as well:
- completeness of tested requirement watchers, thus checking the coverage of the requirements monitored by watcher instruments.
- in case the automatic generation is enabled in the experiment specification, then one more test case will be exported, namely one that merges the pass/fail results of all automatically generated scenarios. For instance, if at least one automatically generated scenario detected a failure then the merged test case is marked as failed.
- export with instruments view by checking
Instrument viewcheckbox: this gives more details than the default view, namely this exports every reporter and watcher instrument, as well as the termination monitor as a test case in the exported test suite.
- This view is the recommended one for the export of experiments that use the automatic scenario generation.