phpunit

To structure PHPUnit tests for Laravel projects, place feature tests in the tests/Feature directory and unit tests in tests/Unit. This separation ensures feature tests bootstrap Laravel while unit tests run independently.

The best way to manage test data in Laravel PHPUnit tests is using model factories. Every new model should have a corresponding factory in database/factories, utilizing factory states to cover data variations and edge cases.

You need RefreshDatabase in Laravel feature tests whenever the test touches the database. This trait resets the database after each test, ensuring a clean state and preventing data bleeding between test runs.

PHPUnit unit tests should not use the Laravel bootstrap to ensure they run in isolation. Testing pure logic without framework overhead keeps unit tests fast and verifies that the code does not rely on Laravel's service container.

To write PHPUnit test method names for Laravel, use the test_ prefix with snake_case and declare a void return type. This standardized convention ensures clarity and consistency across your testing suite.

You should prefer assertSame over assertEquals in PHPUnit tests for strict type and value checks. Using assertSame ensures your explicit assertions match both the expected value and the exact data type.