Skill

Benchmark

gstack

Detects performance regressions by measuring how fast pages and interactions run and comparing them against a baseline, so a change that made things slower is caught. It is about speed over time, not finding functional bugs, reporting them, or driving the browser to look at the page.

Situations it fits

Is the app slower than last release? You want its performance measured and any speed regressions flagged.

Benchmark. All four touch a running web app, which is the trap. benchmark measures speed and flags performance regressions against a baseline, not functional bugs. By contrast qa systematically tests the app AND fixes each bug it finds, so you end up with a working product; 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.

You want to know whether your latest changes made a key page slower than before - catch performance regressions by comparing load times against a baseline.

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

Skills it gets confused with

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

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

Today's session

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