Web Testing Overview

Complete guide to creating, managing, and executing web application tests in ContextQA — from recording your first test to running full regression suites.

Who is this for? Testers and SDETs who want to automate web application testing using natural language — no Selenium or Playwright expertise required.

ContextQA's web testing capabilities let you build automated tests for any web application in natural language — no code required. The AI agent navigates real browsers, interacts with your UI, and verifies results exactly as a human QA engineer would.

Quick answer

ContextQA web testing converts a plain-English workflow, recorded browser session, or imported requirement into a reviewable automated test. The saved test runs in a real browser, collects step-level and execution-level evidence, and can be reused in suites, test plans, schedules, and CI/CD quality gates. Self-healing addresses routine element-location drift while genuine application failures remain visible for investigation.

---

How Web Testing Works

1. Describe the test — Write what you want to test in plain English, including the steps to perform and what to verify.
2. ContextQA creates the steps — The AI parses your description into structured, executable steps.
3. Execution runs in a real browser — The AI agent navigates Chrome, Firefox, Safari, or Edge with actual browser rendering and JavaScript execution.
4. Evidence is collected automatically — Screenshots, video, network HAR, and console logs are captured for every run.
5. AI self-healing keeps tests green — If a UI element changes, the agent automatically finds the equivalent new element and continues.

---

Supported Browsers

Browser	Versions	Notes
Chrome	Latest + 2 previous	Default; best performance
Firefox	Latest + 2 previous
Safari	Latest	macOS/iOS only
Edge	Latest	Chromium-based

Browser selection is configured in the Test Plan or per individual execution run.

---

What You Can Test

• Single-page applications (React, Angular, Vue, Svelte) — full JavaScript execution and dynamic routing
• Traditional server-rendered sites — page loads, form submissions, redirects
• Authentication flows — login, logout, SSO/SAML redirect handling, MFA (with Knowledge Base entries)
• Multi-step workflows — checkout flows, onboarding wizards, multi-page forms
• Data entry and validation — form field inputs, error messages, required field enforcement
• Navigation and routing — breadcrumbs, back button behavior, deep link handling
• API-backed UI — the network monitor captures all XHR/fetch requests, so API failures surface in test results
• PDF and file download — verify that downloads trigger and files have expected content
• File uploads — test file input fields with actual files
• Responsive layouts — set the viewport size per run to test desktop, tablet, and mobile breakpoints

---

In This Section

Creating and editing tests

Page	What you'll learn
Creating Test Cases	How to write effective test descriptions; AI-powered test generation from tickets and requirements
Test Steps Editor	Manual step editing; conditional logic (If / Else If / Else), loops, API calls, and step groups
Debugging Test Cases	Debug interactively with breakpoints, live variable inspection, and step-by-step execution

Requirements-driven testing

Page	What you'll learn
Requirements Management	Upload requirement documents and let AI generate test cases, analyze coverage gaps, and track change history
Requirements Library	Review AI-generated test cases, analyze coverage gaps, and manage your requirements library
Uploaded Test Files	View and manage imported requirement files, review AI analysis, and inspect file metadata
Imported Files	View test cases generated from imported files, review AI results, and track import history

Advanced step types

Page	What you'll learn
Database Steps	Run SQL queries during tests and verify backend data with assertions
Custom Code Steps	Execute custom JavaScript for complex logic, calculations, and DOM interactions
Document Generation Steps	Generate TXT and CSV files dynamically for file upload and import testing

Test data and variables

Page	What you'll learn
Test Data Management	Data-driven testing with parameterized profiles; local and global variables
Environment Data Management	Manage environments, variables, database connections, and data profiles from one workspace
Importing and Exporting Data	Export and import environments, data profiles, and variables using JSON or Excel

Suites, plans, and versioning

Page	What you'll learn
Managing Test Suites	Grouping test cases; building regression and smoke suites
Test Plans	Creating execution plans; scheduling, CI/CD integration, parallel execution, and recovery settings
Version History	Track, compare, and restore previous versions of your test cases

AI self-healing

Page	What you'll learn
AI Self-Healing	How self-healing works; reviewing and approving healing suggestions
AI Self-Healing (Interactive Demo)	See self-healing detect a broken locator and repair a step automatically

Tutorials

Page	What you'll learn
Tutorial: Data-Driven Testing	Build a parameterized login test that runs with multiple user roles from one data profile
Tutorial: Step Groups	Build a reusable login step group, insert it into multiple test cases, and update it once

---

Quick Start: Your First Web Test

If you want to jump straight in:

1. Go to Test Cases in the left navigation.
2. Click + New Test Case.
3. Choose Start with AI Assistance.
4. Enter your application URL and a plain-English description:

   Navigate to https://demo.myapp.com/login
   Enter [e-mail] in the email field
   Enter the password Admin123!
   Click the Login button
   Verify the page heading reads "Welcome back"

5. Click Generate Test Case.
6. Watch the AI run, capture screenshots, and build the structured steps.
7. Click Run to execute the saved test case.

The test is now saved and can be added to a suite and scheduled.

---

Tips for Effective Web Tests

• Be specific about what to verify — "verify the order confirmation number appears" is better than "verify the page loads".
• Use your Knowledge Base — if your app has cookie banners, chat widgets, or feature tours, add Knowledge Base entries to dismiss them automatically before they interfere with tests.
• Keep tests atomic — one test case per user scenario. This makes failures easier to diagnose.
• Use step groups for shared setup — if 20 test cases all start with "log in as admin", create a Login step group and reuse it.
• Set realistic environments — always use an Environment record instead of hardcoding URLs in steps, so the same tests can run against staging and production.

---

Related Pages

• Tutorial: Data-Driven Testing
• Core Concepts
• Execution & Scheduling
• AI Features Overview
• MCP Server

Frequently asked questions

Can ContextQA automate a web application without Selenium or Playwright code?

Yes. The standard workflow uses natural-language steps, AI assistance, browser recording, or imported requirements. ContextQA handles browser interaction and evidence capture. Custom JavaScript and Playwright export remain available for teams that need code-level extensions.

What is the difference between a test case, test suite, and test plan?

A test case represents one user scenario. A test suite groups related cases, such as smoke or checkout coverage. A test plan determines which suites run, along with the browser or device, environment, parallelism, notifications, and schedule.

Does self-healing hide application bugs?

Self-healing is intended for routine element-location drift, such as an equivalent button moving in the DOM. It does not make a failed business assertion pass, replace a removed workflow, or correct a server-side error. See AI Self-Healing for triggers and limits.

Can the same web test run against staging and production?

Yes. Store deployment-specific URLs and values in environments instead of hardcoding them in the test. Select the intended environment when you configure or execute the plan.

Can web tests run in CI/CD?

Yes. Put the cases in a suite and plan, validate the plan in the portal, and connect it to an approved CI/CD or MCP workflow. See Integrations and Prepare a CI/CD quality gate.

70% less manual test maintenance with AI self-healing Book a Demo →