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

# For QA

> Testing an Almedia Link integration before it ships, and confirming it works once it is live.

This section is for whoever signs off that the integration actually works — QA, release
management, or the engineer doing the last pass before a build goes out.

It is deliberately separate from the [engineering docs](https://docs.almedia.dev/technical.md): those describe how to
build the integration, these describe how to prove it behaves correctly for a real player.

## The three passes

> **[Set up a test build](https://docs.almedia.dev/qa/test-build.md)**
>
> Devices and OS versions, which build talks to which backend, and how to force any SDK state
> from the Unity editor.

> **[Test checklist](https://docs.almedia.dev/qa/test-checklist.md)**
>
> What a successful link looks like end to end, what a failed one looks like, and the order to
> test the experiences in.

> **[Verify attribution](https://docs.almedia.dev/qa/verify-attribution.md)**
>
> Confirm events are reaching Almedia, and the three failures that account for almost every
> problem on a live integration.

Work through them in that order. The first is a one-time setup per project; the other two run
on every build that touches Link.

## Two references worth having open

* The **[best practices guide](https://docs.almedia.dev/overview/best-practices.md)** states the rules the player-facing
  placement is judged against — timing, dismissal, CTA wording, reward wording. It also carries
  two AI audit prompts that will grade a screenshot of your pop-up or entry point against those
  rules and return a pass/fail scorecard.
* The **[MMP Setup pages](https://docs.almedia.dev/publisher/mmp.md)** list the exact settings and event names your
  dashboard should show, which is the reference to check a live integration against.

> [!NOTE]
>
> Attribution problems are quiet — nothing errors, and the symptom is players earning less than
> they should. If the numbers disagree and the cause is not obvious, send what you are seeing to
> `link@almedia.co` rather than changing settings to make the totals match.


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