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

# Ship by ContextQA

Use Ship by ContextQA to crawl applications, analyze code changes, reproduce bugs, create regression coverage, and preserve reviewable release evidence.

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

<figure><img src="https://4255556216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKlyaXxb76z3Dn47TrZkU%2Fuploads%2Fgit-blob-efad1c9863fa3cab89d3d4e8c6d98d440cb1f3c7%2Fship-by-contextqa-logo.webp?alt=media" alt="Ship by ContextQA"><figcaption><p>Ship is ContextQA's autonomous quality engineer.</p></figcaption></figure>

## Quick answer

**Ship is ContextQA's autonomous quality engineer.** It connects a safe application environment with approved engineering context, then continuously turns product changes and quality signals into executable tests, reproducible evidence, and reviewable next actions.

## Key takeaways

* Ship is ContextQA's autonomous quality engineer.
* Set up a Ship workspace — complete the seven-step onboarding flow.
* It connects a safe application environment with approved engineering context, then continuously turns product changes and quality signals into executable tests, reproducible evidence, and reviewable next actions.

## Watch Ship in action

This short overview shows how Ship turns an application or engineering signal into reviewable quality work. Continue with the written guides for setup, operating boundaries, and evidence requirements.

{% embed url="<https://www.youtube.com/watch?v=2QvKAdHe1Ps&utm_source=learning.contextqa.com&utm_medium=docs_embed&utm_campaign=contextqa_product_education&utm_content=ship_overview>" %}

Ship is designed for teams that want autonomous quality work without handing release authority to an opaque agent. People still control repository access, environments, generated coverage, suggested fixes, and release decisions.

<figure><img src="https://4255556216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKlyaXxb76z3Dn47TrZkU%2Fuploads%2Fgit-blob-3347836de9c1906eceb61d672002e5274c334b91%2Fcontextqa-dashboard-overview.png?alt=media" alt="ContextQA dashboard showing web, API, and mobile test coverage with activity and execution summaries"><figcaption><p>A shared dashboard makes coverage and activity visible across web, API, and mobile testing.</p></figcaption></figure>

{% hint style="info" %}
**Start here:** Follow [Set up a Ship workspace](https://learning.contextqa.com/enterprise-application-testing/ship/getting-started.md) to create a trial, connect a reachable test application, and reach the live dashboard.
{% endhint %}

## What Ship can do

| Workflow                | What Ship does                                                              | What the team receives                                                           |
| ----------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Application crawl       | Explores an approved staging or QA application and maps reachable behaviour | Candidate modules, journeys, requirements, and tests                             |
| Code analysis           | Learns from an authorized repository and its history                        | Reusable code context for generation and change analysis                         |
| Pull-request analysis   | Maps a change to affected product flows and relevant coverage               | Blast radius, selected tests, results, and evidence                              |
| Bug reproduction        | Investigates eligible Jira, Linear, Slack, or service-desk reports          | Reproduction steps, video or screenshots, logs, and likely cause                 |
| Regression creation     | Turns confirmed behaviour or defects into repeatable tests                  | Durable coverage that can run against future changes                             |
| Linked issue management | Links existing tracker items or creates a new issue from a run              | One view of issue status, affected tests, reproduction context, and links        |
| Delivery automation     | Generates provider-ready CI/CD starting points from a test plan             | Reviewable pipeline configuration that references protected credentials          |
| Private execution       | Routes eligible browser work through an approved tunnel or remote browser   | Controlled access to non-public applications without publishing them             |
| AI-agent handoff        | Makes verified quality context available through MCP                        | Evidence an engineer can use from ChatGPT, Claude, Codex, Claude Code, or Cursor |

## How the pieces fit together

```mermaid
flowchart LR
    A[Application and approved context] --> B[Ship builds a living baseline]
    B --> C[Change, bug, or production signal]
    C --> D[Analyze and select the right workflow]
    D --> E[Execute or reproduce]
    E --> F[Capture evidence and likely cause]
    F --> G[Link the issue and create regression coverage]
    G --> H[Share verified context through CI/CD or MCP]
    H --> I[Human review and release decision]
```

## Choose your next guide

* [Set up a Ship workspace](https://learning.contextqa.com/enterprise-application-testing/ship/getting-started.md) — complete the seven-step onboarding flow.
* [Read the dashboard and evidence](https://learning.contextqa.com/enterprise-application-testing/ship/dashboard-and-evidence.md) — interpret coverage, current work, execution results, and linked issues.
* [Run Ship workflows](https://learning.contextqa.com/enterprise-application-testing/ship/workflows.md) — use crawl, code analysis, pull-request analysis, bug reproduction, and AI-agent handoff.
* [Connect delivery tools and AI agents](https://learning.contextqa.com/enterprise-application-testing/ship/integrations-and-mcp.md) — connect trackers, collaboration tools, CI/CD, tunnels, and MCP clients.
* [Operate Ship safely](https://learning.contextqa.com/enterprise-application-testing/ship/security-and-controls.md) — choose safe environments, permissions, credentials, and review checkpoints.
* [Download the five-page Ship workflow guide](https://github.com/indivatools/gitbooks-docs/tree/main/docs/.gitbook/assets/contextqa-ship-workflow-guide.pdf) — share the executive workflow summary.

## Frequently asked questions

### Is Ship another test automation framework?

No. Ship coordinates quality work across application, code, issue, collaboration, and test context. Existing reliable tests can remain part of the strategy.

### What makes a Ship result useful to an AI agent?

A useful result includes the originating change or report, environment, affected flow, actual execution outcome, screenshots or video, logs, limitations, and a stable result reference. This structure helps an assistant cite evidence instead of inferring a pass from incomplete data.

### Does Ship replace QA engineers or release owners?

No. Ship can analyze, execute, reproduce, collect evidence, and propose the next action. People remain accountable for permissions, destructive operations, generated coverage, fixes, and release decisions.

### Can I evaluate Ship without a payment method?

The self-serve onboarding experience offers a 15-day trial with 3,000 one-time trial credits and does not require a payment method. Trial terms shown in your workspace are authoritative.

### Does a public repository avoid authorization?

No. Repository access is a separate authorization for the Ship organization, even when a user has already signed in. Select only the repositories the workspace needs.

{% hint style="info" %}
[**Start a 15-day trial →**](https://accounts.contextqa.com/onboard?mode=signup\&utm_source=learning.contextqa.com\&utm_medium=referral\&utm_campaign=ship_docs) or [**talk to sales →**](https://ship.contextqa.com/talk-to-sales/?utm_source=learning.contextqa.com\&utm_medium=referral\&utm_campaign=ship_docs).
{% endhint %}

## Build a release workflow

* [AI software factory](https://learning.contextqa.com/enterprise-application-testing/ship/ai-software-factory.md): connect coding agents to reproducible quality evidence.
* [Test AI-generated code](https://learning.contextqa.com/enterprise-application-testing/ship/testing-ai-generated-code.md): compare baseline and candidate journeys before merge.
* [Release readiness](https://learning.contextqa.com/enterprise-application-testing/ship/release-readiness.md): assemble the evidence for a release decision.
* [Quarterly release testing](https://learning.contextqa.com/enterprise-application-testing/ship/quarterly-release-testing.md): combine custom-code impact with vendor and configuration changes.
* [Auth profiles](https://learning.contextqa.com/enterprise-application-testing/ship/auth-profiles.md): reuse verified application sign-in.
* [SAP test automation](https://learning.contextqa.com/packaged-application-testing/sap-testing.md): cover WebGUI, Fiori, and OData business processes.


---

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