Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Table of Contents

Web Testing Introduction

Web interface testing can be difficult to automate. Teams often abandon automated testing in favor of manual testing because automated tests produce many false positives—or because so much time and effort is required to maintain the test suites.

SOAtest is designed to reduce these obstacles. It isolates and tests 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.

Selenium WebDriver Engine and Parasoft Native Driver (Legacy) Engine

Since version 9.8, the Selenium WebDriver is available for playback of web scenarios. The Parasoft Native Driver (legacy) engine is still available as well.

For details, see About the Selenium WebDriver Engine.

Browser Recording and Cross-Browser Execution

The first step in web testing is browser recording, which is described inBrowser 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:

Browser Support
Browser Support
Browser Support

Include Page
Browser Support
Browser Support