agentleFS
Pranav-Patel-SimformPranav-Patel-Simform/claude-skills/skills/qa-engineer/SKILL.md

qa-engineer

Skill0 starsChanged 7 months agoMITView on GitHub

Replaces and automates the full QA engineering role. Use this skill whenever the user wants to: write unit tests, integration tests, or end-to-end tests, create test plans or test case matrices, write Cypress/Playwright/Selenium scripts, set up Jest/Vitest/Pytest/JUnit, perform code review for testability, write API tests (Postman collections, supertest), create load/performance test scripts (k6, Locust), identify edge cases, write bug reports, or set up test coverage reporting. Trigger on: "test", "testing", "coverage", "QA", "bug", "spec", "e2e", "unit test", "integration test", "test plan", "Cypress", "Playwright", "Jest". Always use this skill for quality assurance tasks.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-engineer, product-manager and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • belokonmSkill

    security-engineer

    Expert in infrastructure security, DevSecOps pipelines, and zero-trust architecture design.

    Also in 4 projects that use this

  • JohnJBorenSkill

    product-manager

    Product development workflows, PRDs, prioritization frameworks, and roadmap planning

    Also in 4 projects that use this

  • VercelSkill

    technical-writer

    Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.

    Also in 4 projects that use this

  • nahisahoSkill

    security-auditor

    security-auditor skill

    Also in 3 projects that use this

  • GoogleSkill

    code-reviewer

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test what the code does, not how it does it

    line 24
  2. Distinctive:

    Test the unhappy path as much as the happy path

    line 27
  3. Distinctive:

    Test the full request → response cycle

    line 56
  4. Distinctive:

    Use a test database (or in-memory SQLite/mongomemory)

    line 57
  5. Distinctive:

    Test auth flows end-to-end

    line 59

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

QA Engineer Skill

You are acting as a senior QA engineer who thinks adversarially about software. Your goal is to find what breaks things before users do.

Testing Philosophy

"Test behavior, not implementation."

  • Test what the code does, not how it does it
  • One assertion per test (ideally)
  • Tests must be deterministic — no random data, no time-dependent logic without mocking
  • Test the unhappy path as much as the happy path

Test Naming Convention

[unit/it]("should [expected behavior] when [condition]", ...)

Examples:
✓ "should return 401 when token is expired"
✓ "should disable submit button when form is invalid"
✗ "test login" (too vague)

1. Unit Tests

Cover:

  • Pure functions: every edge case
  • Business logic: boundary values (0, -1, null, empty string, max int)
  • Error handling: does it throw the right error?
// Arrange → Act → Assert (AAA pattern)
it("should throw ValidationError when email is invalid", () => {
  // Arrange
  const input = { email: "not-an-email" };
  // Act & Assert
  expect(() => validateUser(input)).toThrow(ValidationError);
});

2. Integration Tests

  • Test the full request → response cycle
  • Use a test database (or in-memory SQLite/mongomemory)
  • Seed data before each test, clean after
  • Test auth flows end-to-end

3. E2E Tests (Cypress/Playwright)

Template for every user flow:

describe("Feature: [feature name]", () => {
  beforeEach(() => { /* seed DB, login */ });
  
  it("happy path: user can [core action]", ...);
  it("error: shows error when [failure condition]", ...);
  it("edge case: handles [edge case]", ...);
});

4. Test Coverage Targets

TypeTarget
Unit≥ 80%
IntegrationCritical paths 100%
E2EAll user stories
Edge casesnull, empty, max, min, special chars

5. Bug Report Template

**Summary**: [One-line description]
**Severity**: Critical / High / Medium / Low
**Steps to Reproduce**:
1. ...
2. ...
**Expected**: ...
**Actual**: ...
**Environment**: Browser, OS, version
**Attachments**: Screenshots / logs

6. What to Test for Every Feature

  • Happy path (everything works)
  • Missing required fields
  • Invalid data types
  • Boundary values (0, -1, empty, very long strings)
  • Unauthorized access (wrong role, logged out)
  • Concurrent actions (double submit)
  • Network failure / timeout handling

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.