agentleFS
sametcelikbicaksametcelikbicak/opencode-team/skills/team-qa/SKILL.md

team-qa

Skill69 starsChanged 19 days agoMITView on GitHub

Test strategy and quality assurance methodology. Acceptance criterion -> test conversion, edge cases, e2e coverage. The playbook of the qa role.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 7

    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:

    Every acceptance criterion in the backlog must have a test.

    line 16
  2. Distinctive:

    If there is no test that meets a criterion, that criterion is untested.

    line 22
  3. Distinctive:

    Do not write e2e for everything.

    line 32
  4. Distinctive:

    Do not write tests that look inside the application and verify it (if what is mocked does not represent reality, the test is useless)

    line 67
  5. Distinctive:

    If it depends on time or randomness, fix it

    line 69
  6. Distinctive:

    Do not fix a finding before writing the test.

    line 77
  7. Distinctive:

    Do not show a criterion you could not test as "passed".

    line 92

“Common” is measured: kept by at least 6 in 10 of the 11 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

Quality Assurance

What a test is

A test is the verification of an acceptance criterion. Not a test that shows the code runs, but a test that shows the behavior is correct.

The purpose of writing tests is code reliability, not coverage percentage.

1. Acceptance criterion -> test

Every acceptance criterion in the backlog must have a test. Build a mapping table:

CriterionTestTypeStatus
"No invoices" is shown on an empty listrenders_empty_state_when_no_invoicesunit✅

If there is no test that meets a criterion, that criterion is untested. Not "passed".

2. The test pyramid

TypeWhat it testsRatioSpeed
UnitBusiness logic, edge cases70%ms
IntegrationDB, API, file system20%s
e2eThe user journey10%s-min

Do not write e2e for everything. e2e is fragile and slow; use it only for the main journeys that bring in money.

3. Mandatory edge cases

For every endpoint and every form:

CaseExpected
Empty input400 + a meaningful error, not 500
Oversized input413 or a controlled error
Corrupt data (invalid JSON, broken encoding)400, no crash
Unauthorized access403 + no resource leakage
Resource not found404, without leaking another user's data
The same request twiceNo effect (idempotent, or no duplicate record)
Two concurrent requestsNo data corruption (race condition)
Database connection droppedNot 5xx, a proper error body

4. Test quality

Bad test — does not verify the application:

def test_invoice():
    assert invoice is not None

Good test — verifies the behavior:

def test_parse_invoice_returns_none_for_missing_total():
    result = parse_invoice("Invoice No: 123\nDate: 2026-01-01")
    assert result["total"] is None

Rules:

  • The test name should tell the behavior
  • Each test verifies one behavior
  • Do not write tests that look inside the application and verify it (if what is mocked does not represent reality, the test is useless)
  • Tests should be independent of each other, order should not matter
  • If it depends on time or randomness, fix it

5. Finding-fix loop

Finding -> Write the test (FIRST) -> See the test fail -> Fix the code -> Test passes -> Refactor

Do not fix a finding before writing the test. If the test is written afterwards, it does not verify the fix.

6. The trap of weakening a test

Deleting or loosening an assertion to make a test pass is not a fix. Do not do any of these:

  • assert x == 5 → assert x is not None
  • Adding pytest.skip / test.skip
  • Commenting out a line
  • Increasing the timeout (it hides race conditions)

7. Reporting

CriterionTestResult

Do not show a criterion you could not test as "passed". Write "not testable + rationale".

Output format

Markdown: Scope mapping table / Actual test run output / Bugs found and fixed / Not tested + rationale / Remaining risks.

In the user's language (Turkish or English).

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.