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

# QA testing guide

> How QA testers and agents use the Soundcheck test plans: environments, builds, accounts, test data rules, and how to report a bug.

These pages tell a tester, human or agent, what to test in Soundcheck, where to test it, and what is not a bug. Start with [What's ready](https://docs.soundchecklive.io/qa/scope.md) to see every feature that is ready for QA and which build carries it. Then open the test plan for the feature you are testing.

## How a test plan is laid out

Test plans use these sections, in this order. A plan leaves out a section it does not need, and some plans add their own, such as **API only** or **Edge cases worth a run**.

| Section | What it holds |
| - | - |
| **At a glance** | Platforms, roles, the feature flag, the build it needs, and where it is deployed. |
| **Before you start** | Accounts, org, and test data the checks need. |
| **In scope** | Numbered checks such as `CHAT-07`, each with its steps and expected result. A long plan splits this into areas or roles, and names the role and platform on each check where they matter. |
| **Out of scope** | Work that is not built yet, or not part of this feature. Do not file these as bugs. |
| **Known limitations** | Behavior that looks wrong but is intended. Do not file these as bugs. |
| **Needs a real device** | Checks that a simulator, Revyl, or a browser cannot prove, such as push, SMS, or the share sheet. The chat plan puts these under **Text message crew** and **Push notifications**. |
| **For agents** | API calls, analytics events, and commands an agent uses to run or verify the checks. |

Refer to a check by its ID in every bug report and test run, for example "`TC-14` fails on iPhone 15, iOS 26.2".

## Pick the right environment

Each surface talks to one backend. Pair a web URL with a mobile build that uses the same backend, or a message sent on one will not appear on the other.

| Backend | Web app | Mobile app | Gets new code when |
| - | - | - | - |
| Dev | `https://dev.app.soundchecklive.io` | Development and Revyl builds | A PR merges into `dev` |
| QA | `https://qa.app.soundchecklive.io` | No mobile build uses the QA backend | `dev` is promoted to `qa` |
| Production | `https://app.soundchecklive.io` | TestFlight, Play internal, App Store, and Play Store | `qa` is promoted to `main` |

> [!WARNING]
>
> TestFlight builds talk to the **production** backend. Work only in the test org you were given. Never open, message, or change a customer org from a test account.

A TestFlight build carries the mobile code from the `qa` branch, but it calls the production API. A mobile check that also needs a new API change passes in TestFlight only after that API change reaches `main`. [What's ready](https://docs.soundchecklive.io/qa/scope.md) shows, for each feature, whether it has reached `qa` and `main`.

### Which mobile build to use

* **TestFlight (iOS).** Use this for manual QA. A new iOS build reaches TestFlight on every push to `qa`. Install the newest build before each test run.
* **Play internal (Android).** An Android build reaches Play internal only when someone builds and submits one by hand, so the newest Play internal build can be older than `qa`. Before you test a recent change on Android, ask the QA lead which `qa` commit the build came from.
* **App Store or Play Store.** Use this only to compare against what customers have today. A store build gets JavaScript changes over the air once they reach `main`. A change that needs a native build waits for the next store release. See [Older builds](https://docs.soundchecklive.io/qa/scope.md#older-builds).
* **Development, Revyl, or simulator builds.** Engineers and agents use these against the dev backend. See the [agent runbook](https://docs.soundchecklive.io/qa/agent-runbook.md).

Over-the-air (OTA) updates can change JavaScript in an installed build without a new build number. Fully close and reopen the app before a test run so it loads the latest update.

## Accounts, roles, and orgs

Most checks name a role. Use a separate account for each role, because Soundcheck shows different screens to each one:

| Role | Who it is | Where they work |
| - | - | - |
| Owner or admin | Runs the org | Mostly web. Some manager actions also exist on mobile. |
| Coordinator | Org or gig coordinator | Web and mobile. Sees crew hours and each person's crew pay, not the gig's other money. |
| Crew member | Works the gig | Mostly mobile. |
| Text-only crew | Crew with a phone number and no app | SMS only. Needs a real phone that can receive texts. |

The QA lead gives each tester their accounts and the test org name. Do not create orgs or invite people outside that org.

### Feature flags decide what you see

Some features are on only for selected orgs. Soundcheck reads its feature flags from PostHog, and one PostHog project serves dev, QA, and production. A flag change therefore applies to every environment at once.

| Feature | Flag | Who has it on |
| - | - | - |
| Chat | `event-chats` | Every `@soundchecklive.io` account, plus listed test orgs |
| Chat photos as MMS | `event-chat-mms` | Nobody. Text-only crew get a text notice instead of the photo. |
| Time clock | `time-clock` | Listed orgs only |

If a feature is missing, confirm with the QA lead that your org is on the list before you file a bug. A missing feature in an org that is not on the list is expected.

## Test data rules

* **Name everything you create.** Start each gig, chat, and note title with `QA` and the check ID, for example `QA TC-03 hourly shift`.
* **Do not publish a draft gig that has invitations.** Publishing a draft sends its pending invitations by push, text, and email to real people. Publish only gigs whose crew are all test accounts.
* **Do not message or @mention real people.** Chat sends pushes and texts. Keep test chats to test accounts.
* **Archive, do not delete, gigs with clocked hours.** The API refuses to delete a gig that has time clock punches.
* **List what you leave behind.** End every test run with the gigs, chats, and records you created, so the QA lead can clean them up.

## Report a bug

File every bug in the Linear **QA** team. Add the **Bug** label, plus **mobile**, **web**, or **backend** for the surface where it happens. One bug per issue.

```text theme={null}
Title: [CHECK-ID] short description of what is wrong

Check: CHAT-07 (link to the test plan)
Environment: production via TestFlight <version> (<build>), or qa.app.soundchecklive.io
Device: iPhone 15, iOS 26.2, light mode, default text size
Account role: crew member in <test org>

Steps:
1. ...
2. ...

Expected: (copy from the test plan)
Actual: what happened instead
How often: every time, 2 of 5 tries, or once
Attachments: screenshot or screen recording
```

Set the Linear priority from the impact:

| Priority | Use it when |
| - | - |
| Urgent | Data loss, wrong pay, a message or punch sent to the wrong people, or a crash on a core flow |
| High | A core flow is blocked and has no workaround |
| Medium | A flow works with a workaround, or a screen shows wrong information |
| Low | Layout, wording, or a visual glitch |

## Test plans

> [card] [What to test](https://docs.soundchecklive.io/qa/scope.md)
>
> Every feature ready for QA, where it is deployed, and what is out of scope.

> [card] [Chat](https://docs.soundchecklive.io/qa/chat.md)
>
> Gig chats on web and mobile, the SMS bridge, and message actions.

> [card] [Time clock](https://docs.soundchecklive.io/qa/time-clock.md)
>
> Crew clock in and out, crew hours, approval, and timesheets.

> [card] [Travel and venue](https://docs.soundchecklive.io/qa/travel-and-venue.md)
>
> Crew flights and rides, the ride card, and the venue map.

> [card] [Mobile gig screens](https://docs.soundchecklive.io/qa/mobile-gig-screens.md)
>
> The redesigned gig screen, staffing, offers, and agreements.

> [card] [Invites and onboarding](https://docs.soundchecklive.io/qa/invites-and-onboarding.md)
>
> Text and email invites, sign-up paths, and where invitees land.

> [card] [iPad, Performance mode, and platform](https://docs.soundchecklive.io/qa/ipad-and-performance.md)
>
> Wide layouts, Performance mode, widgets, and calendar subscribe.

> [card] [Agent runbook](https://docs.soundchecklive.io/qa/agent-runbook.md)
>
> How an agent runs these plans and reports results.


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