Skip to main content
This page is under construction. More content coming soon!

​
Collaborative Testing

OneTest enables teams to work together seamlessly on test creation, execution, and analysis.

​
Team Features

Product Members

Invite team members with role-based access (Owner, Member)

Test Assignment

Assign tests to specific team members for execution

Real-time Updates

See test run progress as team members execute tests

Comments & Notes

Discuss test cases and results within the platform

​
Team Workflows

​
Collaborative Test Writing

1

Define Test Scope

Team lead creates test outline or uses AI to generate drafts
2

Assign for Detail

Assign incomplete tests to domain experts:
  • Frontend tests → Frontend engineers
  • API tests → Backend engineers
  • Mobile tests → Mobile team
3

Review & Refine

Team members review each other’s tests:
  • Check for completeness
  • Verify steps are clear
  • Ensure expected results are specific
4

Approve

QA lead or team lead approves final tests
Use the AI Assistant to generate initial test drafts, then have team members refine the details.

​
Best Practices for Teams

Why: Prevents “bystander effect” where no one maintains testsHow:
  • Assign tests to specific people or teams
  • Use custom field: owner: "auth-team"
  • Make ownership visible in test metadata
  • Review ownership quarterly
# Find unowned tests
status = active AND owner IS NULL
Why: Ensures consistency across teamHow:
  • Create test case templates
  • Document test writing guidelines
  • Use AI prompts for consistent generation
  • Review new tests for adherence
Save common AI prompts as prompt templates for the whole team to use.
Why: Keeps team aligned on testing strategyAgenda:
  • Review pass rates and trends
  • Discuss flaky tests
  • Identify coverage gaps
  • Plan upcoming test work
  • Share best practices
Frequency: Weekly or bi-weekly
Why: Prevents duplicate effortHow:
  • Create reusable test steps
  • Share test data sets
  • Document common workflows
  • Use saved OQL queries
  • Build test case templates
Why: Improves team capabilityHow:
  • Document domain knowledge
  • Pair testing sessions
  • Internal testing workshops
  • Share test case examples
  • Code review for test automation

​
Team Roles & Responsibilities

​
QA Lead Responsibilities

Test Strategy:
  • Define testing approach
  • Set quality gates
  • Choose test types and coverage targets
Team Management:
  • Assign tests to team members
  • Monitor test execution progress
  • Balance workload
Quality Oversight:
  • Review test results
  • Triage failures with team
  • Make release decisions

​
Communication Tools

In-App Comments

Comment directly on test cases and results

Slack Integration

Get notifications in your team Slack channel

Email Notifications

Receive alerts for test failures and completions

Status Dashboards

Shared dashboards for team visibility

​
Handling Conflicts

Problem: Two people edit the same test simultaneouslySolution:
  • OneTest uses versioning—both edits are saved
  • Compare versions and merge manually
  • Communicate before major test updates
  • Use assignment to indicate “I’m working on this”
Problem: Team members have different opinions on how to testSolution:
  • Discuss in team meeting
  • Document testing standards
  • Defer to QA lead for final decision
  • Try both approaches and compare
Problem: Unclear who owns certain testsSolution:
  • Default to feature team ownership
  • For cross-cutting tests, assign primary owner
  • Document ownership in test metadata
  • Review ownership during test audits

​
Metrics for Team Performance

Track these metrics to improve team effectiveness:

Test Velocity

Tests created/executed per sprint

Coverage Growth

Percentage of features with tests

Defect Detection Rate

Bugs found vs. bugs escaped to production

Cycle Time

Time from test creation to execution

Pass Rate Trend

Quality improvement over time

Automation Ratio

Automated vs. manual tests

​
What’s Next?

Organizing Tests

Structure for team collaboration

Best Practices

Testing best practices for teams

Smoke Tests

Critical path testing workflow

Regression Tests

Comprehensive testing workflow