{"id":481,"date":"2025-08-28T10:33:17","date_gmt":"2025-08-28T10:33:17","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=481"},"modified":"2025-08-28T10:33:19","modified_gmt":"2025-08-28T10:33:19","slug":"testing-laravel-applications-with-phpunit","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/testing-laravel-applications-with-phpunit\/","title":{"rendered":"Testing Laravel Applications with PHPUnit"},"content":{"rendered":"\n

Testing Laravel Applications with PHPUnit<\/strong><\/h2>\n\n\n\n

Testing is essential for building reliable, maintainable Laravel applications. With PHPUnit integrated out of the box, you can write unit and feature tests that validate your business logic, HTTP flows, and database interactions. This guide walks through setup, writing your first tests, and understanding typical test outputs.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Setting Up PHPUnit in Laravel<\/strong><\/h2>\n\n\n\n

Laravel ships with PHPUnit preconfigured in composer.json<\/code> under require-dev<\/code>. Confirm the dependency and install vendor packages.<\/p>\n\n\n

\"require-dev\"<\/span>: {\n    \"phpunit\/phpunit\"<\/span>: \"^10.0\"<\/span>\n}<\/code><\/span>Code language:<\/span> JSON \/ JSON with Comments<\/span> (<\/span>json<\/span>)<\/span><\/small><\/pre>\n\n\n
This ensures PHPUnit is available to Laravel\u2019s test runner. If you\u2019re upgrading, run composer update<\/code> to get the right version for your PHP\/Laravel stack.<\/p>\n\n\n
composer install\nphp artisan test<\/span><\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
The first run should execute the default example test and report results in a readable, colored format.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Creating Your First Unit Test<\/strong><\/h2>\n\n\n\n
Use Artisan to scaffold a unit test class. Unit tests focus on small, isolated pieces of logic without the framework bootstrapping overhead.<\/p>\n\n\n
php artisan make:test<\/span> UserMathTest --unit<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
Open the generated file at tests\/Unit\/UserMathTest.php<\/code> and add a simple assertion.<\/p>\n\n\n
namespace<\/span> Tests<\/span>\\Unit<\/span>;\n\nuse<\/span> PHPUnit<\/span>\\Framework<\/span>\\TestCase<\/span>;\n\nclass<\/span> UserMathTest<\/span> extends<\/span> TestCase<\/span>\n<\/span>{\n    public<\/span> function<\/span> test_basic_math_addition<\/span>()<\/span>\n    <\/span>{\n        $this<\/span>->assertSame(4<\/span>, 2<\/span> + 2<\/span>);\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This basic test verifies your PHPUnit setup. It runs quickly and proves your environment is configured correctly.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Writing a Feature Test (HTTP + Database)<\/strong><\/h2>\n\n\n\n
Feature tests exercise full request lifecycles, including routes, controllers, middleware, and the database. Let\u2019s test a simple \u201ccreate post\u201d flow.<\/p>\n\n\n
php artisan make:test<\/span> PostCreationTest<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
Update tests\/Feature\/PostCreationTest.php<\/code> to validate the HTTP response and database changes.<\/p>\n\n\n
namespace<\/span> Tests<\/span>\\Feature<\/span>;\n\nuse<\/span> Tests<\/span>\\TestCase<\/span>;\nuse<\/span> Illuminate<\/span>\\Foundation<\/span>\\Testing<\/span>\\RefreshDatabase<\/span>;\nuse<\/span> App<\/span>\\Models<\/span>\\User<\/span>;\nuse<\/span> App<\/span>\\Models<\/span>\\Post<\/span>;\n\nclass<\/span> PostCreationTest<\/span> extends<\/span> TestCase<\/span>\n<\/span>{\n    use<\/span> RefreshDatabase<\/span>;\n\n    public<\/span> function<\/span> test_authenticated_user_can_create_post<\/span>()<\/span>\n    <\/span>{\n        $user = User::factory()->create();\n\n        $response = $this<\/span>->actingAs($user)\n            ->post('\/posts'<\/span>, [\n                'title'<\/span> => 'My First Post'<\/span>,\n                'body'<\/span>  => 'Hello world!'<\/span>,\n            ]);\n\n        $response->assertRedirect('\/posts'<\/span>);\n        $this<\/span>->assertDatabaseHas('posts'<\/span>, [\n            'title'<\/span> => 'My First Post'<\/span>,\n        ]);\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This test signs in a user, posts form data, expects a redirect, and verifies that the record exists. For production-grade examples of auth flows, also see How to Build Email Verification in Laravel 12 (Step by Step)<\/a> and Implementing Password Reset in Laravel 12 Without Packages<\/a>.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Running Tests and Filtering by Class\/Method<\/strong><\/h2>\n\n\n\n
Run the entire test suite, a single class, or even a single method using filters.<\/p>\n\n\n
# run all tests<\/span>\nphp artisan test<\/span>\n\n# run a specific class<\/span>\nphp artisan test<\/span> --filter=PostCreationTest\n\n# run a specific test method<\/span>\nphp artisan test<\/span> --filter=PostCreationTest::test_authenticated_user_can_create_post<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
Filtering speeds up the feedback loop while you iterate on a failing scenario.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Sample Output from php artisan test<\/code><\/strong><\/h2>\n\n\n\n
Here\u2019s a typical output when all tests pass. Your numbers will differ based on how many tests\/asser\u00adtions you have.<\/p>\n\n\n
PHPUnit 10.*\/Laravel Test Runner\n\n   PASS  Tests\\Unit\\UserMathTest\n  \u2713 test_basic_math_addition\n\n   PASS  Tests\\Feature\\PostCreationTest\n  \u2713 test_authenticated_user_can_create_post\n\n  Tests:  2 passed\n  Assertions: 3\n  Time: 0.58s<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
When a test fails, the output highlights the failing assertion, expected vs actual values, and a snippet of the stack trace to help you navigate the source quickly.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Seeding, Factories, and Faster Test Data<\/strong><\/h2>\n\n\n\n
Use model factories and seeders to generate realistic test data quickly. This keeps tests readable and reduces duplication across scenarios.<\/p>\n\n\n
\/\/ Example: creating many posts for a listing test<\/span>\n$posts = \\App\\Models\\Post::factory()->count(10<\/span>)->create();<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Factories keep your tests expressive and focused on behavior. For deeper coverage, see Using Laravel Factories and Seeders for Test Data<\/a>.<\/p>\n\n\n\n
<\/div>\n\n\n\n
UI-Related Testing Tips<\/strong><\/h2>\n\n\n\n
For Blade-driven UIs, test the rendered output and important view data. Focus on what matters (HTTP status, redirected routes, session flashes, and presence of key strings).<\/p>\n\n\n
public<\/span> function<\/span> test_posts_index_renders_titles<\/span>()<\/span>\n<\/span>{\n    $posts = \\App\\Models\\Post::factory()->count(2<\/span>)->create([\n        'title'<\/span> => 'Visible In List'<\/span>\n    ]);\n\n    $response = $this<\/span>->get('\/posts'<\/span>);\n\n    $response->assertOk()\n        ->assertSee('Visible In List'<\/span>);\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/div>\n\n\n\n
Wrapping Up<\/strong><\/h2>\n\n\n\n
You learned how to confirm your PHPUnit setup, create unit and feature tests, filter test runs, read outputs, and leverage factories for fast data setup. A disciplined testing habit yields fewer regressions and more confidence when refactoring.<\/p>\n\n\n\n
What\u2019s Next<\/strong><\/h2>\n\n\n\n
Continue strengthening your test suite with these related guides:<\/p>\n\n\n\n
This checks that the index page renders properly and contains expected text. For browser-level interactions (clicks, JS), consider How to Use Laravel Dusk for Browser Testing<\/a>.<\/p>\n\n\n\n