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
- Use "E2E Testing Patterns" with your Muse.
- 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:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Use "E2E Testing Patterns" with your Muse. Prerequisites: the Muse app (mobile or web), a web app you can run locally or in CI, and Node.js with Playwright installed for the hands-on parts. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/e2e-testing/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Set up a Playwright E2E suite for [my app at URL or repo path]. Start with the auth flow and the [core feature] flow." 3. Ask Muse to scaffold the structure (specs by area, fixtures, page objects with data-testid locators, playwright.config.ts) and the CI job with artifacts on failure. Tip: if your suite is already flaky, ask for a flaky-test triage first: wait conditions, test isolation, and resource-starved runners cause most flakes, not the app. Safety: a skill is plain-text instructions; it runs nothing by itself. Review any test code before running it, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.