> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testyourappnow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Acceptance Testing: Independently Verify Software Delivery

> Turn written requirements into repeatable acceptance flows and independently verify that your development team delivered working software.

Your development team says the feature is done. Now you need to verify it actually works before you sign off. TYAN lets you translate plain-English requirements directly into repeatable acceptance flows, so you can independently confirm that the delivered build matches the spec — no manual clicking, no ambiguity.

## The Acceptance Testing Workflow

<Steps>
  <Step title="Write the Requirement in Plain English">
    Start with the requirement exactly as it was written or agreed upon. Clarity here prevents misaligned tests later. For example:

    > "Users can reset their password via email."

    If the requirement has multiple clauses or edge cases, break each one into its own acceptance flow. One requirement clause, one flow — this keeps failures easy to trace back to a specific deliverable.
  </Step>

  <Step title="Translate Each Clause into Flow Steps">
    Open TYAN, create a new flow, and map each part of the requirement to a concrete step. For the password reset example:

    | Requirement Clause                             | Flow Step                                        |
    | ---------------------------------------------- | ------------------------------------------------ |
    | User navigates to the forgot-password page     | **Navigate** to `/forgot-password`               |
    | User enters their email address                | **Fill** email field with a test email address   |
    | User requests a reset link                     | **Click** "Send reset link" button               |
    | User sees confirmation that the email was sent | **Assert** "Check your email" message is visible |

    Name the flow after the requirement (e.g., `[ACC] Password Reset via Email`) so it's immediately identifiable in your flow library.
  </Step>

  <Step title="Run the Acceptance Flow Against the Delivered Build">
    Point the flow at the delivered build's URL — this could be a staging environment or your production URL, depending on your release process. Click **Run** from the flow detail page.

    TYAN executes every step and assertion in sequence. You'll see a pass or fail result for each step within seconds.
  </Step>

  <Step title="Accept or Return the Feature">
    * **Pass** — every step and assertion succeeded. The feature meets the requirement. Accept it and proceed to the next item.
    * **Fail** — one or more steps failed. TYAN captures a screenshot at the exact point of failure. Share the failure screenshot and the run log with your dev team as concrete evidence of what's broken and where. No he-said-she-said, no ambiguous bug reports.

    Once the team ships a fix, re-run the acceptance flow to confirm the issue is resolved before you sign off again.
  </Step>
</Steps>

## Sharing Results with Stakeholders

After a run completes, open the run detail page and click **Share Report**. TYAN generates a read-only link you can send to stakeholders, clients, or product managers — no account required to view it. The report shows each step, its pass/fail status, and screenshots, giving non-technical reviewers a clear picture of what was verified.

## Promoting to a Production Monitor

Once a feature is accepted, don't discard the flow. Open it and click **Promote to Monitor** to schedule it as a recurring check against production. The acceptance flow that verified the feature on delivery becomes the regression test that protects it going forward.

<Tip>
  Build a dedicated folder in your flow library for acceptance flows, organized by feature or sprint. Over time, this library becomes your full regression suite — every accepted feature is already tested, already proven to work, and ready to re-run the moment something changes.
</Tip>

<CardGroup cols={2}>
  <Card title="Acceptance Tests Concept" icon="circle-check" href="/concepts/acceptance-tests">
    Learn how acceptance tests differ from monitors and how to organize them by requirement or sprint.
  </Card>

  <Card title="Flows Concept" icon="route" href="/concepts/flows">
    Understand the building blocks of a flow — navigate, interact, and assert steps — and how to compose them.
  </Card>
</CardGroup>