agency-test-automation-engineer

Build and maintain end-to-end test automation suites with Playwright and Cypress.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common failure points in end-to-end testing, specifically flaky tests, slow CI pipelines, and brittle selectors that break during UI refactors.

Core Features & Use Cases

  • Deterministic Test Design: Implements condition-based waits and API-driven data seeding to eliminate hard sleeps and race conditions.
  • Resilient Selector Strategy: Prioritizes user-facing roles and labels to ensure tests survive design changes.
  • CI/CD Optimization: Configures sharded parallel execution and trace-on-retry policies to ensure fast, debuggable test runs.

Quick Start

Ask the test automation engineer to review your current Playwright test suite and refactor any hard-coded sleeps into condition-based assertions.

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 E2E tests in Playwright?

To fix flaky E2E tests in Playwright, replace hard-coded sleeps with condition-based assertions and implement API-driven data seeding to eliminate race conditions. This approach ensures deterministic test execution by verifying application state dynamically.

What is the best way to prevent UI refactors from breaking Cypress selectors?

The best way to prevent UI refactors from breaking Cypress selectors is to prioritize user-facing roles and labels over brittle CSS selectors. This resilient selector strategy ensures tests survive design changes by targeting elements based on user interaction attributes.

How do I optimize E2E test execution for fast CI pipelines?

To optimize E2E test execution for fast CI pipelines, configure sharded parallel execution and trace-on-retry policies. This configuration accelerates test runs while providing debuggable artifacts for failed attempts, ensuring quick and reliable feedback.

Does CI-integrated test automation support failure forensics?

Yes, CI-integrated test automation supports failure forensics by enabling trace-on-retry policies during execution. This captures detailed debugging information for failed runs, allowing developers to analyze test failures directly within their CI/CD workflow.

Why does non-deterministic test execution break my test pyramid principles?

Non-deterministic test execution breaks test pyramid principles by introducing unpredictable failures that undermine the reliability of your end-to-end suite. Enforcing a zero-tolerance policy for flakiness through deterministic data management ensures stable, trustworthy tests.