The Releases feature in TestCollab helps teams decide with confidence whether a release is ready to ship.
By associating test plans with a release, TestCollab automatically aggregates execution results, defect data, evidence coverage, and test coverage to generate a real-time Go / No-Go verdict all in one place.
Instead of manually reviewing spreadsheets or multiple reports, you get a clear, actionable readiness status backed by configurable thresholds.
π― What Is a Release in TestCollab?
A Release represents a specific version or milestone of your software (e.g., v2.5.0, Sprint 24, Q1 Release).
Each release can have:
Associated test plans
A tracked release status
A calculated readiness verdict
Coverage and defect metrics
A shareable dashboard
π Creating and Managing Releases
To create a release:
Go to the Releases section.
Click Create Release.
Enter release details
Name and description,
Status,
Target date and release date
Public / Private
Go / No-Go thresholds - to decide when release ready to ship
β Min pass rate (%)
π Max open defects
π Min evidence (%)
Save.
You can:
βοΈ Edit a release
π Delete a release
Release Status Options
Planned
In Progress
Ready
Shipped
Blocked
πΈ Screenshot: Create/Edit Release screen
π’π΄ Automated Go / No-Go Verdict
The system automatically generates a Go or No-Go verdict based on configured thresholds.
The verdict considers:
β Pass rate
π Open blocker or critical defects - status will be synced from defects manager
π Evidence coverage - the attachments added at the time of test execution
If the defined thresholds are met, the release is marked Go.
If not, it remains No-Go until conditions improve.
This ensures decisions are objective, consistent, and data-driven.
Other verdicts can be:
At Risk
Pending
The readiness verdict updates automatically in the background when:
Test results change
Test cases are added or removed
Test plans are associated or disassociated
Defect statuses are updated
βοΈ Configurable Thresholds
Each project can define its own readiness rules, such as:
Minimum pass percentage required
Maximum allowed open critical defects
Required evidence coverage percentage - Measures what percentage of failed test cases have attachments (screenshots, logs, etc.)
This flexibility allows different teams to align release readiness with their quality standards.
π Multi-Dimensional Coverage Insights
The readiness dashboard provides coverage breakdowns across:
Test Suites
Configurations (e.g., Browser, OS, Device)
Custom Fields (e.g., Module, Feature)
This allows you to quickly answer questions like:
Are all critical modules fully tested?
Did we cover all required browser configurations?
Which areas have lower pass rates?
π Release Comparison (Delta View)
You can compare the current release against the previous one.
The system highlights:
π Drop in pass rate
π Improvement in coverage
π Changes in defect counts
This helps stakeholders understand whether quality is trending upward or downward before shipping.
π Public Read-Only Dashboard Sharing
Need to share release readiness with stakeholders, clients, or leadership?
You can generate a token-based public URL that provides:
Read-only access
Real-time metrics
No login required
This is ideal for executive reporting or external visibility.
π§ Why Use Releases?
The Releases dashboard helps you:
Make objective Go/No-Go decisions
Eliminate last-minute uncertainty
Improve cross-team transparency
Maintain audit-ready release documentation
Track quality trends over time
Instead of asking, βAre we ready?β, you will know.
β Best Practices
Define clear readiness thresholds before starting execution.
Associate only relevant test plans to avoid misleading metrics.
Monitor coverage across critical configurations.
Use comparison view during release reviews.
Share public dashboards for leadership visibility.
π¬ Conclusion
The Releases & Release Readiness Dashboard transforms release decisions from subjective discussions into data-backed outcomes.
By combining execution results, defect insights, and coverage metrics into one unified view, TestCollab helps teams ship confidently, and only when truly ready.







