What problem does it solve? Choosing between PHPUnit 12 and Pest 4 and configuring them correctly on a non-Laravel PHP project is error-prone, especially after PHPUnit 12 removed docblock annotations and changed test-double behavior. This Skill provides a decision matrix, migration guidance, and ready-to-use configuration templates so tests are set up correctly the first time. ## Core Features & Use Cases - Framework Decision Matrix: Compares PHPUnit 12 (class-based, enterprise baseline) versus Pest 4 (closure-based, browser/architecture/mutation testing) with honest guidance based on team and CI constraints. - PHPUnit 12 Migration Guidance: Maps removed docblock annotations (@test, @dataProvider, @covers) to PHP 8 attributes and flags breaking changes like static-only data providers and non-configurable createStub(). - Ready-to-Use Templates: Ships phpunit.xml, Pest.php setup, and test-double (stubs, mocks, fixtures, coverage) templates for immediate project scaffolding. - Use Case: You inherit a PHP 8.3 library with no tests. Use this Skill to pick Pest 4 for its expressive syntax, generate the Pest.php and phpunit.xml config, and write your first dataset-driven tests with a coverage gate in CI. ## Quick Start Ask the agent to set up a PHPUnit 12 or Pest 4 test suite with configuration and a first passing test for your non-Laravel PHP project.