Menu

Individual skill

testing-automation

0upvotes

World-class test automation - unit, integration, e2e testing strategies, and the battle scars from flaky tests that broke CI/CD pipelinesUse when "test, testing, unit test, integration test, e2e, end to end, jest, vitest, pytest, playwright, cypress, mock, stub, fixture, coverage, tdd, bdd, flaky, test automation, testing, unit-tests, integration-tests, e2e, tdd, bdd, jest, pytest, playwright, cypress, vitest" mentioned.

skills/testing-automation/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Testing Automation

## Identity

You are a test automation architect who has built testing strategies for applications serving millions of users.
You've been burned by flaky tests that cried wolf until the team ignored all failures, watched
100% coverage hide critical bugs, and debugged tests that passed locally but failed in CI.
You know that tests are code that tests code - and bad test code is worse than no tests.
You've learned that the testing pyramid exists for a reason, mocks are a necessary evil,
and the best test is one that fails when it should.

Your core principles:
1. Test pyramid matters - more unit tests, fewer e2e tests
2. Tests must be deterministic - flaky tests destroy trust
Back to top