Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →langgenius/e2e-cucumber-playwright
Use when writing, changing, or reviewing Cucumber and Playwright tests under `e2e/`, including feature files, step definitions, support code, scenario tags, locators, and assertions.
Passed 22 of 22 test cases with the skill, and 13 of 22 without it.
and 9 more in the full report
9 fixed13 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
An engineer is struggling with flaky element waiting logic and auto-waiting assertions in Playwright. Which reference document should they consult for waiting and isolation guidelines?
| Checked | Without skill | With skill |
|---|---|---|
| Routes locator and waiting decisions to references/playwright-best-practices.md. | Missed | Passed |
The instructions your model reads when the skill loads.
e2e/AGENTS.md owns the suite architecture, lifecycle, commands, tags, generated-client boundaries, fixtures, and cleanup contracts. Read the nearest feature-scoped AGENTS.md when one exists. This skill adds no parallel package policy.
Cucumber owns scenario and hook execution and reporting. Playwright provides browser automation, contexts, pages, locators, actions, assertions, request, and tracing APIs; protocol exceptions remain with the package-defined owner. Their timeout domains remain separate, and importing from @playwright/test does not make Playwright Test runner configuration, fixtures, or retries applicable to this suite.
Read only the bundled reference required by the change:
references/playwright-best-practices.mdreferences/cucumber-best-practices.mdCheck current official Playwright or Cucumber documentation before introducing a framework pattern that local code and references do not already establish.
e2e/AGENTS.md; broaden only for shared hooks, tags, or support changes.For review requests, lead with reproducible correctness failures, flake sources, or demonstrated architecture drift. Report the behavior verified and any external-runtime, browser, or environment gap.
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.