> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/oe-user-guides/value-streams/working-with-value-streams/testing-value-stream.md).

# Testing a Value Stream

Test out the value stream before publishing.

When you create or edit a value stream, you have two possibilities as the next actions: test or publish.

* **Test** - allows you to test the draft version of the process, which means all the triggers and steps that you constructed in the value stream can be checked before you publish them
* **Publish** - creates a production version of the value stream

To test the value stream before publishing, choose the **Test** button.

<figure><img src="https://2734760799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8dAaH7DfB59pzZwLxmur%2Fuploads%2Fgit-blob-98a36d5c508c2a1acae8a6c8e02e59859f33150f%2Fdp_test_vs.png?alt=media" alt="" width="553"><figcaption></figcaption></figure>

You can test the value stream in two ways:

* Copy the curl request sample - you can use it for sending a request and checking if it starts the process (for instance in Postman)

  <figure><img src="https://2734760799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8dAaH7DfB59pzZwLxmur%2Fuploads%2Fgit-blob-4a8fef229b8393e9e981a5d2b114b1af9602dd88%2Fdp_test_curl_vs.png?alt=media" alt=""><figcaption></figcaption></figure>
* Test directly in the UI - when the process is not published yet, you can test it directly from the UI, using the exiting payload example or adding your own. If it's successful, you get the notification in the same window.

  <figure><img src="https://2734760799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8dAaH7DfB59pzZwLxmur%2Fuploads%2Fgit-blob-4f0bccb77cfd9e5cf84419d427dbd1cee31ef698%2Fdp_test_ui_vs.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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://developer.emporix.io/oe-user-guides/value-streams/working-with-value-streams/testing-value-stream.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.
