Webapp Testing
- Web
Drive a running web app with a real browser to check it works: click through a flow, grab a screenshot, read the console when it breaks.
A situation it fits
Before you merge, you want to click through signup, checkout and logout on the running app and capture a screenshot of each step.
2 scenarios in the bank answer to Webapp Testing. The rest are in the game.
Skills it gets confused with
These share a family with Webapp Testing, which is another way of saying they are the ones you might reach for by mistake.
- Frontend DesignDeciding how a UI should look and feel before you build it: typography, colour, hierarchy, and escaping the default templated appearance.
- responsive-design (wshobson)Make one layout work across screen sizes — fluid grids, breakpoints, and sensible touch targets — so a page reads well on phone, tablet, and desktop without a separate mobile site.
- Theme FactoryPut a consistent look on something already built: pick or generate a colour-and-font theme and apply it across slides, docs, or a page.
- Web Artifacts BuilderAmbitious claude.ai artifacts with many moving parts: React, Tailwind, component libraries, real state and routing rather than a single static page.
Knowing what Webapp Testing does is the easy half. Telling it apart from the others under time pressure is the game.
Today's sessionWebapp Testing is part of anthropics/skills. Licence: Apache-2.0. The description above was written for this game, not taken from the skill.