> 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/administration-and-reference/feature-guides.md).

# Release Readiness Feature Guides

Find practical ContextQA guides for agentic workflows, code analysis, impact-based regression, SAP upgrades, authentication, API testing, and execution evidence.

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

## Quick answer

Use the guide for the decision you need to make: reproduce a report, understand a change, build coverage, run a candidate, or approve a release. Connect the evidence across these tasks rather than evaluating each feature in isolation.

## Key takeaways

* Start with a business journey and a clear expected outcome.
* Use connected reports, code context, and execution to build the evidence.
* Preserve failures and missing coverage when making the release decision.

## Choose a practical guide

| What do you need to do?                           | Guide                                                                                                                            |
| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Onboarding and AI software factory                | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/ship/getting-started.md)                          |
| Slack / Linear / Jira / ClickUp agentic workflows | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/ship/slack-linear-to-release.md)                  |
| Bug reproduction and fix revalidation             | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/ship/ticket-driven-testing.md)                    |
| Code analysis and source-grounded coverage        | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/ship/code-analysis.md)                            |
| Crawl v2 / live activity / drafts / proposals     | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/ai-features/crawl-requirements.md)                |
| Auth profiles and session renewal                 | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/ship/auth-profiles.md)                            |
| PR/MR impact and autonomy policy                  | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/ai-features/pr-impact-analysis.md)                |
| Execution journeys and auto-fix                   | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/reporting/execution-journey-and-auto-fix.md)      |
| Healing approval and persistence                  | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/web-testing/self-healing.md)                      |
| AI agent steps and runtime controls               | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/web-testing/ai-agent-step-controls.md)            |
| API assertions and AWS Signature                  | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/api-testing/aws-signature-authentication.md)      |
| CI/CD token and release gate                      | [Open the guide](https://learning.contextqa.com/integrations-and-developer-tools/integrations/ci-cd-release-gates.md)            |
| Tunnels / machine routes / browser health         | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/execution/tunnels-and-private-apps.md)            |
| Environment data and variable scope               | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/web-testing/environment-data-management.md)       |
| Billing usage and AWS Marketplace                 | [Open the guide](https://learning.contextqa.com/administration-and-reference/administration/billing-and-usage.md)                |
| API load testing                                  | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/api-testing/load-testing.md)                      |
| Mobile builds and execution                       | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/mobile-testing/mobile-test-plans.md)              |
| Plan capacity / recovery / stopped runs           | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/execution/parallel-execution.md)                  |
| Search / module / permissions / exports           | [Open the guide](https://learning.contextqa.com/enterprise-application-testing/web-testing/finding-and-organizing-test-cases.md) |
| MCP orchestration and data integrity              | [Open the guide](https://learning.contextqa.com/contextqa-mcp/overview/agent-integration-guide.md)                               |
| SAP business processes and quarterly upgrades     | [Open the guide](https://learning.contextqa.com/packaged-application-testing/sap-testing.md)                                     |

## Which workflow should I try first?

For an engineering leadership evaluation, follow [Slack or Linear to release readiness](https://learning.contextqa.com/enterprise-application-testing/ship/slack-linear-to-release.md). Use one known bug, one candidate fix, and a small critical-journey suite. Verify the original failure, patch, deployed build, selected tests, and final results before broadening automation.

For a vendor-driven upgrade, start with [quarterly release testing](https://learning.contextqa.com/enterprise-application-testing/ship/quarterly-release-testing.md). Repository change analysis complements vendor release notes, configuration review, and business-process regression; it does not replace them.


---

# 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/administration-and-reference/feature-guides.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.
