> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/e2e-flow-end-to-end-flow.md).

# E2E Flow (End-to-End Flow)

An end-to-end (E2E) flow is a test automation feature that combines multiple individual test cases into a single, ordered sequence that mirrors a complete business scenario or user journey. Rather than validating each test case as a standalone unit, an E2E flow chains them together so they execute in a defined order, with the outcome of one test case feeding into the next.

For example, a business scenario might include creating a record, updating the record, and verifying the resulting status. An E2E flow lets you combine these test cases into one continuous flow that reflects how a real user would move through the application, rather than treating each step as an isolated, disconnected test.

### Why is an E2E flow required?

Most real-world business processes involve multiple steps across different screens, modules, or systems. Testing these steps individually confirms that each part works on its own, but it doesn't confirm that the parts work correctly together, in sequence, the way an actual user would experience them.

An E2E Flow fills this gap. An E2E flow helps you test an entire business process from start to finish, just as a user would perform it. It ensures that all the steps work together correctly. For example, data entered in one step is correctly used in the next step. This helps you identify issues that may not be detected when testing each step separately.

### Benefits of using E2E flows

* Accurate validation: Tests the application the way a user actually experiences it, across multiple screens or modules, instead of in isolated fragments.
* Verify interactions between test cases: Identify issues that might occur when multiple functions or processes work together.
* Reduced test maintenance: Since E2E flows are built from existing test cases, updates to a shared test case can automatically apply across every E2E flow that uses it.
* Better coverage of business-critical scenarios: Helps ensure that key user journeys are covered, in addition to individual features being consistently tested.


---

# 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://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/e2e-flow-end-to-end-flow.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.
