Skip to content

Skill

QA

gstack

Systematically tests a running web app for bugs AND fixes each one it finds in the same pass, so you end up with a working product rather than a defect list. The fixing is the point - unlike a report-only QA sweep, a plain headless browser for eyeballing the site, or a performance-regression check.

Situations it fits

Go through my site, find what is broken, and fix it - I want the problems resolved, not just reported.
QA. All four touch a running web app, which is the trap. qa systematically tests the app AND fixes each bug it finds, so you end up with a working product. By contrast qa-only tests the app and REPORTS the defects without changing any code, leaving fixes to the team; browse just drives a headless browser to open the site and see what renders - a tool for eyeballing, not a bug sweep; benchmark measures speed and flags performance regressions against a baseline, not functional bugs.
You want your web app systematically tested for bugs, and you want the bugs that turn up actually fixed in the same pass - not just a list handed back.
QA. All four touch a running web app, which is the trap. qa systematically tests the app AND fixes each bug it finds, so you end up with a working product. By contrast qa-only tests the app and REPORTS the defects without changing any code, leaving fixes to the team; browse just drives a headless browser to open the site and see what renders - a tool for eyeballing, not a bug sweep; benchmark measures speed and flags performance regressions against a baseline, not functional bugs.

3 scenarios in the bank answer to QA. The rest are in the game.

Skills it gets confused with

These share a family with QA, which is another way of saying they are the ones you might reach for by mistake.

Knowing what QA does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

QA is part of garrytan/gstack. Licence: MIT. The description above was written for this game, not taken from the skill.