Menu

Individual skill

webapp-testing

0upvotes

Strategy and practice for testing web applications: test pyramid, critical user journeys, flaky-test control, and CI integration. Use when setting up or improving a web app's test suite.

skills/webapp-testing/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Webapp Testing

## Overview

Testing a web application means answering one question reliably: **can a user still do the important
things?** This skill covers the strategy layer — which tests to write, how many of each, how to keep
them fast and trustworthy — and the practice layer: testing critical journeys, controlling flakiness,
and wiring it all into CI so the suite is a gate, not a suggestion.

The goal is a suite developers trust: green means shippable, red means a real problem, and nobody
ignores it.

## When to use
Back to top