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

# Generate test cases

*Give QA a ready list of what to test, straight from your designs.*

[Generate PRDs, test cases and product documentation with Figr AI](https://www.youtube.com/embed/TeR251naXr4)

Figr turns a flow, prototype or PRD into test cases your QA team can use. Each case covers what to do, what should happen, and which edge cases to check, so testing starts from the design instead of guesswork.

**1. Pick what to test**

Select a flow, prototype or PRD on your canvas.

**2. Attach your Context Pod**

Select your pod in the chat so the test cases follow your product's real rules and roles.

**3. Ask Figr for test cases**

For example: "Write test cases for this sign-up flow, including edge cases."

![A test case prompt in the chat box with the flow attached](https://mintcdn.com/figr-1af7ae64/6fNHqiw94uTEs_lh/images/docs/test-03-prompt-1.png?fit=max\&auto=format\&n=6fNHqiw94uTEs_lh\&q=85\&s=b74c06d52bbcf22d29403efcea35ee1c)

**4. Review the test cases**

Figr lists each case with steps and the expected result. Remove what's out of scope and add anything specific to your setup.

![Generated test cases on the canvas](https://mintcdn.com/figr-1af7ae64/6fNHqiw94uTEs_lh/images/docs/test-04-list-1.png?fit=max\&auto=format\&n=6fNHqiw94uTEs_lh\&q=85\&s=d1fc2487b43834a749403e005c765b90)

> [!TIP]
>
> Map edge cases first, then generate test cases. Figr turns each edge case into a test, so nothing you designed for goes untested.

**5. Hand them to QA**

Share the test cases with your team, or copy them into your testing tool.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.