> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/docs/getting-started-guide/testing-and-qa.md).
# Testing and QA
You're almost there! Your data feed is imported, the basic configuration is complete, and your integration is in place. Just a few more steps until go-live.
One of the most important steps before go-live is FactFinder quality assurance (QA) and testing. Your Technical Consultant will QA your integration—including all modules and tracking—and highlight any topics to address before go-live.
Depending on the modules you selected, our Technical Consultants conduct QA using a detailed checklist and generate a report with findings and recommendations.
## What will be tested?
The testing process is primarily centered around two key aspects:
* Does the webshop frontend display the same search results as the FactFinder UI?
* Is the technical integration set up correctly (e.g., parameters)?
## When will it be tested?
As soon as you let us know we can start QA, we will schedule testing accordingly.
## What can you do to speed up the process?
It greatly accelerates the process if you and/or your integration partner perform a QA assessment before granting approval for testing.
The following checklist provides **examples** of test scenarios:
| **Example test scenarios** | **Expected behavior** | **Result** |
| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
| Make a search | The search works and the products from the FactFinder backend match the products in the shop | |
| Type something in suggest and compare shop result with FactFinder Backend | Suggest works and the same suggestion will be shown in the shop and in the FactFinder backend | |
| Check paging or scrolling | Paging or "scrolling" in the result overview page is implemented and page count is displayed.
Same result shown when moving to next page and back to previous one
| |
| Sorting options available | Sorting works and by default the results are sorted according to relevancy | |
| Article Number Search - Take some article numbers and randomly check by searching for them | Only one product is found | |
| Make search and use ASN | Filtering works.
Every filter type can be selected without loss of already chosen filters
| |
This is a brief overview of typical use cases. For a more comprehensive QA process, contact our Technical Consultants for assistance and guidance.
## After QA
Once QA is completed, you will receive a report indicating whether you're ready for go-live and any outstanding issues to address.
---
# 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.fact-finder.com/docs/getting-started-guide/testing-and-qa.md?ask=&goal=
```
`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.