Penpot QA · Coverage vs Bugs

Decision matrix

Each point is a functional area (Qase root suite). X axis: automated tests · Y axis: reported bugs. Dashed lines = medians.

cover reinforce review pruning maintain ok / low risk

Bug trend

Created vs closed per month. Most of the history enters the project from 2026-04 onward.

created closed

Bugs vs automated tests by area

Top bar: bugs (GitHub project, excluding Rejected) · bottom bar: automated tests (Qase regression).

Detail and decision by area

Click a bug, test, or feature count to open the underlying GitHub issues / Qase cases.

Area (Qase root suite)	Inventory	Reg. tests	Automated	% inv. auto	Bugs	Open	Features	Bugs/test	Decision

Test reliability — flaky & failing

Automated regression tests that flaked or failed in CI at least once in the last days, tallied per Qase ID from the daily run's results.json (see flaky-tally.ts). Click a column to sort — defaults to most failed first, ties broken by most flaky. This is frequency, not a rate (no denominator of clean runs). "Last seen" links to that run's report where available — raw reports expire off S3 after ~10 days, so older links may 404.

Test	Area	Flaky	Failed	Total	Last seen