> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/sagent/qa.md).

# QA

Create test cases and run QA tests before release.

The **QA** section helps you verify that Sagent responds safely and behaves as expected. It turns key shopper journeys and safety requirements into repeatable checks before release.

Use **Test Cases** to define expected behavior. Use **Test Results** to run those checks and investigate failures.

Use **Test Results** to run safety and regression tests. Use **Test Cases** to define the prompts and assertions those tests evaluate.

### Use QA as a release gate

**Test Cases** define what must pass. Each case contains a shopper scenario, prompt, expected outcome, and any required assertions.

**Test Results** show what happened when Sagent ran those cases. Use them to compare actual behavior with the expected outcome and identify failures.

Run QA in this order:

1. Create or update **Test Cases** for new journeys, tools, content, and safety risks.
2. Run **Test Results** against the release candidate.
3. Investigate unexpected outcomes and correct the related configuration.
4. Run affected cases again and record the final result.

Publish only when required cases pass and unexpected results are resolved. Treat a changed catalog, prompt, knowledge source, translation, or design as a reason to rerun affected cases.

{% hint style="warning" %}
Passing an earlier run does not approve later changes. Run Test Results again after each release-impacting update.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.crobox.com/how-to-guides/sagent/qa.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.