What is QA Sync?
QA Sync is a browser-based workspace for coordinating software delivery and quality assurance. It replaces QA that lives in chat threads, calls and spreadsheets with structured tasks, structured test results, role-based access and a full audit trail.
The problem it solves
Section titled “The problem it solves”QA tends to break down in the same places:
- Testers don’t know what to test, or which build they are testing.
- Issues arrive in inconsistent formats, without device, environment or reproduction details.
- Developers get incomplete reports and can’t tell what’s blocking a release.
- Nobody has one view of who has access, which areas of the product exist, and where coverage is missing.
- New testing needs appear faster than formal test tasks are written.
QA Sync makes each of those explicit: every task has instructions and an expected result, every QA run records a status, severity and evidence, and every privileged change is written to an audit log.
How it works
Section titled “How it works”- Your organisation is set up. QA Sync provisions an organisation for your company and makes the person who requested it the first Organisation Admin. See Request access.
- Admins model the product. Work is organised as apps → modules → submodules → tasks. Each task has test instructions, an expected result, an assigned developer and assigned tester groups. See Apps, modules and sprints.
- Developers deliver. Tasks move through one shared lifecycle, from Draft to Production. Developers move their own tasks from Planned to In Progress, In Review and then Staging. See Task lifecycle.
- Testers verify. When a task reaches Staging it appears in the queue of every tester in its assigned groups. A tester records a QA run as Passed, Failed or Blocked, with notes, reproduction steps and screenshots. A pass moves the task to Ready to Ship; a failure sends it back to In Progress. See QA execution and evidence.
- Releases are approved. Ready-to-ship items collect the approvals your rules require. Product managers complete product approvals, and admins promote the release to Production. See Approvals and releases.
- Everyone stays informed. Status changes, QA results, approvals and @mentions create in-app notifications, and every item keeps its status history, activity timeline and comments.
Who uses it
Section titled “Who uses it”| Role | What they do in QA Sync |
|---|---|
| Admin | Manages members, apps, tester groups, modules, tasks, task requests, approval rules and releases for the organisation. |
| Product Manager | Tracks portfolio, roadmap and release health; completes product manager approvals. |
| Developer | Moves assigned tasks through delivery; triages issue reports; escalates tester suggestions. |
| Tester | Runs QA on staging tasks for their groups; records results with evidence; requests missing test coverage. |
| UI Designer, Client, Viewer | Follow progress and release readiness; read history; leave comments. |
Read more in Roles and permissions.
What QA Sync is not
Section titled “What QA Sync is not”QA Sync is deliberately focused. It does not:
- accept public bug reports from your end users;
- run automated tests;
- sync with third-party issue trackers;
- offer public sign-up, single sign-on or a public API.