CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/web-e2e-overview

Teaches web end-to-end testing from first principles: what browser-driven E2E covers and how it differs from unit and integration tests, a decision table for choosing between Playwright, Cypress, Selenium WebDriver, WebdriverIO, Puppeteer, TestCafe and the BrowserStack / Sauce Labs / LambdaTest cloud grids based on files already present in the repo, install and first-run commands for each, and the flakiness traps (fixed sleeps, CSS and XPath selectors, state shared between tests) that sink new suites. Use when a web application has no E2E coverage yet, when picking or replacing an E2E framework, or when a first browser test needs to go green end to end.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable overview that gives a concrete decision procedure, runnable commands, and the specific pitfalls that matter, while deferring per-tool depth to separate component skills. Its only real weakness is length, which it mostly justifies with sourced, non-obvious content.

DimensionReasoningScore

Conciseness

The body is dense but nearly every token earns its place: it teaches non-obvious distinctions (framework vs automation library, E2E vs unit/integration) and quotes primary sources rather than re-explaining basics Claude already knows. It borders on long, so a 2 is defensible, but the elaboration is substantive not padded.

3 / 3

Actionability

Provides executable bash discovery commands, copy-paste install/first-run commands for every tool, and a runnable Playwright spec with real role-based locators and retrying assertions.

3 / 3

Workflow Clarity

Clear sequence — read the repo first, take the first matching table row, scaffold and run, then watch the four traps — with an explicit tie-break rule and a 'Success looks like' checkpoint. No destructive/batch operation is present, so the missing validate-retry loop does not cap the score.

3 / 3

Progressive Disclosure

A focused overview with a clearly signaled, one-level-deep 'Going deeper' table pointing to dedicated per-tool component skills; no local bundle files exist, and inline references are all external doc URLs, so navigation is clean.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, specific description that names concrete capabilities, supplies natural-language triggers, and explicitly marks when to use it. It is somewhat long but earns its length with actionable specificity rather than fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — a decision table for choosing among seven frameworks based on repo files, install/first-run commands per tool, and the specific flakiness traps (fixed sleeps, CSS/XPath selectors, shared state).

3 / 3

Completeness

Explicitly answers what it does in the first clause and follows with an explicit 'Use when' clause giving three concrete trigger scenarios.

3 / 3

Trigger Term Quality

Natural triggers users would say appear verbatim — 'no E2E coverage yet', 'picking or replacing an E2E framework', 'a first browser test needs to go green end to end'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (web E2E greenfield/framework selection and first green test) with triggers unlikely to fire for unit/integration or non-web testing skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents