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

# Enterprise Application Learning Path

Follow an enterprise application testing path from web, mobile, and API setup to reusable regression suites and release evidence.

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

## Quick answer

Use enterprise application testing for the web, mobile, and API applications your team builds and maintains. Start with one business journey, create and run a test, inspect its evidence, then organize reusable regression coverage. For Salesforce, Oracle, SAP, or Workday, start in the separate packaged application section.

## Key takeaways

* Choose web, mobile, or API by the interface you need to exercise.
* Complete one verified journey before expanding the suite.
* Use the shared execution, reporting, and integration modules as your coverage grows.

## Choose an interface

| Module              | Start here                                                                                          | First outcome                                               |
| ------------------- | --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| Web applications    | [Record your first browser test](/enterprise-application-testing/web-testing/recording-tutorial.md) | One business journey with assertions and execution evidence |
| Mobile applications | [Your first mobile test](/enterprise-application-testing/mobile-testing/mobile-testing-tutorial.md) | One app journey on the selected device configuration        |
| APIs and services   | [Your first API test](/enterprise-application-testing/api-testing/api-testing-tutorial.md)          | A request with response assertions                          |

For a vendor application, choose [packaged application testing](/packaged-application-testing/packaged-app-testing.md). For a chatbot or voice agent, choose [AI agent testing](/ai-agent-testing/agent-evaluation.md).

## Module 1 — Prepare and run a first test

Complete [workspace onboarding](/start-here/self-serve-onboarding.md), identify a test environment and account, then follow the interface tutorial above. Define a concrete expected result before generating or recording steps. Review the resulting test before execution.

**Checkpoint:** you can identify the target environment, test inputs, assertion, and run result for one journey. If a test fails, use [failure debugging](/enterprise-application-testing/reporting/debugging-failing-tests.md) before adding more cases.

## Module 2 — Make the journey reusable

Use [test data](/enterprise-application-testing/web-testing/test-data-management.md) for input variations and [environment data](/enterprise-application-testing/web-testing/environment-data-management.md) for environment-specific values. Extract repeated operations into [step groups](/enterprise-application-testing/web-testing/step-groups-tutorial.md). Organize related cases into [suites](/enterprise-application-testing/web-testing/managing-test-suites.md).

**Checkpoint:** the same logical journey can run with a second approved data set without editing every step. Verify that repeated or parallel runs do not collide on shared records.

## Module 3 — Connect interfaces and review failures

When a workflow crosses services and screens, use [API chaining](/enterprise-application-testing/api-testing/api-chaining.md) and the relevant browser assertions to verify the same business record. Review [test results](/enterprise-application-testing/reporting/test-results.md), available [video and screenshots](/enterprise-application-testing/execution/video-and-screenshots.md), and [failure analysis](/enterprise-application-testing/reporting/failure-analysis.md).

**Checkpoint:** a passing click sequence is supported by the required business state, and failures have enough evidence for investigation.

## Module 4 — Build the release workflow

Create a [regression suite](/enterprise-application-testing/execution/regression-suite-tutorial.md), configure [environments](/enterprise-application-testing/execution/environments.md), and prepare a [CI/CD quality gate](/start-here/ci-cd-tutorial.md). Use [Ship](/enterprise-application-testing/ship.md) for the documented autonomous quality workflows and [release readiness](/enterprise-application-testing/ship/release-readiness.md) for a reviewable decision.

**Checkpoint:** the release reviewer can see what ran, against which build and environment, what failed, and what was excluded.

## Watch, try, and verify

Watch the [web-test walkthrough](https://www.youtube.com/watch?v=be4DUh8T1ag\&utm_source=learning.contextqa.com\&utm_medium=docs_referral\&utm_campaign=contextqa_product_education\&utm_content=enterprise_web_path), then complete the [browser recording tutorial](/enterprise-application-testing/web-testing/recording-tutorial.md). Explore the [execution demo](/enterprise-application-testing/execution/demo.md) and compare its evidence with your own first run.

The [walkthrough library](/walkthroughs-demos-and-examples/learn.md) pairs videos and demos with written exercises. Continue into the Web, Mobile, API, Execution, and Reporting modules in this section for detailed reference.


---

# 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/enterprise-testing.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.