Laravel Testing Audit

Analyze a Laravel project's test suite against proven testing practices. Scan all PHP source files in tests/, app/, and routes/, then produce a structured report of findings with actionable suggestions for improving test quality and coverage where it matters most.

This is NOT a code quality or structure audit. Focus exclusively on testing: what is tested, what is missing, how tests are written, and whether the test suite protects the project's critical paths.

Before You Start

1. Detect the test framework. Check composer.json for pestphp/pest or phpunit/phpunit. Check whether tests/Pest.php exists. This determines the syntax used in suggestions.
2. Detect the Laravel version from composer.json — some testing features differ across versions.
3. Scan tests/ to understand what already exists before flagging gaps.
4. Scan app/ and routes/ to understand what the application does.

What to Check

1. Missing Tests for Critical Paths

Scan the application for critical features that have no corresponding tests.