Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

e2e-implementer

Étoiles5

Forks4

Mis à jour6 mars 2026 à 11:52

Create and run E2E tests using Playwright in the `apps/e2e` module.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

davidgfolch

davidgfolch/AI-job-search

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	e2e-implementer
description	Create and run E2E tests using Playwright in the `apps/e2e` module.

E2E Implementer Instructions

Use this skill when implementing or modifying End-to-End (E2E) tests. These tests are distinct from unit/integration tests and are housed in a dedicated module.

1. Location & Structure

Module: All E2E tests MUST be located in apps/e2e.
Structure:
- specs/: Contains test files (*.spec.ts).
- pages/: Page Object Models (POM).
- utils/: Helper functions.

2. Naming Conventions

Test Files: Must end in .spec.ts (Playwright standard).
Page Objects: Must end in Page.ts (e.g., LoginPage.ts).

3. Best Practices

Page Object Model: ALWAYS use POM. Do not define selectors or logic inside specs.
Independence: Tests should not depend on each other.
Selectors: ALWAYS use IDs to locate DOM objects. Ensure target elements have unique id attributes in the source code. Avoid using text-based locators or CSS classes unless absolutely necessary.
Database: Do NOT use the production database. Use the scripts/run_e2e_tests.py script which handles isolation.

4. Architecture Verification

Ensure apps/e2e does not import internal implementations from other apps directly (unless it's a shared type/constant). It should interact via the browser.
Run commonlib/.../architecture_test.py to verify the architecture.

Usage

Preferred Method: Run python scripts/run_e2e_tests.py from the root. This will:
1. Setup a temporary isolation database.
2. Start the backend on a free port.
3. Run the tests.
Manual run: npm test inside apps/e2e (WARNING: Configured against local dev environment by default).

Plus depuis ce dépôt

même dépôt

test-implementer

davidgfolch/AI-job-search

Implement and run tests adhering to valid architecture and best practices.

2026-06-195

test-implementer

davidgfolch/AI-job-search

Implement and run tests adhering to valid architecture and best practices.

2026-06-195

version-bumper

davidgfolch/AI-job-search

Bump the version of any apps/* module following semver, including syncing dependency references and secondary version files.

2026-06-085

scrapling-implementer

davidgfolch/AI-job-search

Use this skill to implement new scrappers using the Scrapling framework (https://github.com/D4Vinci/Scrapling).

2026-06-045

test-implementer

davidgfolch/AI-job-search

Implement and run tests adhering to valid architecture and best practices.

2026-03-185

skill-builder

davidgfolch/AI-job-search

Create new skills for Claude Code. This skill automates the creation of skill directories and boilerplate SKILL.md files.

2026-03-065

name	e2e-implementer
description	Create and run E2E tests using Playwright in the `apps/e2e` module.

E2E Implementer Instructions

Use this skill when implementing or modifying End-to-End (E2E) tests. These tests are distinct from unit/integration tests and are housed in a dedicated module.

1. Location & Structure

Module: All E2E tests MUST be located in apps/e2e.
Structure:
- specs/: Contains test files (*.spec.ts).
- pages/: Page Object Models (POM).
- utils/: Helper functions.

2. Naming Conventions

Test Files: Must end in .spec.ts (Playwright standard).
Page Objects: Must end in Page.ts (e.g., LoginPage.ts).

3. Best Practices

Page Object Model: ALWAYS use POM. Do not define selectors or logic inside specs.
Independence: Tests should not depend on each other.
Selectors: ALWAYS use IDs to locate DOM objects. Ensure target elements have unique id attributes in the source code. Avoid using text-based locators or CSS classes unless absolutely necessary.
Database: Do NOT use the production database. Use the scripts/run_e2e_tests.py script which handles isolation.

4. Architecture Verification

Ensure apps/e2e does not import internal implementations from other apps directly (unless it's a shared type/constant). It should interact via the browser.
Run commonlib/.../architecture_test.py to verify the architecture.

Usage

Preferred Method: Run python scripts/run_e2e_tests.py from the root. This will:
1. Setup a temporary isolation database.
2. Start the backend on a free port.
3. Run the tests.
Manual run: npm test inside apps/e2e (WARNING: Configured against local dev environment by default).