Apply battle-tested strategies for unit, integration, and E2E testing in production SaaS applications. TRIGGER this skill automatically when the user mentions: writing tests, Jest, Vitest, Playwright, Cypress, test coverage, unit tests, integration tests, E2E tests, mocking, test setup, "how do I test this", TDD, testing hooks or components, testing API routes, CI test runs, or any quality assurance topic. Also trigger when new features are added without tests or when existing tests are failing unexpectedly.
Produce proportionate automated evidence for software behavior. Use when writing or selecting tests, checking a regression or requirement, investigating a test failure, or assessing whether passing tests support a claim. Compose with implementation, debugging, browser QA, and code review as needed; do not take over their workflows or require tests for every trivial reversible edit.
Testing strategy, coverage analysis, and quality assurance. Use when: (1) Planning test strategy for a story, (2) Analyzing test coverage, (3) Reviewing test quality in PRs, (4) Creating mocks for integrations, (5) Defining testing standards. Referenced by developer-analysis (test strategy in design) and git-workflow (PR review test verification).
How to test in this repo — the verification loop, the four unit-test archetypes, MSW mock handlers, and Playwright e2e. Use when writing or fixing any test, adding a mock endpoint, or deciding whether a change is adequately covered.
How to test a full-stack app to a shipping bar, distilled from a real recruiter-led SaaS. Covers the test layers (unit, integration, contract, end-to-end, smoke, regression, security, performance, accessibility), what to run per change versus per release, the cross-viewport visual discipline (mobile, tablet, desktop, wide), the "verify for real" principle that a passing type-check is not a passing feature, hermetic stubbed e2e, tenant-isolation as a standing regression gate, and the file-upload and authorization security checks that keep a multi-tenant app safe. Load when writing tests, setting up a test harness, deciding what to verify before a commit, or reviewing whether a change is actually safe to ship. Fetch current framework docs with Context7 rather than from memory.
Use when writing, modifying, running, or reviewing tests for the project. Covers what to test, what not to test, structure, naming, fixtures, coverage targets, and the rule that tests are written against behaviour — never modified to paper over broken code.
Test strategy, audit and writing - decides what is worth testing and at which level, audits an existing suite for tests that can't fail, flakiness and gaps in risky behaviour, or writes missing unit, integration and E2E tests that follow the project's conventions. Stack-agnostic.
Test strategy and patterns — what to test, how to structure tests, mocking rules, and flaky-test prevention. Use when writing tests, setting up a test suite, or deciding how to verify code works.
Deep reference for the Kibana Functional Test Runner (FTR). Use when reading, analyzing, debugging, or reviewing FTR tests, including config anatomy, services, page objects, loadTestFile patterns, data loading, tags, CI wiring, and common FTR idioms.
21k5mo agoReviewMountCreate a free account to mount
Generate hybrid cloud tests for the Sentry codebase. Use when asked to "generate HC test", "create hybrid cloud test", "write HC test", "add HC test", "write RPC test", "test RPC service", "silo test", "cross-silo test", "outbox test", "API gateway test", or "endpoint silo test". Covers RPC service tests, API gateway tests, outbox pattern tests, and API endpoint tests with silo decorators.
No other project uses it yet
46k5mo agoReviewMountCreate a free account to mount
ABP testing patterns - integration tests over unit tests, GetRequiredService, IDataSeedContributor, Shouldly assertions, AddAlwaysAllowAuthorization, NSubstitute mocking, WithUnitOfWorkAsync. Use when writing or reviewing tests for application services, domain services, or repositories in ABP projects.
14k8mo agoReviewMountCreate a free account to mount
Run and write tests in the CAS Gradle monorepo: testcas.sh categories, JUnit tags, single-module test tasks, fast compile checks, how tests stay correct under JUnit parallel execution (shared registries, ports, pac4j clients, negative assertions), test authentications and principal attributes, and ticket-granting cookies in MockMvc tests. Use when running tests, choosing a test category, writing or fixing a *Tests.java class, or chasing a flaky test.
11k10d agoReviewMountCreate a free account to mount
Interactive testing of Podman Desktop UI using the electron-test MCP server. Supports both production (installed app) and development (pnpm watch) modes. Use for manually testing UI workflows, debugging UI issues, exploring features, or quick acceptance testing.
2 projects use a version of this
8.1k8d agoReviewMountCreate a free account to mount
Test an OpenResearch change the way its user will find the problems, and bring evidence a reviewer can see. Covers starting from the right state, driving the real flow from its entry point, real agents and backends, states, themes, sizes, languages and failure cases, the desktop webviews on macOS, Windows and Linux, screenshots and video and checking each frame. Use before calling any change a user can see done, before filing or updating a pull request, when asked to test, verify, screenshot, record or QA, and whenever a user reports a bug that "the tests pass" on. In this repo, use it in place of any general UI testing skill, including when reviewing someone else's change.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
psubramanianReads credentialsSkill
