Case study
Testing ChartIt
QA on a charting tool: testing chart creation, editing, and export, and reporting the bugs in a form the developer could act on.
Problem
ChartIt is a charting tool with a specific failure mode a general pass won't catch: you can label every control correctly and still ship a chart nobody can actually read once it's built, because the chart itself has to convey its data, not just be reachable.
Approach
I tested chart creation, editing, and export end to end, wrote up the usability issues I hit with enough detail that the developer could reproduce them without me in the room, and went back through each fix to confirm it landed.
Outcome
Contract work, June through September 2025, so I'm not the person to ask about the current state of the product. But the fixes I verified stayed fixed.