This topic provides an overview of SOAtest’s web functional (cross-browser) testing capabilities. In this section:

Web Testing Introduction

Organizations often abandon automated web testing in favor of manual testing due to the false positives and maintenance issues associated with automated tests. SOAtest removes the barriers to automated web testing by isolating and testing individual application components for correct functionality across multiple browsers without requiring scripts. Dynamic data can be stubbed out with constant data to reduce test case noise. Validations can be performed at the page object level as well as the HTTP message level. SOAtest also verifies the client-side JavaScript engine under expected and unexpected conditions through asynchronous HTTP message stubbing.

Browser Recording and Cross-Browser Execution

The first step in web testing is browser recording, which is described in Browser Recording and Playback.

Once created, tests can be executed as described in Executing Functional Tests.

Extending and Reusing Web Scenarios

You can rapidly extend your recorded web scenarios to meet your goals. The following examples are common practices for extending and reusing web scenarios:

• Configuring cross-browser testing; see Configuring Browser Playback Options
• Configuring user actions; see Modifying User Actions Simulated by a Web Scenario
• Configuring validations; see Validating or Storing Values
• Configuring wait conditions; see Configuring Wait Conditions
• Configuring actions that occur before and after test execution; see Adding Set-Up and Tear-Down Tests.
• Configuring execution options, such as test sequence, test relationship, and test flow logic; see Configuring Test Suite Properties - Test Flow Logic, Variables, etc..
• End-to-end testing of scenarios that extend through web interfaces, backend services, ESBs, databases, and everything in between; see End-to-end Test Scenarios
• Load testing; see Load Test
• Penetration testing; see Penetration Testing
• Data-driven testing; see Parameterizing Tests with Data Sources, Variables, or Values from Other Tests.
• Using stubs and environments to configure a predictable and accessible test bed; see Configuring Testing in Different Environments.

Browser Support