php-test-writer

Automate PHP test writing by using a skill that generates PHPUnit tests following your project's conventions, including proper file structure, factory usage, naming prefixes, and multitenancy awareness. This reduces manual test creation and ensures consistent adherence to Laravel best practices.

Structure Laravel tests by mirroring your app/ directory in tests/, using the test_ prefix for methods, following the Arrange-Act-Assert pattern, leveraging factories instead of direct model manipulation, and routing DataObject interactions through services. This maintains architectural integrity and prevents multitenancy data isolation issues.

Handle multitenancy in Laravel tests by enforcing ->recycle($customer) usage within your test setup to ensure proper data isolation between tenants. This prevents common pitfalls where tests leak data across customer boundaries or fail to respect tenant boundaries in assertions.

Yes, you can automate test generation that enforces project-specific conventions like test_ naming, factory usage, service-driven interactions, and PHPUnit best practices. This ensures all generated tests comply with your project's standards without manual refactoring or reviews.

No, you can automate test writing for Laravel features using a convention-driven approach that generates comprehensive feature and unit tests following PHPUnit and Laravel standards. This eliminates repetitive manual test creation while maintaining code quality and architectural patterns.

Tests that bypass services and directly manipulate models break architectural integrity and make multitenancy enforcement difficult. The skill ensures all DataObject and ObjectDefinition interactions route through their services, preventing these architectural violations and maintaining consistent data handling.