> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/workflow/test-and-troubleshoot/test-steps-and-complete-workflows.md).

# Test steps and complete workflows

In this section you will learn about Test & Debug

Test individual steps to diagnose their inputs and outputs, then test the complete workflow and its real trigger.

## Prepare test inputs

Choose a fictional record and record its original state. For a `ticket_id` workflow, prepare a valid ID, a missing ID, and a record that should take another branch.

Set test parameters on the trigger step. Match their types to the values the real caller will supply.

## Test a step or the whole workflow

The editor provides controls for testing individual steps and the complete workflow.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2Fv0cRyhh1orrhB96gHgSJ%2Fdhtrg.png?alt=media\&token=72712b41-9297-4c6d-a158-6023b2408acc)

1. Run the first step with your test input.
2. Inspect its output.
3. Configure and test the dependent step.
4. Run the complete workflow.
5. Inspect the resulting record or external action.

Testing can execute writes and notifications. Use test records and destinations you control; do not assume the test control simulates effects.

## Inspect an error

A failing step is highlighted. Select it and open the **test** tab to read the error.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FAdP4lS4eFZKbU7rmohjn%2Fzrshxdct.png?alt=media\&token=5e7705db-a5d6-41d6-8150-c3aabbbaeb91)

Check the received value, expected type, record identifier, and operation access. Inspect earlier effects before repeating a run.

## Test the actual trigger

A successful editor test does not prove that a button binds the right input, a schedule is enabled, or a webhook sender uses the expected payload.

Run the actual entry point with fictional data. Compare the input and final outcome with the editor test.

## Minimum test matrix

| Case                     | What to verify                                            |
| ------------------------ | --------------------------------------------------------- |
| Normal input             | The intended record changes                               |
| Other branch             | The alternate path produces its expected result           |
| Empty lookup or list     | No unrelated records change                               |
| Missing or invalid input | The process stops or follows the intended fallback        |
| Controlled failure       | The error is understandable and earlier effects are known |
| Repeated input           | Repeat behavior matches the design                        |

For background work, check the trigger's available execution details and the final data. Do not assume the editor test panel is a persistent run-history feature.

See [Troubleshoot common problems](/workflow/test-and-troubleshoot/troubleshoot-common-problems.md).


---

# 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.jetadmin.io/workflow/test-and-troubleshoot/test-steps-and-complete-workflows.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.