Milestones
A milestone is a named delivery event — a release, a sprint, a beta, a go-live — that you can attach test runs to. When multiple runs are linked to a milestone, Collabase aggregates their results into a single quality view: overall pass rate, failure count, and pending count.
Milestone fields
| Field | Required | Description |
|---|
| Name | Yes | e.g. “v2.4 Release”, “Sprint 12”, “Q1 Beta” |
| Description | No | Context about this milestone |
| Target Date | No | Planned delivery date — shown in the milestone list |
Creating a milestone
- Test Project → Milestones → + New Milestone
- Name it and set a target date
- Save
Then link runs to it when creating them (or edit an existing run and set its Milestone field).
Milestone quality dashboard
Open a milestone to see the aggregated view:
- Overall pass rate across all linked runs
- Failure breakdown — which cases failed across the milestone
- Run list — each linked run with its individual pass rate and case count
- Timeline — when each run was executed
Using milestones as quality gates
Before shipping, check the milestone dashboard:
- Pass rate ≥ your team’s target (e.g. 95%)?
- All CRITICAL priority failures resolved?
- No BLOCKED cases in any of the linked runs?
If yes, the milestone is shippable.
Use Automation to enforce this: trigger a Slack message to the release channel when a milestone’s pass rate crosses 95% — trigger: testRunCompleted, action: Collabase getMilestoneStats + Slack message.
