Improvements
Record observations and expected behavior, then use retest evidence to decide resolution
Improvements tracks follow-up work with expected behavior, actual observations, related pages, features and tests, and a decision history.
Register an improvement
Start from page details, feature details, or a test result to prefill references to that source. You can also register a record directly in Improvements.
- Enter a title and observed behavior.
- Describe the behavior the product should provide.
- Review the page URL, related test, and priority before saving.
For example, record “Order appears complete after card authorization fails” rather than “Payment failure.” The expected behavior could be “Keep the order incomplete and offer payment retry.”
Status and decisions
| Status | Meaning |
|---|---|
| Needs review | Review the observation and expected behavior |
| Planned | Accepted for improvement |
| In progress | Investigation or changes are underway |
| Needs retest | Check execution evidence after a change |
| Resolved | Explicitly judged resolved after reviewing evidence |
| Deferred | Decision postponed |
| Dismissed | Excluded from improvement work |
Record a reason when changing status. Completing an AI investigation or fix does not automatically resolve an improvement.
Retest
If a test is linked, start a retest from improvement details. Confirm current code and environment in run settings. After execution, select its record as Retest evidence and save the status and decision note. Requesting a run alone neither attaches its result nor resolves the record.
Recurring observations
Registering the same source identifier, target, and expected behavior from a page or test result appends an observation to the existing record. Recurrence on a resolved record returns it to Needs review. Similar manually entered prose is not automatically merged, and collection findings are not automatically registered.
Observation text and evidence references remain in the improvement. Original reports, captures, or files may no longer open after retention cleanup. Registering an improvement does not create a separate backup of its artifacts.
Use Changes to compare runs and Reports and analytics to inspect execution evidence.