# Execution Overview

{% 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.

***

## 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.

***

## In this section

| Page                                                       | What it covers                                                                                     |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [Running Tests](/execution/running-tests.md)               | Run individual test cases, suites, or plans manually or via MCP tools                              |
| [Parallel Execution](/execution/parallel-execution.md)     | Execute tests in parallel across browsers and environments for faster results                      |
| [Environments](/execution/environments.md)                 | Configure test environments with base URLs, variables, and execution parameters                    |
| [Scheduling](/execution/scheduling.md)                     | Schedule test runs on recurring intervals (hourly, daily, weekly)                                  |
| [Video & Screenshots](/execution/video-and-screenshots.md) | Review execution evidence including video recordings, screenshots, HAR logs, and Playwright traces |
| [Interactive Demo](/execution/demo.md)                     | Interactive demo of execution features                                                             |

***

## Related sections

* [Creating Test Cases](/web-testing/creating-test-cases.md) — build the test cases that the execution engine runs
* [Reporting](/reporting/reporting.md) — analyze pass rates, failure trends, and execution history after runs complete
* [Integrations](/integrations/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/)
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learning.contextqa.com/execution/execution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.