This topic section describes the preconfigured, "built-in" Test Configurations that are included with SOAtest.In this section:
Change Impact Analysis
| Name | Description |
|---|
| Perform Change Impact Analysis | Executes the Change Impact Analysis functionality, which prompts Change Advisor to report how assets’ messages are impacted by a change in the related definition file (for example, WSDL, schema, WADL, OpenAPI/Swagger, RAML). |
Functional Testing Category
| Name | Description |
|---|
| Run Automated Server Tests | Executes functional tests without calculating API coverage and with reporting of traffic for all tests (so reports include a "Test Traffic [All Tests]" section that provides traffic for every test execution, whether or not it was successful). Designed for automated server-based test execution (such as via the API or through Parasoft CTP). |
| Run Web Functional Tests in All Browsers | Executes each web scenario in Firefox, Chrome, Safari, and Edge (where applicable). |
| Run Web Functional Tests in Browser Specified by Tests | Executes each web scenario using the browser playback settings configured in the test scenario’s Browser Playback Options tab. If you have multiple scenarios, each with different browser playback settings, this Test Configuration would run all the scenarios in the designated browser(s). |
| Run Web Functional Tests in Edge | Executes each web scenario in Edge. If a web scenario was configured to run only in one or more other browsers, it will not be run. |
| Run Web Functional Tests in Chrome | Executes each web scenario in Chrome. If a web scenario was configured to run only in one or more other browsers, it will not be run. |
| Run Web Functional Tests in Firefox | Executes each web scenario in Firefox. If a web scenario was configured to run only in one or more other browsers, it will not be run. |
| Run Web Functional Tests in Safari | Executes each web scenario in Safari. If a web scenario was configured to run only in one or more other browsers, it will not be run. |
Load Testing Category
| Name | Description |
|---|
| Configure for Load Test | Configures browser-based web scenarios to run in a browserless load test environment. See Configuring Tests for details. |
| Validate for Load Test | Executes tests in load testing mode and alerts you to any outstanding issues that might impact your load testing, for example, incorrectly configured HTTP requests. See Validating Tests for details. |
Static Analysis Category
| Name | Description |
|---|
| Check HTML Well-Formedness | Reports missing end tags. Reports if default values need to be added for attributes (that is, those that are "true" by default). Reports attribute values that do not have quotes around them. Reports if attributes that require numerical values have non-numerical values. Reports orphaned end tags. Reports missing required tags. Documents require <HTML> <HEAD> <TITLE> </TITLE> </HEAD> <BODY> </BODY> </HTML> Framesets require <HTML> <HEAD> <TITLE> </TITLE> </HEAD> <FRAMESET> </FRAMESET> </HTML> |
| Check Links | Detects broken links, program failures, and other critical site problems. |
| Check Spelling | Checks for spelling errors in HTML and XML files. |
| Check Web Standards | Verifies whether code follows coding standards for HTML, JavaScript, CSS, and ASP/VBScript. |
| Check XML Well-formedness | Checks whether XML files are well-formed and (optionally) validates them. |
| Schema Best Practices | Checks compliance to best practices for ensuring schema interoperability, maintainability, and security. |
| WSDL Best Practices | Checks compliance to best practices for ensuring WSDL interoperability, maintainability, and security. |
Accessibility Sub-Category
...