...
| Generate recommendations | Enable this option to generate element locator recommendations. Selenic analyzes previous test runs to generate recommendations. The test must be successfully executed with Selenic at least once for Selenic to generate recommendations. The following options are available:
| |||||
|---|---|---|---|---|---|---|
| Self-healing | Self-healing allows test execution to continue when changes to the application may otherwise halt testing activities. Self-healing is typically enabled when executing tests from the command line. Enable this option and configure the following self-healing settings. Locators Enable this option and Selenic will automatically attempt to update broken element locators during execution. Selenic uses historical data about successful test executions to determine the best possible locator to replace a broken locator. Healed locators are flagged and included in the report for further investigation. Wait conditions Enable this option and specify by how much Selenic should extend Selenium wait conditions to prevent a timeout. You can specify a percentage of the original value that should be added when a wait condition is identified. For example, if a wait condition is configured for You can also specify a minimum number of seconds to add for all wait conditions identified by Selenic in the Minimum additional time (seconds) field. | |||||
| Take screenshots on failures | Enable this option to take a screenshot of the browser when a failure occurs. | |||||
| Open HTML report after execution | Enable this option to automatically open the report when Selenic finishes running. The report will open either in an internal or external browser. You can configure how the report opens in the IDE preference settings. When this option is enabled, the Report when execution time exceeds threshold option becomes available. | |||||
| Report when execution time exceeds threshold | Enable this option to use the performance benchmarking feature. During performance benchmarking, the average execution duration per test method is calculated based on a minimum set of test runs. Test methods that exceed the average duration by a specified percentage are flagged in the report. Only runs for passing tests are included in the calculation when determining the average. By default, at least five test runs are required to benchmark performance. The minimum number of test runs is only configurable when running Selenic on the command line (see -performanceBenchmarking). By default, the benchmark threshold is 20 percent, but you can configure the threshold in the Execution time threshold (percent) field. | |||||
| Execution time threshold (percent) | Specifies the test execution duration threshold for the current test run against the average execution time. If tests in the current run exceed the average test duration by more than the specified percentage, tests will be flagged in the HTML report (see Viewing the Report). The Report when execution time exceeds threshold must be enabled to specify the threshold. Default is 20 percent. | |||||
| Create API tests with Parasoft SOAtest | Enable this option to create API tests for REST calls made by the application under test during test execution. API tests will be added to the workspace of the SOAtest server specified in the API Test Creation Options. A separate license feature for API test creation is required for the SOAtest server. See Parasoft Recorder for details about API test creation.
Only one .tst file can be created at a time if you enable this option. If you are running test tests concurrently, API tests will only be created for one scenario at time. The following error will be shown in the log for other scenarios running at the same time:
|