agency-test-automation-engineer

Builds deterministic Playwright and Cypress end-to-end test suites with CI integration.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-test-automation-engineer-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-test-automation-engineer
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/testing-test-automation-engineer
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-test-automation-engineer-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? End-to-end test suites often become flaky, slow, and untrusted, forcing teams to retry builds until green and ignore real failures. This Skill engineers deterministic browser tests that own their data, wait on conditions instead of timers, and produce debuggable failure artifacts. ## Core Features & Use Cases - Deterministic Test Authoring: Writes Playwright and Cypress tests using role-based selectors, API-driven setup, and condition-based waits with zero hard sleeps. - CI Pipeline Engineering: Configures sharded parallel execution, trace-on-retry forensics, and merge-blocking quality gates in GitHub Actions. - Flake Triage & Root-Cause Analysis: Diagnoses flaky tests by signature (timing races, shared state, animation timing) and fixes root causes rather than deleting tests. - Use Case: A team inherits a 40-minute suite at 70% pass rate. Use this Skill to rebuild it with worker-scoped auth fixtures, per-test data factories, and sharded CI, producing an 8-minute merge-blocking suite. ## Quick Start Ask the agent to write a deterministic Playwright test for your checkout flow with API-based setup and role selectors, then wire it into a sharded CI pipeline.

Frequently Asked Questions about agency-test-automation-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky Playwright tests in CI?

Flaky Playwright tests are fixed by replacing hard sleeps with condition-based waits, isolating test data per test or worker via API factories, and using role-based selectors. Pass-on-retry results signal flakes that need root-cause analysis, not more retries.

How to set up Playwright authentication without logging in every test?

Use worker-scoped fixtures that authenticate once per worker through the API and save storage state to a file. Each worker gets a unique user, so parallel runs never share state and tests skip the login UI entirely.

Playwright vs Cypress for end-to-end testing?

Playwright offers fixtures composition, multi-browser projects, and trace viewer forensics, while Cypress provides custom commands, cy.intercept network control, and session caching. Cypress's single-tab model can be limiting for multi-window flows.

Why do tests pass locally but fail in CI?

CI failures usually expose timing races hidden by faster local machines. Replace time-based waits with condition-based waits on element state, network responses, or URL changes, and audit the suite for any waitForTimeout calls.

When should I not write an end-to-end test?

Skip E2E when the behavior can be proven with a unit or API test, since browser tests are the slowest and most expensive layer. Reserve E2E for journeys where the integration itself is the risk, like checkout or signup.