Coming soon
QA test management

Test smarter. Ship safer.

Structured test planning, guided execution, evidence capture, and release gating — integrated with your tasks and release pipeline. It's on our roadmap and not yet available.

On the roadmap

The QA toolkit we are building

QA test management is not available yet. Here is the structure and traceability we are designing for QA teams.

Test plans

Planned: organize testing by release or milestone, define scope and entry/exit criteria, assign testers, and track overall progress.

Case management

Planned: a reusable test case library with steps, expected results, and preconditions, organized into suites and linked to your work.

Test execution

Planned: run cases individually or in bulk and record pass, fail, or blocked results, with execution time captured automatically.

Evidence capture

Planned: attach screenshots, logs, and recordings to results so every test outcome carries a complete, reviewable trail.

Release gating

Planned: tie test outcomes to release readiness so under-tested work is visible before a release is marked ready.

Automation & webhooks

Planned: trigger runs from CI pipelines and receive results via webhooks, alongside your existing release integrations.

Guided test execution

We are building a guided execution flow: walk through test steps, mark each as passed or failed, add notes, and attach evidence without leaving the run.

Planned: step-by-step guided execution

Planned: one-click pass, fail, or blocked status

Planned: inline evidence attachment per step

Planned: automatic duration and timestamps

Quality signals for releases

Today, releases already carry per-environment verification tests that must be recorded before an environment is verified — QA will build on that. Test results will feed into the same release readiness model, so quality is part of every readiness decision.

Planned: pass-rate and coverage signals

Planned: readiness checks before a release is marked ready

Planned: visibility of blockers per release

Planned: trends across runs over time

Linked to your tasks and work

When it ships, QA will connect test outcomes to the tasks, products, and releases already in OpsWorker — keeping testing in the same workspace as the rest of delivery.

Planned: links between tests and tasks

Planned: traceability from work to test outcome

Planned: defect capture alongside results

Planned: coverage gaps surfaced per area

QA test management is on the way

We're building structured test management into OpsWorker. Explore everything the platform does today while we get QA ready.