> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/enterprise-application-testing/execution.md).

# Execution Overview

Run, schedule, and monitor test executions across browsers and environments — with parallel runs, video evidence, and full execution traceability.

> **Documentation owner:** [Deep Barot](https://contextqa.com/academy/) · **Last updated:** October 22, 2026

{% hint style="info" %}
**Who is this for?** Testers, SDETs, and QA managers who need to run tests reliably across environments, scale execution with parallelism, and review detailed evidence for every run.
{% endhint %}

ContextQA's execution engine handles everything from a single ad-hoc test run to scheduled parallel suites across multiple browsers and environments. Every execution captures video recordings, screenshots, HAR logs, and Playwright traces so you always have the evidence you need to diagnose failures and prove coverage.

## Quick answer

ContextQA can execute an individual case or a plan-based collection of suites immediately, on a schedule, through an approved CI/CD workflow, or through authenticated MCP tools. The selected plan controls its suites and execution settings, while the resulting run exposes status and available evidence for review. Validate a plan interactively before making it a release gate.

## Key takeaways

* ContextQA can execute an individual case or a plan-based collection of suites immediately, on a schedule, through an approved CI/CD workflow, or through authenticated MCP tools.
* Select what to run — Pick an individual test case, a test suite, or an entire test plan.
* Parallel execution — Run multiple test cases simultaneously across browsers and environments to cut total execution time.

***

## How execution works

1. **Select what to run** — Pick an individual test case, a test suite, or an entire test plan.
2. **Choose the environment** — Select a preconfigured environment that defines the base URL, variables, and browser settings.
3. **Execute** — Run immediately, schedule for later, or trigger from a CI/CD pipeline or MCP tool.
4. **Monitor in real time** — Watch execution progress on the Execution Dashboard as results stream in.
5. **Review evidence** — Every run produces video, screenshots, network logs, and trace files for step-level debugging.

***

## Key capabilities

* **Parallel execution** — Run multiple test cases simultaneously across browsers and environments to cut total execution time.
* **Environment management** — Define named environments with base URLs, global variables, and execution parameters so the same tests work against dev, staging, and production.
* **Scheduling** — Set up recurring runs on hourly, daily, or weekly intervals without any external scheduler.
* **Execution evidence** — Video recordings, step-level screenshots, HAR network logs, and downloadable Playwright traces are captured automatically for every run.
* **CI/CD and MCP integration** — Trigger runs from GitHub Actions, Jenkins, GitLab CI, or directly from an AI coding agent through the ContextQA MCP Server.
* **Private-network and remote-grid execution** — Reuse organization proxy and remote-browser profiles from a test case or plan.

***

## In this section

| Page                                                                                                                                            | What it covers                                                                                     |
| ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [Running Tests](https://learning.contextqa.com/enterprise-application-testing/execution/running-tests.md)                                       | Run individual test cases, suites, or plans manually or via MCP tools                              |
| [Parallel Execution](https://learning.contextqa.com/enterprise-application-testing/execution/parallel-execution.md)                             | Execute tests in parallel across browsers and environments for faster results                      |
| [Environments](https://learning.contextqa.com/enterprise-application-testing/execution/environments.md)                                         | Configure test environments with base URLs, variables, and execution parameters                    |
| [Proxy & Remote Browser Profiles](https://learning.contextqa.com/enterprise-application-testing/execution/proxy-and-remote-browser-profiles.md) | Route a case or plan through a saved proxy or remote WebSocket browser endpoint                    |
| [Scheduling](https://learning.contextqa.com/enterprise-application-testing/execution/scheduling.md)                                             | Schedule test runs on recurring intervals (hourly, daily, weekly)                                  |
| [Video & Screenshots](https://learning.contextqa.com/enterprise-application-testing/execution/video-and-screenshots.md)                         | Review execution evidence including video recordings, screenshots, HAR logs, and Playwright traces |
| [Interactive Demo](https://learning.contextqa.com/enterprise-application-testing/execution/demo.md)                                             | Interactive demo of execution features                                                             |

***

## Related sections

* [Creating Test Cases](https://learning.contextqa.com/enterprise-application-testing/web-testing/creating-test-cases.md) — build the test cases that the execution engine runs
* [Reporting](https://learning.contextqa.com/enterprise-application-testing/reporting.md) — analyze pass rates, failure trends, and execution history after runs complete
* [Integrations](https://learning.contextqa.com/integrations-and-developer-tools/integrations.md) — trigger executions from CI/CD pipelines and push results to Jira or Azure DevOps

{% hint style="info" %}
**Cut execution time with parallel cross-browser runs** [**Book a Demo →**](https://contextqa.com/book-a-demo/?utm_source=learning.contextqa.com\&utm_medium=referral\&utm_campaign=docs_demand_gen\&utm_content=execution_overview)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learning.contextqa.com/enterprise-application-testing/execution.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
