LiorCohen/sdd / plugin/fullstack-typescript/skills/components/e2e-testing/e2e-testing-scaffolding
e2e-testing-scaffolding
VerifiedScaffolds E2E test suite structure with Playwright configuration and Testkube integration.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
SKILL.md
View on GitHub---
name: e2e-testing-scaffolding
description: Scaffolds E2E test suite structure with Playwright configuration and Testkube integration.
user-invocable: false
---
# E2E Testing Scaffolding
Scaffolds an end-to-end testing component with Playwright for browser automation and Testkube for Kubernetes-native test execution.
## Input
Invoked by the scaffolding orchestrator with:
- `component_name`: Name of the testing component
- `project_name`: Project name from settings
- `existing_components`: Currently configured components (servers, webapps)
## Directory Structure
```
components/testing/e2e/{name}/
├── src/
│ ├── fixtures/
│ │ ├── auth.fixture.ts # Authentication helpers
│ │ └── page.fixture.ts # Page object base
│ ├── pages/
│ │ └── .gitkeep # Page objects go here
│ ├── tests/
│ │ └── .gitkeep # Test files go here
│ └── helpers/
│ ├── test-data.ts # Test data management
│ └── selectors.ts # data-testid selectors
├── playwright.config.ts
├── package.json
├── tsconfig.json
└── README.md
```
## Workflow
1. Create the testing directory structure
2. Generate Playwright configuration:
- Configure browsers (chromium by default)
- Set base URL from webapp config
- Configure test timeouts and retries
3. Create fixture files for authentication and page objects
4. Generate Testkube test suite definition (if helm components exist)
5. Create README with E2E testing conventions
## Standards
Follow `e2e-testing-standards` for test structure, page object patterns, and selector conventions.
## Output
Returns a declared actions response with `register_component` action for the new E2E testing component.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |