---
title: "Record the starting conditions for a QA journey | Proofline Help"
description: "Some journeys require application state, such as an outstanding invitation. A fresh browser does not reset the data behind your site."
url: https://proofline.sh/help/qa-journey-preconditions/
---

[Help center](/help/)

# Record the starting conditions for a QA journey

Some journeys require application state, such as an outstanding invitation. A fresh browser does not reset the data behind your site.

[![The Storefront setup editor lists three journeys, their sources and the filing destination.](/help-images/qa-edit-journeys-light.png)](/help-images/qa-edit-journeys-light.png)

Expand a journey to edit the action and its expected outcome. Fictional demo workspace.

## Tell the run what must already be true

Open the journey in the setup editor and add its preconditions. Describe the required starting state separately from the action and expected result. Save the setup.

When a run reports a blocked journey, compare its reason with the saved preconditions. Restore the starting state in your test application before running again. The run does not create missing state solely to satisfy a precondition.

## Related guides

-   [How Agentic QA works](/help/agentic-qa/)
