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.

72

Quality

90%

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

82%Weight 40%Scale 1-5

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

A well-structured, highly actionable overview with copy-paste commands, a repo-keyed decision table, and explicit first-run validation. The conceptual intro and quoted passages add some length, and the deeper references point to sibling skills rather than local bundle files.

Suggestions

Tighten the 'What web E2E testing is' intro — the unit-vs-integration-vs-E2E distinction is largely known to Claude; keep the practitioner budget and the flakiness rationale, trim the rest.

Add a brief validation checkpoint to the cloud-grid section (e.g. 'confirm one remote run goes green before scaling the matrix') to match the first-run path's rigor.

Clarify in 'Going deeper' whether the named components (playwright-testing, cypress-testing, etc.) are sibling skills in the same bundle or external references, so navigation is unambiguous.

DimensionReasoningScore

Conciseness

Mostly efficient, leaning on tables, code blocks, and reference-style links, with practitioner knowledge earning its place; the conceptual 'What web E2E testing is' intro and several quoted-doc passages could be trimmed slightly.

4 / 5

Actionability

Fully executable guidance throughout — repo-detection grep/ls commands, scaffold and run commands per tool, and a copy-paste-ready Playwright spec example covering the common first case.

5 / 5

Workflow Clarity

Clear sequence for the default path (read repo → take first matching row → scaffold → run example → verify → write spec) with an explicit 'Success looks like' validation checkpoint; later sections (grids, traps) are more list-like and lack comparable checkpoints.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled, one-level-deep 'Going deeper' table pointing to sibling skills; no nested references. The deeper targets are sibling skills rather than bundled files in this skill's directory, a minor organization note.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 strong, third-person description that concretely states what the skill teaches and gives three explicit use-when triggers. Minor room to add user-natural phrasings like 'set up E2E tests' or framework-comparison queries.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — what E2E covers vs unit/integration, a framework decision table keyed on repo files, install/first-run commands per tool, and named flakiness traps (fixed sleeps, CSS/XPath selectors, shared state) — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (teaches E2E coverage, framework selection, install commands, flakiness traps) and 'when' (a 'Use when...' clause with three concrete trigger conditions).

5 / 5

Trigger Term Quality

Strong natural triggers ('no E2E coverage yet', 'picking or replacing an E2E framework', 'first browser test needs to go green') with synonyms, but a few phrasings a user might actually say (e.g. 'set up E2E tests', 'compare Playwright and Cypress') are not present.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (web E2E testing and framework selection) with named tools and specific trigger conditions, making it unlikely to fire for unit-testing or non-web skills.

5 / 5

Total

19

/

20

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