E2E Testing Patterns
Stable Playwright suites: Page Object Model, CI integration, artifact management, and flaky-test strategies.
- What
- Stable Playwright suites: Page Object Model, CI integration, artifact management, and flaky-test strategies.
- Cost
- Free
- Needs
- none. No account, no API key, no payment — this skill is a single guidance file.
- Level
- Beginner
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: comprehensive Playwright patterns for building stable, fast, and maintainable end-to-end test suites. Covers test file organization (grouping specs by auth, features, and API, with shared fixtures), the Page Object Model with locator-based page classes and data-testid selectors instead of brittle CSS, Playwright configuration, CI/CD integration, artifact management (traces, screenshots, videos on failure), and above all the strategies that kill flaky tests: proper wait conditions, networkidle discipline, and test isolation. Written as ready-to-adapt TypeScript, so an agent can scaffold a suite or refactor an unstable one directly. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: Playwright and Node.js focused; you need a running app to test against, and the flaky-test fixes assume you control the test environment (CI runners with enough resources). Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
E2E Testing Patterns is a free Muse skill with comprehensive Playwright patterns for building stable, fast and maintainable end-to-end test suites. It covers test file organization by auth, features and API with shared fixtures, the Page Object Model with locator-based page classes and data-testid selectors instead of brittle CSS, Playwright configuration, CI integration, artifact management and flaky-test strategies.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none. No account, no API key, no payment — this skill is a single guidance file. Install "E2E Testing Patterns" for me. It gives my agent Playwright end-to-end testing patterns: test organization, the Page Object Model, configuration, CI/CD integration, artifact management and strategies for flaky tests. Once it is installed, I use it by asking my agent to write Playwright tests or fix a flaky E2E run for one of my apps. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/e2e-testing/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder and look inside. It is the only file this skill needs. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprint below. I want you to compute the SHA-256 of the downloaded file and compare: - SKILL.md: SHA-256 b0e00e7e17cb259101139900816c5528aed18dd10bcf5f9cb42cfc35baf8a755 If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none, this file is guidance text with Playwright code examples) - every shell command it runs (expected: none) - every place credentials, API keys or personal data are read, stored or sent (expected: none) - any obfuscated or encoded code (expected: none, plain markdown guidance) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "e2e-testing". 6. Verify with no network calls: frontmatter valid, skill name is e2e-testing, and the file is in place. 7. Report what was installed, where, and what I still need to do myself. Nothing else is required: to use the skill afterwards, I point my agent at one of my apps and ask it to write or fix Playwright tests. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.