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.
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:
- Configuring cross-browser testing; see Configuring Browser Playback Options
- Configuring user actions; see Configuring User Actions (Navigation, Delays, etc.)
- 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; End-to-End Test Scenarios
- Load testing; see Load Testing
- Penetration testing; see Penetration Testing
- Runtime error detection; see Performing Runtime Error Detection
- 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.