Skip to content

Deployments & triggers

A deployment happened. Did QA Wolf test it?

Date
2026
Role
  • UX design
  • Interaction design
  • Prototyping
Collaborators
Product engineers

Did testing happen?

A deployment can be ready without any tests having run. A test results page won't explain that gap.

I worked with product engineers to make untested deployments visible. Connecting deployment activity with trigger rules gives users a place to understand why testing didn't happen.

A failed deployment and a failed test need different responses. We separated their statuses so users can tell whether to investigate the deployment, the trigger, or the tests.

We designed the detail drawer to distinguish deployment failures from testing issues, so users can see what needs attention and what to do next.

Deployment states

The deployment is ready. Nothing tested it.

Expand “PR Testing - Release” to see the environment mismatch. “Create trigger” carries production-beta into the configuration.

Build confidence in automated testing

Setting up a trigger means deciding how future deployments will be tested. We separated when to run from what to test, then brought those choices together in a preview so users could verify the automation before enabling it.

1. Set the condition
2. Check what will run