Aglet

Product quality playbooks

Investigate usability defects and define checks that reflect real journeys. Choose a scenario, then the decision you need to make.

Flaky test

A test alternates between passing and failing without a stable reproduction, weakening confidence in release evidence.

Missing edge case

A valid but unusual input or state is not covered, leaving a boundary behavior uncertain or vulnerable to regression.

Inaccessible primary action

A primary task action is difficult or impossible to reach for some users, despite the underlying workflow being available.

Browser-specific bug

A workflow behaves differently in one browser or engine, while the same path appears healthy elsewhere.

Broken deep link

A shared or bookmarked URL opens the wrong place, loses context, or returns an error instead of the intended record or view.

Stale cached UI

The interface shows an older status or record after data changed, making a completed action or current state look wrong.

Empty state confusion

A page is empty but does not explain whether data is absent, filtered out, unavailable, or waiting for the next setup step.

Validation draft loss

A form rejects submission and the page drops some or all entered values, forcing users to reconstruct work.

Responsive overflow

A page or control extends beyond a narrow viewport, hides content, or makes a required action difficult to use.

Inconsistent status labels

The same state is named or colored differently across pages, making records hard to compare and actions easy to misread.