What TestBridge does
TestBridge is a QA handoff and verification platform. It tracks a defect from the moment QA finds it to the moment QA proves it is fixed on a real build, and it enforces each step along the way. A defect cannot reach a tester until the fix is actually deployed. It cannot be closed without a recorded retest against a named build.
You can use it on the web and in the iOS and Android apps. Both run against the same account and the same data.
Create your account
- 1Go to Create account and enter your organization name, your name, your work email and a password of at least 8 characters.
- 2TestBridge creates your organization and makes you its Organization Admin. You are signed in straight away.
- 3Everyone else joins by invitation from you. There is no separate sign-up for teammates.
Were you invited by a teammate? Don’t create a new account. Open the invitation email and choose a password from there, so you join your team’s organization.
Set up a project
Defects live in projects. Organization Admins and Product / Project Managers can create one from Projects.
- 1Give the project a name and a short key, such as SFS. Every defect gets a reference from it: SFS-1, SFS-2 and so on.
- 2Choose the environments and platforms you test on. These populate the defect form and the filters.
- 3Optionally add custom fields, such as “Affected module”, and mark the ones a reporter must fill in.
- 4Set SLA targets per severity: how quickly a defect must be acknowledged and resolved. Defects that miss them are escalated to the leads.
- 5Add members to the project. Only project members see its defects.
Invite your team
Open Organization → Members and invite people by email with a role. Each person receives an email with a link to set their password. You can resend an invitation or change someone’s role later. Only Organization Admins can invite people or change roles.
Roles and permissions
Each person has one role in your organization. The role decides which screens they see and which actions the API allows.
| Role | What they do |
|---|---|
| QA Tester | Reports defects, retests fixes and records the outcome against a build. |
| QA Lead | Everything a tester does, plus triage, imports and share links. |
| Developer | Works assigned defects, breaks them into sub-tasks and submits fixes. |
| Engineering Lead | Triages, assigns work across the team, confirms deployments and manages the CI and repository connections. |
| Product / Project Manager | Creates projects, triages and follows release readiness. |
| Viewer / Client | Read-only access to the projects they belong to. Internal comments are hidden from them. |
| Organization Admin | Full control: members, roles, projects, organization settings and the audit log. |
How a defect moves
Every defect follows one path. Each arrow below is a rule TestBridge enforces, and every change is recorded in the defect’s timeline with who made it and when.
- ReopenedA retest fails — back to the developer with the reason
- BlockedWork cannot continue until something else is resolved
- RejectedTriage decides it is expected behaviour, cannot be reproduced or won’t be fixed
- DuplicateMerged into an existing defect during triage
Report a defect
Use Report Defect on the web, or the report button in the mobile app. The form saves a draft as you type, so you can leave and come back.
- 1Write a clear title and pick the issue type: defect, improvement, feature request or technical task.
- 2Add the environment, platform, device and app version or build number you tested on.
- 3List the steps to reproduce, then the expected and the actual result.
- 4Attach evidence: screenshots, screen recordings or a voice note. Large recordings upload directly and resume if the connection drops.
- 5Submit. The defect leaves your drafts and goes to triage.
Each report gets a quality score based on what it contains. The form shows what is still missing. Your organization can set a minimum score that a defect must reach before it can be assigned.
Triage
QA Leads, Engineering Leads and PMs work the Triage queue. It lists new and reopened defects, with blockers first. For each defect you can:
- Set severity and priority, and place it in a release.
- Assign it to a developer.
- Ask the reporter for more information. The defect goes back to them, and they resubmit.
- Merge it into an existing defect as a duplicate.
- Reject it as expected behaviour, cannot reproduce, or won’t fix.
Fix and submit
Developers find their work in My Work. Acknowledging a defect starts its SLA clock and shows the team someone owns it.
- 1Optionally split the work into sub-tasks (backend fix, UI, migration, regression test, deploy). Any open sub-task blocks the handoff, so half-finished work never reaches QA.
- 2When the fix is done, submit the fix with the branch and the build it ships in. A linked pull request is attached automatically if your repository is connected.
- 3The defect moves to Waiting for deployment. Merging code alone does not make it retestable.
Deployment and handoff
A defect becomes Ready for retest only when its build is confirmed live in an environment. That confirmation can come from either of two sources:
| Source | How it works |
|---|---|
| CI webhook | Your pipeline calls the project’s signed webhook after a deploy. Every defect waiting on that build advances within seconds and is marked as system-verified. |
| Manual attestation | An Org Admin, PM or Engineering Lead confirms the build is deployed. Their name is permanently recorded against the handoff. |
The reporter and the QA team are notified as soon as the defect is ready.
Retest and verify
Testers work the Retest Queue. It is grouped into ready, in retest, waiting for build, overdue, failed and blocked. Start a retest, test on the named build, and record one outcome with evidence:
- Passed
- Failed — same behaviour
- Partially fixed
- Could not reproduce
- Blocked
- Regression introduced
Passed verifies the defect. A failure reopens it and sends it back to the developer with your comment. Every attempt is kept with its build, tester and evidence, so you can always see what was tested and where.
Releases and reports
Releases groups defects by release and shows readiness: how many are cleared, reopened, blocked or still outstanding. Reports covers cycle time, reopen rate and SLA performance, with a CSV or Excel export of any filtered defect list and a weekly PDF summary per project.
Integrations
| Integration | What it does |
|---|---|
| GitHub | Add a repository webhook. Pull requests that mention a defect key are attached to that defect. |
| CI / CD | Call the project’s signed deployment webhook from your pipeline to confirm builds automatically. |
| Slack and Discord | Post defect events to a channel, filtered by event type and minimum severity. |
Set them up in Integrations. Webhook secrets are visible only to Org Admins, PMs and Engineering Leads.
Import a spreadsheet
Moving from a spreadsheet? QA Leads and Org Admins can upload a CSV or paste a shared Google Sheet link in Import. TestBridge suggests a column mapping and matches people by name or email. It then runs a dry run that shows exactly what will be created and what will be skipped, before anything is written. You can roll back an import after committing it.
Notifications
TestBridge notifies you in the app, by email and by push on mobile. Notifications go out when you are assigned, when a fix is ready to retest, when a retest fails, when someone mentions you, and when an SLA is breached. Choose which channels you want in Settings.
Mobile app
The iOS and Android apps use the same sign-in as the web. Testers can file a defect with a screen recording straight from the device, work the retest queue and record outcomes. Developers can acknowledge and update their assignments. Drafts survive the app being backgrounded mid-form.
