pest-testing

To write Pest tests for Laravel, use `test()` or `it()` syntax with Laravel-friendly patterns. This covers feature, unit, browser, smoke, and architecture testing scenarios while maintaining project conventions and appropriate assertions.

Yes, you can convert PHPUnit tests to Pest syntax. This Skill refactors existing tests into Pest style, repairs failing tests, and updates assertions after code changes to keep your test suite consistent and fast.

Yes, Pest Laravel testing supports datasets and mocking. You can implement advanced coverage including feature tests, unit tests, browser tests, smoke tests, datasets, mocking, and architecture checks within your testing workflow.

The best way to fix failing Pest tests after a Laravel feature changes is to refactor the affected tests, align conventions with the existing suite, use RefreshDatabase when needed, and run the smallest useful test set before finishing.

Yes, Pest 4 syntax is required for creating and refining Laravel tests. This ensures proper use of Laravel test conventions, appropriate assertions, RefreshDatabase usage when needed, and practical test execution guidance across all testing scenarios.

TDD workflow integrates with Pest testing in Laravel by creating new tests using `test()` or `it()` patterns, supporting failing test repair, refactoring, and maintaining alignment with existing suite conventions throughout the development process.