What ContextQA is
ContextQA is an AI-driven test automation platform. Instead of hand-writing and maintaining brittle scripts, you build a test case as a sequence of plain-language steps, and ContextQA runs it in a real browser. AI helps locate elements and adapt as your application changes, which is what keeps tests working across releases. It covers web UI flows and API test cases, with reusable test data and multiple environments.
The building blocks
Test cases & the steps editor — a test case is an ordered list of steps (for example, "Enter [email protected] in the Email field"). Each step's data value has a test-data type, and a right-side Configuration panel controls waits, retries, browser/viewport, AI behaviour, and execution settings.
Environments & data — under Environment & Data in the left sidebar, Environments hold values that change per target (base URLs, credentials), and Data Profiles hold data sets for running the same flow once per row of data.
Runs & results — you run a test (choosing the execution environment in the run confirmation dialog) and review what passed or failed.
Access & roles — what each person can see and do is controlled by a per-user Admin toggle plus custom roles your workspace defines.
A typical first flow
Create a test case and add the steps for the flow you want to check.
Replace any value that differs per target (a URL, a login) with an Environment value rather than typing it inline — this is what lets one test run against Staging and Production.
Open the Configuration panel to set the browser/viewport and, if a step is slow, the waits and retries.
Run the test, pick the environment in the confirmation dialog, and review the result.
Finding your way around
Most of what you need lives in the left sidebar: your test cases, Environment & Data (Environments and Data Profiles), and run results. Workspace-level settings — including users and roles — are under Settings. Each organisation has its own subdomain, for example yourcompany.contextqa.com.
Where to go next
To keep tests reliable when you switch environments, see our article on keeping tests stable across environments.
For the four test-data types and how environments work, see our article on test data and environments.
For waits, retries, browser settings, and data-driven runs, see our article on test case settings and the steps editor.
If an option seems to be missing, it's usually your role or plan — see our article on roles, permissions, and login.
Getting help
If something looks broken rather than confusing, tell support it's a bug report and include your workspace URL and a screenshot so it routes to the right queue.