screenleon

QA Testing Rules — Testing skill for Claude Code

Testing community

Language-agnostic QA testing rules for AI coding agents — pre-write category enumeration, structured docstrings, mutation self-checks, and explicit test-layer decisions.

How to install QA Testing Rules

This entry records only its repository, not the path inside it, so there is no exact command to give. Open screenleon/qa-testing-rules and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What QA Testing Rules does

Language-agnostic QA testing rules for AI coding agents — pre-write category enumeration, structured docstrings, mutation self-checks, and explicit test-layer decisions. Designed for @import into any project's CLAUDE.md / AGENTS.md / .cursorrules.

Alternatives in Testing

OpenAgentsControl — AI agent framework for plan-first development workflows with approval-based execution 4.8k ★
Axiom — Development Changelog — Purpose: Historical record of Axiom development milestones, TDD testing results, and architectural decisions 671 ★
Maestro Spec — Intent-driven spec precipitation — state a constraint in natural language (加一条规范：禁止用 any / 记录架构约束：服务间走 gRPC / 530 ★

README

qa-testing-rules

Language/framework-agnostic QA testing rules — a single source of truth that AI coding agents and human engineers can `@import`.

Why this exists

Without explicit guidance, LLM agents default to **happy-path-only** tests — pretty coverage numbers that catch no bugs. This repo forces three habits: (1) **enumerate test categories** before writing tests, (2) compare against an **anti-pattern catalog**, and (3) run a **mutation self-review** after writing.

Two-tier structure (important)

**Tier 1 (agent hot path, always loaded, ~3k tokens — budget enforced in CI):**

`AGENT.md` — the agent's only required entry point. Workflow + 12-category quick reference + red lines + self-checklist.

**Tier 2 (reference, read only when needed):**

File	When to read
`PRINCIPLES.md`	unsure how to judge an edge case
`TEST-STRATEGY.md`	choosing test layers, designing CI / environments / coverage / flakiness / mutation-testing policy
`TEST-CATEGORIES.md`	stuck on concrete sub-cases for a category
`GENERATIVE-TESTING.md`	boundary / negative enumeration is endless (parser, serializer, money math) — property-based, fuzzing, model-based
`ANTI-PATTERNS.md`	reviewing / saw a smell and want to confirm it is an anti-pattern
`EXAMPLES.md`	need good-vs-bad code comparisons
`LLM-TESTING.md`	the SUT calls an LLM / output is non-deterministic
`LEGACY-TESTING.md`	adding tests to untested legacy code before changing it
`TEST-ORACLES.md`	writing/reviewing AI-generated tests; changing assertions, snapshots, golden files, or expected behavior
`TEST-DESIGN.md`	selecting high-value cases from large input/configuration spaces
[`ACCESSIBILITY-TESTING.md`](./ACCESSIBILITY-TESTING.