> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/price-testing/price-testing-integration-guides/integration-guide-using-shopify-functions/step-4-qa-your-integration-and-publish-your-changes.md).

# Step 4: QA your integration, and publish your changes

After you have completed all previous integration steps, preview the test and make sure prices are correct for each test group, anywhere prices appear on the site. Follow our QA checklist [here](/price-testing/price-test-qa-checklist.md).

Once you have verified Intelligems is fully integrated, you can publish your theme changes (if you haven't already) and start your test from the Intelligems App! Check out our step-by-step guide on doing this [here](/price-testing/starting-a-price-test.md).

#### What happens next?

Now that you've started your first test, here are some things to do next:

* Check the Results tab in your test to see how the test is doing frequently.
* Start thinking about your [testing roadmap](/getting-started/best-practices/test-design-best-practices.md).
* Review some [test suggestions](/getting-started/common-use-cases.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 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.intelligems.io/price-testing/price-testing-integration-guides/integration-guide-using-shopify-functions/step-4-qa-your-integration-and-publish-your-changes.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.