backend-test-guidelines

To structure PHPUnit tests in a 7-layer Laravel architecture, write unit tests for UseCases using mocked repositories, and feature tests for repositories and controllers to ensure proper authentication and Inertia assertions.

In Laravel unit testing, you should use mocks for repositories and avoid database interactions to keep tests isolated. Feature tests should handle database interactions and validate repository behaviors end-to-end.

To test Inertia responses in Laravel feature tests, use specific Inertia assertions within your controller tests to verify component props and status codes while ensuring proper authentication and authorization checks are passed.

The best way to ensure consistent backend test coverage is to apply standardized test strategies across Model, UseCase, and Repository layers, leveraging factories, mocks, and an AI weakness checklist to verify quality and consistency.

No, this testing guideline provides directory structure templates and concrete patterns to standardize test design across layers, requiring alignment with the 7-layer architecture to effectively utilize the provided references and checklists.