QA is a team sport. The platform should act like it.
Comments. Mentions. Presence. Review workflows. Edit locks. Role-based access. The infrastructure for teams that need to stay aligned without stepping on each other.
Threaded Comments
Comment on a test case. Thread replies. Attach a comment to a specific step — the step index is stored, so the comment appears where it belongs.
@mention a teammate and they get an email. No context switch required to ask a question about a specific test step.
[data-testid="apply-btn"]Edit Locks & Presence
A 5-minute edit lock prevents two people from overwriting each other. Renewable in-session. Real-time WebSocket presence shows exactly who is viewing or editing the same test case.
Concurrent editing conflicts don't fail silently in RuyQA. They don't happen.
Review Workflow
Request review: the test case moves to IN_REVIEW. Approve: moves to APPROVED. Reject: returns to DRAFT with a required rejection note. Deprecate: marks the case as no longer maintained.
Review queue per project. Stats by status. The workflow is the governance layer for your test suite.
Roles
OWNER, ADMIN, MEMBER, VIEWER. Invitation by email with accept/reject. Admin impersonation for support and debugging — with a full ghost-mode audit trail.
Every action, every role change, every impersonation: logged.
Bring your team together.
Collaborate on test cases, review changes, and ship quality as a team.
Start Free Trial