Page tree

Skip to end of metadata
Go to start of metadata

This topic describes the preconfigured "built-in" Test Configurations that are included with SOAtest. In this section:

Code Review Category

NameScopeCode Review
Post-CommitAll project filesTemplate code review configuration for teams who want to review code after it is committed to source control
Pre-CommitOnly files added or modified locallyTemplate code review configuration for teams who want to review code before it is committed to source control

Functional Testing Category

NameDescription
Run Automated Server TestsExecutes 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 (e.g., via the API or through Parasoft CTP).
Run Web Functional Tests in All  BrowsersExecutes each web scenario in Firefox, Chrome, Safari, and Internet Explorer (as applicable).
Run Web Functional Tests in  Browser Specified by TestsExecutes 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 EdgeExecutes 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 ChromeExecutes 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 FirefoxExecutes 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 Internet ExplorerExecutes each web scenario in Internet Explorer. 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 SafariExecutes 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

NameDescription
Configure for Load TestConfigures browser-based web scenarios to run in a browserless load test environment. See Configuring Tests for details.
Validate for Load TestExecutes 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.

Security Category

NameDescription
Run Hybrid Analysis Penetration Tests for Web ApplicationsExecutes penetration testing (using attacks designed for web applications) with runtime error detection. See Penetration Testing for details.
Run Hybrid Analysis Penetration Tests for Web ServicesExecutes penetration testing (using attacks designed for web services) with runtime error detection. See Penetration Testing for details.
Run Penetration Tests for Web ApplicationsExecutes penetration testing (using attacks designed for web applications). See Penetration Testing for details.
Run Penetration Tests for Web ServicesExecutes penetration testing (using attacks designed for web services). See Penetration Testing for details.

Static Analysis Category

NameDescription
Check HTML Well-Formedness

Reports missing end tags.

Reports if default values need to be added for attributes (i.e., 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 LinksDetects broken links, program failures, and other critical site problems.
Check SpellingChecks for spelling errors in HTML and XML files.
Check Web StandardsVerifies whether code follows coding standards for HTML, JavaScript, CSS, and ASP/VBScript.
Check XML Well-formednessChecks whether XML files are well-formed and (optionally) validates them.
Schema Best PracticesChecks compliance to best practices for ensuring schema interoperability, maintainability, and security.
WSDL Best PracticesChecks compliance to best practices for ensuring WSDL interoperability, maintainability, and security.

Accessibility Sub-Category

NameDescription
Recommended Section 508Monitors compliance to critical and recommended Section 508 accessibility guidelines.
Recommended WCAG 2.0Monitors compliance to recommended WCAG 2.0 accessibility  guidelines.
Section 508Monitors compliance to the most critical Section 508 accessibility guidelines.
WCAG 1.0 - Level 1

Monitors compliance to Level 1 WCAG 1.0 accessibility guidelines.

Level 1 success criteria:

  1. Achieve a minimum level of accessibility through markup, scripting, or other technologies that interact with or enable access through user agents, including assistive technologies.
  2. Can reasonably be applied to all Web resources.
WCAG 1.0 - Level 1 and 2

Monitors compliance to Level 1 and Level 2  WCAG 1.0 accessibility guidelines.

Level 2 success criteria:

  1. Achieve an enhanced level of accessibility through one or both of the following:
    1. markup, scripting, or other technologies that interact with or enable access through user agents, including assistive technologies
    2. the design of the content and presentation
  2. Can reasonably be applied to all Web resources.
WCAG 1.0 - Level 1, 2, and 3

Monitors compliance to Level 1, Level 2, and Level 3 WCAG 1.0 accessibility guidelines.

Level 3 success criteria:

  1. Achieve additional accessibility enhancements for people with disabilities.
  2. Are not applicable to all Web resources.
WCAG 2.0 - Level AMonitors compliance to Level A WCAG 2.0 accessibility guidelines.
WCAG 2.0 - Level A and AAMonitors compliance to  Level A and AA  WCAG 2.0 accessibility guidelines.
WCAG2.0 - Level A, AA, and AAAMonitors compliance to Level A, AA, and AAA WCAG 2.0 accessibility guidelines.

Code Review Category

NameScopeCode Review
Pre-CommitOnly files added or modified locally

For teams who want to review code before it is committed to source control.

To use this Test Configuration, the Code Review Preference Show user assistant during scanner run setting must be enabled so that the author can designate the appropriate reviewer(s). See the Code Review for details.

Post-Commit (Template)All project files modified in the previous day

For teams who want to review code after it is committed to source control.

This Test Configuration must be duplicated and customized prior to use (e.g, to specify author-reviewer mappings). See  the Code Review for details.

Post-Commit (Assign All)All project files modified in the previous day

For teams who want to review code after it is committed to source control.

This Test Configuration can be used without customization. It includes a mapping for the local code review user; it assigns all revisions found in scope (for any author) to the current user.

See the Configuring Test Configurations and Rules for Policies to learn how to develop custom Test Configurations that are tailored to your projects and team priorities.

  • No labels