Testmo for Teams: Roles, Assignments, Milestones, and Cross-Team Collaboration

Testmo for Teams: Roles, Assignments, Milestones, and Cross-Team Collaboration

Test management is fundamentally a coordination problem. Someone writes test cases, someone assigns them for execution, developers fix bugs, and QA managers need visibility across all of it. Testmo's collaboration features are designed around these workflows.

This guide covers how Testmo handles multi-person QA: roles and permissions, test assignment, milestone coordination, and integration with the issue trackers developers already use.

User Roles and Permissions

Testmo has three role levels:

Administrator — full access to everything. Manages billing, users, projects, and system settings. Typically the QA lead or head of engineering.

Member — the standard role for QA engineers. Can create and edit test cases, create and execute runs, submit automation results, run exploratory sessions, and view all reports. Most of your team will have this role.

Viewer — read-only access. Can view test cases, runs, reports, and automation results, but cannot make changes. Useful for developers, PMs, or stakeholders who need visibility into QA status without editing access.

Roles are per-project in Testmo. A user can be an administrator on one project and a viewer on another. This lets you give individual teams ownership of their own test suites without exposing unrelated projects.

Restricting Automation Tokens

API tokens used for CI submissions are tied to a project and have their own access level. You can create read-only tokens for monitoring tools and write tokens for CI pipelines. Revoking a CI token doesn't affect user access, and vice versa.

Test Case Assignment

Test cases don't have permanent owners in Testmo — ownership happens at the run level. When you create a test run, you can assign individual test cases (or groups of cases) to specific team members.

Assigning Cases in a Run

When creating or editing a run, each test case can be assigned to any member. The assignment appears in the tester's personal queue ("My Tests") and in the run's assignment summary view.

For large regression cycles with multiple testers, Testmo provides several assignment strategies:

Manual assignment — you drag or select cases and assign them to specific people. Good for distributing work by expertise area ("Sarah handles checkout flows, Marcus handles account settings").

Balanced auto-assignment — Testmo distributes cases evenly across selected team members. Fastest for routine regression where any tester can cover any area.

Round-robin — similar to balanced, but sequential rather than optimized. Useful when you want predictable distribution patterns.

My Tests Queue

Each team member sees their personal "My Tests" view — a filtered view of runs showing only their assigned cases. This is the working view for testers during active regression cycles. They don't need to see the full run or other testers' assignments.

Tracking Tester Progress

Run managers see per-tester progress in the run's overview: how many cases each tester has completed, their current pass/fail counts, and cases not yet started. This surfaces blockers early — if one tester is stuck, it shows before the run misses a deadline.

Milestones

Milestones in Testmo correspond to releases, sprints, or testing phases. They're optional but valuable for teams doing formal release cycles.

Creating Milestones

A milestone has:

  • Name and description
  • Start date and due date
  • Status (open, completed)
  • An optional parent milestone (for hierarchical organization — e.g., a release milestone with sub-milestones per sprint)

Linking Runs to Milestones

When creating a test run, you assign it to a milestone. All runs in a milestone aggregate into the milestone's summary report. A release milestone might contain:

  • "Regression - Sprint 23" run
  • "Smoke tests - Release candidate 1" run
  • "Edge cases - Checkout flow" run
  • "Regression - Sprint 24" run (regression after bug fixes)

The milestone report shows the aggregate: total cases across all runs, pass rate, what changed between early and late runs in the cycle.

Milestone Due Dates and Progress Tracking

Milestones show a progress indicator: number of runs completed vs. planned, and the percentage of test cases in associated runs that have been executed. If your milestone is due in 3 days and you're 60% through test execution, you have a decision to make.

QA managers use milestone progress in stand-ups and release meetings. "We're at 78% pass rate with 20 cases still blocked waiting for bug fixes" is a concrete status update derived from Testmo data.

Jira Integration

The Jira integration is the most important collaboration bridge for teams where developers work in Jira. It's bidirectional.

Linking Test Cases to Jira Issues

A test case can reference one or more Jira issues. This creates a navigable link: from a test case, click through to the Jira issue. From a Jira issue (with the Jira app installed), see linked test cases and their recent pass/fail status.

This matters for traceability: "which test cases verify this requirement?" and "which Jira issues are covered by this test case?"

Linking Test Runs to Jira Issues

A test run (or individual test failure) can be linked to a Jira issue. When a test case fails, you can create a new Jira bug directly from Testmo, pre-populated with the failure details, steps, and attachments.

Testmo App for Jira

Install the Testmo app from the Atlassian Marketplace to see Testmo test case and run information directly in Jira issue views. Developers reviewing a bug ticket see the associated test cases and whether they're currently passing or failing.

Linear and GitHub Issues Integration

For teams using Linear or GitHub Issues instead of Jira, Testmo provides similar (though less deep) integrations:

  • Link test cases to Linear issues or GitHub issues
  • Create issues from test failures
  • Navigate between the tools via links

These integrations are primarily link-based rather than embedded-view like the Jira app. For most teams, linking is sufficient.

Slack and Teams Notifications

Testmo sends notifications via webhook to Slack or Microsoft Teams. Configurable events include:

  • Test run created
  • Test run completed
  • Milestone created or completed
  • Automation run submitted (optionally filtered by pass/fail status)

A useful pattern: create a #qa-failures Slack channel and configure Testmo to notify it whenever an automation run has a pass rate below 90%. This gives developers immediate visibility into CI failures without requiring them to check Testmo directly.

Exploratory Testing as Collaboration

Exploratory sessions are how teams capture ad-hoc findings and share them beyond the individual tester.

Session Missions and Team Coordination

A testing session has a "charter" or mission — a short description of what to explore and what questions to answer. Sessions are visible to the whole team. Before starting ad-hoc exploration, check whether another team member already ran a session on the same area recently.

Session Findings as Bugs

During a session, findings go into the session log. Each finding can be elevated to a formal bug report — either filed directly in Testmo as a failed test case, or pushed to Jira/GitHub Issues. This prevents findings from being lost in personal notes.

Session Reviews

After a session, the log is permanent and reviewable. QA leads can review sessions to assess coverage, find patterns across multiple sessions, and identify areas that need formal test cases.

Managing Multiple Projects

For organizations with multiple products or teams, Testmo's project isolation matters. Each project has:

  • Its own test case repository
  • Its own runs and automation history
  • Its own milestones
  • Its own user roles
  • Its own API tokens

Cross-project reporting is available in the global Reports view — you can see aggregate statistics across all projects, or compare projects on key metrics. But day-to-day work is project-scoped, which prevents noise and permission confusion.

Most teams should map Testmo projects to products or applications, not to teams. The product is the right boundary because it matches what's being shipped. One team might own multiple products, or multiple teams might contribute to one product.

Avoid one project per feature or microservice — this creates too many small projects with thin test coverage in each. The overhead of managing many projects usually outweighs the organizational benefit.

Onboarding New Team Members

Testmo's learning curve is low. A new QA engineer can be productive within their first day:

  1. Create an account and accept the project invite
  2. Review the test case repository structure (30–60 minutes for a medium-sized repo)
  3. Get assigned a subset of cases in an active run
  4. Work through assigned cases in "My Tests"

The main onboarding challenge is usually understanding the test case structure rather than the Testmo UI. Document your folder hierarchy and tagging conventions in a README or wiki page.

Summary

Testmo's collaboration features are designed around the actual workflows of QA teams: assigning work for regression cycles, tracking milestone progress, integrating with developer issue trackers, and capturing exploratory findings in a shared record. The Jira integration is strong enough to bridge the QA-developer gap for most teams, and the Slack notification setup is simple enough to configure in minutes.

The most important collaboration practice isn't about features — it's keeping your Testmo projects accurate. Old test cases that nobody runs, milestones that never close, and runs that don't get reviewed undermine the tool's value. Regular housekeeping (archive stale cases, close completed milestones, clean up orphaned runs) keeps Testmo useful as a source of truth.

Read more

Start now free