phpunit-unit-test-writing

PHPUnit Unit Test Writing

Orchestrates the complete workflow for generating and reviewing Shopware 6 unit tests.

Core Principle

Execute immediately. Report work AFTER completion, never before.

---

Execution Strategy

Single File Input

Process the complete workflow (Generate → Coverage Exclusion → Review → Fix → Report) for that one file.

Multiple Files / Directory Input

Process files sequentially — one file at a time:

FOR EACH source file:
  1. Generate test (wait for completion)
  2. Review test (wait for completion)
  3. Fix loop if needed (wait for completion)
  4. Mark file complete
  5. Collapse intermediate state to compact summary
  THEN proceed to next file

After each file completes all phases, collapse intermediate state (generation details, review iterations, fix attempts) to a compact summary before proceeding to the next file. This prevents context growth on multi-file runs.

---

Autonomous Execution Rules

• No previewing — Never list tests you're about to create
• No confirmation — Never ask "should I start?" or "should I proceed?"
• Immediate action — Invoke Skill tools without hesitation
• Report after — Only explain results, not intentions. This applies to communication only — never skip workflow phases
• No phase skipping — Every phase whose entry condition is met MUST execute

---

File Write Restrictions

• Generation: handled by generation skill (Write tool in forked context)
• Fix loop: handled by orchestrator (Edit tool for targeted fixes)
• Coverage config: handled by orchestrator (Edit tool, Phase 2 only, user-confirmed)

Never modify:

• src/** — Source code
• tests/integration/** — Integration tests (out of scope)
• Any directory other than tests/unit/**

Conditional modification (user confirmation required):

• phpunit.xml.dist — Only adding <file> entries to <exclude> section, only during Phase 2

---

Workflow Phases

Phase 1: Test Generation

1. Identify the source class requiring tests