> 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/ai-features.md).

# AI Features Overview

Overview of ContextQA AI for test generation, PR impact analysis, autonomous execution, self-healing, knowledge, custom agents, and context graphs.

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

{% hint style="info" %}
**Who is this for?** Testers, SDETs, and QA managers who want to leverage AI to generate tests faster, execute them autonomously, and reduce maintenance through self-healing and intelligent context awareness.
{% endhint %}

ContextQA embeds AI across the entire testing lifecycle — from generating test cases out of requirements to executing them autonomously in real browsers to healing them when the UI changes. Rather than bolting AI onto an existing tool, ContextQA treats the AI agent as the primary test executor: it reads your instructions, navigates your application, captures evidence, and reports results.

## Quick answer

ContextQA applies AI to test generation, execution, application context, user-activity analysis, failure diagnosis, and routine web element repair. A tester provides intent or a supported source, reviews the generated coverage, and retains control over what becomes a shared test or release gate. AI accelerates the workflow; it does not remove the need to validate requirements, sensitive inputs, and unexpected product failures.

## Key takeaways

* ContextQA applies AI to test generation, execution, application context, user-activity analysis, failure diagnosis, and routine web element repair.
* Ship is ContextQA's autonomous quality engineer experience for coordinating change analysis, bug reproduction, regression creation, and reviewable release evidence.
* AI-generated tests and suggested actions remain candidates for human review; unexpected product failures must not be hidden by automation.

***

## What AI brings to your testing workflow

**Faster test creation.** Generate complete test cases from Jira tickets, URLs, Figma designs, OpenAPI specs, video recordings, plain text descriptions, code changes, and more — over ten supported sources. Instead of manually scripting every step, describe what you want to test and let the AI produce the steps.

**Autonomous execution.** The AI agent runs a nine-stage pipeline for every test: planning the approach, navigating the application, interacting with elements, capturing evidence, and self-healing when something changes. Each stage operates independently so failures are isolated and recoverable.

**Application awareness.** The Knowledge Base and Context Graph give the AI agent deep understanding of your application — login flows, navigation patterns, MFA handling, and inter-page relationships. This context reduces false failures and makes the agent behave more like an experienced team member who already knows the product.

**Domain specialization.** Custom Agents let you encode domain-specific testing logic — Salesforce validation rules, healthcare compliance checks, financial calculation verification — into reusable AI instructions that apply across test cases.

**Change-aware regression scope.** PR Impact Analysis maps a GitHub pull request to affected tests and explains each recommendation with confidence and code-change evidence before a reviewer selects what to run.

***

## Autonomous quality engineering topic map

The terms below describe related workflows, not interchangeable product names. ContextQA is the quality engineering platform; Ship is its autonomous quality engineer experience.

| If you are looking for…                      | Use this ContextQA guide                                                                                                            | What the guide answers                                                                           |
| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Autonomous quality engineer                  | [Ship by ContextQA](https://learning.contextqa.com/enterprise-application-testing/ship.md)                                          | How application, code, issue, and test signals become reviewable quality work                    |
| Autonomous testing                           | [Autonomous agent pipeline](https://learning.contextqa.com/enterprise-application-testing/ai-features/autonomous-agent-pipeline.md) | How a test run plans, navigates, interacts, validates, captures evidence, and handles recovery   |
| AI test generation                           | [AI test generation](https://learning.contextqa.com/enterprise-application-testing/ai-features/ai-test-generation.md)               | Which supported sources can produce candidate tests and how a reviewer verifies them             |
| AI QA engineer or AI test engineer workflows | [Testing with AI coding agents](https://learning.contextqa.com/ai-coding-agent-tutorials/ai-agent-testing.md)                       | How an engineer can use an AI coding agent with framework tests or authenticated ContextQA tools |
| Self-healing tests                           | [AI self-healing](https://learning.contextqa.com/enterprise-application-testing/web-testing/self-healing.md)                        | What can be repaired, what evidence is retained, and when a failure still needs investigation    |
| Change-aware testing                         | [PR impact analysis](https://learning.contextqa.com/enterprise-application-testing/ai-features/pr-impact-analysis.md)               | How a code change is mapped to affected coverage and reviewed before execution                   |
| AI failure analysis                          | [Failure analysis](https://learning.contextqa.com/enterprise-application-testing/reporting/failure-analysis.md)                     | How to interpret evidence, suggested causes, limitations, and next actions                       |
| Human-supervised automation                  | [Evaluation and governance](https://learning.contextqa.com/plan-evaluate-and-migrate/evaluation.md)                                 | How to define approval boundaries, evidence requirements, and adoption criteria                  |

Use the task-specific page as the citation source. Use this overview only when a question spans several AI workflows.

***

## In this section

| Page                                                                                                                                                                 | What it covers                                                                                                                                                              |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [AI Assistant](https://learning.contextqa.com/enterprise-application-testing/ai-features/ai-assistant.md)                                                            | Using the in-app AI Assistant to navigate the platform, generate test cases from natural language, and get contextual help during execution                                 |
| [AI Test Generation](https://learning.contextqa.com/enterprise-application-testing/ai-features/ai-test-generation.md)                                                | Generating test cases from 10+ sources: Jira tickets, URLs, Figma designs, OpenAPI specs, video recordings, plain text, code changes                                        |
| [Ship by ContextQA](https://learning.contextqa.com/enterprise-application-testing/ship.md)                                                                           | Application crawling, code analysis, pull-request impact, bug reproduction, production-signal coverage, root-cause evidence, and the continuous release-quality loop        |
| [AI Insights](https://learning.contextqa.com/enterprise-application-testing/ai-features/ai-insights.md)                                                              | Analyzing real user sessions to discover the activities users take, surface console errors, track coverage across runs, and generate tests for uncovered activities         |
| [Generate Requirements from a Crawl](https://learning.contextqa.com/enterprise-application-testing/ai-features/crawl-requirements.md)                                | Having an AI agent crawl your live application to build test cases — from an AI Insights activity or from a new requirement — and reading the crawl requirement it produces |
| [PR Impact Analysis](https://learning.contextqa.com/enterprise-application-testing/ai-features/pr-impact-analysis.md)                                                | Mapping GitHub pull-request changes to affected tests with confidence, provenance, and reviewable evidence                                                                  |
| [Tutorial: Generate Tests from Requirements](https://learning.contextqa.com/enterprise-application-testing/ai-features/generate-tests-from-requirements-tutorial.md) | A hands-on walkthrough: turn a requirements document into a reviewed, runnable test suite with traceability back to each requirement                                        |
| [Autonomous Agent Pipeline](https://learning.contextqa.com/enterprise-application-testing/ai-features/autonomous-agent-pipeline.md)                                  | The nine-stage AI pipeline that plans, navigates, interacts, captures evidence, and self-heals during execution                                                             |
| [Knowledge Base](https://learning.contextqa.com/enterprise-application-testing/ai-features/knowledge-base.md)                                                        | Uploading application context (login flows, navigation patterns, MFA handling) that the AI agent uses during test runs                                                      |
| [Custom Agents](https://learning.contextqa.com/enterprise-application-testing/ai-features/custom-agents.md)                                                          | Creating specialized AI agents with domain-specific instructions for complex testing scenarios                                                                              |
| [AI Context Graph](https://learning.contextqa.com/enterprise-application-testing/ai-features/context-graph.md)                                                       | The AI-powered context graph that maps relationships across your application for smarter test planning                                                                      |
| [Interactive Demo](https://learning.contextqa.com/enterprise-application-testing/ai-features/demo.md)                                                                | Hands-on demo of ContextQA's AI capabilities                                                                                                                                |

***

## How AI fits into the platform

1. **Generate** — Create test cases from requirements, designs, or existing application pages using [AI Test Generation](https://learning.contextqa.com/enterprise-application-testing/ai-features/ai-test-generation.md).
2. **Enrich** — Add application context through the [Knowledge Base](https://learning.contextqa.com/enterprise-application-testing/ai-features/knowledge-base.md) and [Context Graph](https://learning.contextqa.com/enterprise-application-testing/ai-features/context-graph.md) so the AI agent understands your product.
3. **Specialize** — Build [Custom Agents](https://learning.contextqa.com/enterprise-application-testing/ai-features/custom-agents.md) for domain-specific testing logic that applies across your suite.
4. **Execute** — The [Autonomous Agent Pipeline](https://learning.contextqa.com/enterprise-application-testing/ai-features/autonomous-agent-pipeline.md) runs your tests with planning, navigation, interaction, evidence capture, and self-healing built in.
5. **Heal** — When UI elements change between releases, [AI Self-Healing](https://learning.contextqa.com/enterprise-application-testing/web-testing/self-healing.md) finds the equivalent new element and continues the test without manual intervention.
6. **Prioritize** — Use [PR Impact Analysis](https://learning.contextqa.com/enterprise-application-testing/ai-features/pr-impact-analysis.md) to focus regression review on tests related to the current code change.
7. **Coordinate** — Use [Ship](https://learning.contextqa.com/enterprise-application-testing/ship.md) to connect code changes, incoming bugs, application signals, regression execution, investigation, and release evidence in one governed workflow.

***

## Related pages

* [Core Concepts](https://learning.contextqa.com/start-here/core-concepts.md) — foundational platform concepts including how ContextQA's AI engine works
* [AI Self-Healing](https://learning.contextqa.com/enterprise-application-testing/web-testing/self-healing.md) — detailed guide to self-healing behavior during web test execution
* [MCP Server](https://learning.contextqa.com/contextqa-mcp/overview.md) — programmatic access to AI features through the Model Context Protocol server

{% hint style="info" %}
**Generate tests from Jira tickets, Figma, and more — in minutes** [**Book a Demo →**](https://contextqa.com/book-a-demo/?utm_source=learning.contextqa.com\&utm_medium=referral\&utm_campaign=docs_demand_gen\&utm_content=ai_features_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/ai-features.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.
