Build tests · 9 min read

Tools and browsers

Choose the coverage profile and browser that fit the risk you want to test.

Tools and browsers do different jobs

The tool you select shapes the test language, coverage, acceptance criteria, and checks QATesty prepares. The browser selection controls the real browser engine used for the run. QATesty keeps both choices visible with the run result so reviewers know what was tested.

Available test profiles

Playwright

End-to-end and regression journeys

Cypress

Frontend-focused user flows

Selenium

Portable browser automation coverage

Lighthouse

Accessibility and performance checks

JMeter

Load and response behavior

k6

Performance budgets and traffic scenarios

OWASP ZAP

Automated web security checks

Burp Suite

Security-focused validation planning

Available browser engines

Choose Chromium for the broadest everyday baseline, Firefox when your audience uses Mozilla's engine, and WebKit to cover Safari-like browser behavior. Browser binaries must be installed by the workspace administrator before a run can use them.

  • Chromium: a strong default for most first runs.
  • Firefox: useful for engine-specific layout and interaction differences.
  • WebKit: useful for Safari-oriented compatibility checks.

Make a good first choice

  1. 1

    Start from the release risk

    Choose the customer journey, security concern, or performance target you need to prove.

  2. 2

    Select one matching profile

    Use Playwright for a first end-to-end journey; add specialist profiles when their checks answer a real question.

  3. 3

    Run a browser baseline

    Begin with Chromium, then repeat important journeys in Firefox and WebKit when cross-browser support matters.

  4. 4

    Compare like with like

    When reviewing history, compare runs that used the same scenario, environment, tool profile, and browser.