e2e-test
e2e-test automates creation of spec-traceable end-to-end tests using your project's configured framework, with every test linked to a TC code and structured via Page Object Model. It handles test generation from recordings, specs, or UI changes while enforcing semantic selectors and self-sufficient test data to keep tests resilient to future changes.
e2e-test generates maintainable end-to-end tests from specs or recordings with TC code traceability and Page Object Model structure.
AI-generated summary based on this skill's SKILL.md
Install
duc01226/EasyPlatform/e2e-test · repository language: C#
git clone https://github.com/duc01226/EasyPlatform
cp -r EasyPlatform/.agents/skills/e2e-test ~/.claude/skills/e2e-testnpx skillfed install duc01226/EasyPlatform/e2e-testFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I write end-to-end tests with e2e-test?
e2e-test generates maintainable end-to-end tests automatically from your project's configured framework (Playwright, Cypress, or Selenium). Each test is linked to a TC code for traceability and structured using the Page Object Model pattern with semantic selectors. You can generate tests from recordings, feature specs, or UI changes—e2e-test detects your framework and applies project-specific conventions to ensure consistency.
Can e2e-test generate tests from feature specs or recordings?
Yes. e2e-test automates test generation from both feature specifications and browser recordings. When you provide specs or recordings, e2e-test creates spec-traceable tests with TC code annotations and self-sufficient test data setup. This approach keeps your tests resilient to future UI changes while maintaining clear links back to your original requirements.
How does e2e-test handle page object model testing pattern?
e2e-test implements the Page Object Model pattern by organizing tests with semantic selectors and centralized test data. This structure separates test logic from UI details, making tests easier to maintain. When UI elements change, you update selectors in one place rather than across multiple tests, reducing maintenance overhead.
What should I do to update e2e tests after UI changes?
e2e-test simplifies test maintenance after UI changes by using semantic selectors and the Page Object Model pattern. When your UI updates, e2e-test helps you identify affected tests and regenerate or patch them while preserving TC code traceability. The centralized selector strategy means changes propagate efficiently across your test suite.
How does e2e-test detect my project's E2E framework?
e2e-test automatically detects whether your project uses Playwright, Cypress, or Selenium WebDriver and applies the appropriate conventions and syntax. This detection ensures generated tests follow your framework's best practices and integrate seamlessly with your existing test infrastructure and CI/CD pipelines.
What makes e2e-test tests resilient and maintainable?
e2e-test ensures resilience through semantic selectors, self-sufficient test data setup, and TC code traceability. Tests are structured via Page Object Model to isolate UI details from test logic. This combination reduces brittleness, simplifies debugging when tests fail, and keeps your test suite aligned with specifications even as your application evolves.
SKILL.md
rendered from the published skill — quoted content, verbatim
> Codex compatibility note:
>
> - Invoke repository skills with $skill-name in Codex; this mirrored copy rewrites legacy Claude /skill-name references.
> - Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.
> - User-question prompts mean to ask the user directly in Codex.
> - Ignore Claude-specific mode-switch instructions when they appear.
> - Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.
> - Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
> - Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.
> - For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.
> - If a required step/tool cannot run in this environment, stop and ask
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agents/skills/e2e-test/SKILL.md