PHPUnit setup in Laravel

Introduction

PHPUnit helps you test your Laravel app to make sure it works correctly. It finds mistakes early so your app stays reliable.

When you want to check if your app's features work after changes.

Before releasing your app to catch bugs automatically.

When adding new features to ensure old parts still work.

To run tests automatically during development.

When fixing bugs to confirm the fix works and nothing else breaks.

Syntax

Laravel

php artisan make:test TestName

// Run tests
./vendor/bin/phpunit

// Or use artisan
php artisan test

Use php artisan make:test to create a new test file.

Run tests with php artisan test or ./vendor/bin/phpunit.

Examples

This creates a test file named UserTest.php in the tests/Feature folder.

Laravel

php artisan make:test UserTest

This command runs all tests in your Laravel app and shows results in the terminal.

Laravel

php artisan test

A simple test checking if the home page loads successfully with status 200.

Laravel

<?php

namespace Tests\Feature;

use Tests\TestCase;

class UserTest extends TestCase
{
    public function test_example()
    {
        $response = $this->get('/');
        $response->assertStatus(200);
    }
}

Sample Program

This test checks if the home page URL ('/') returns a successful HTTP status (200). Running php artisan test will show if the test passes.

Laravel

<?php

namespace Tests\Feature;

use Tests\TestCase;

class HomePageTest extends TestCase
{
    public function test_home_page_loads()
    {
        $response = $this->get('/');
        $response->assertStatus(200);
    }
}

// To run this test, use:
// php artisan test

// Expected output example:
// 
//   PASS  Tests\Feature\HomePageTest
//    test_home_page_loads
// 
//  Tests:  1 passed
//  Time:   0.12s

Important Notes

Laravel includes PHPUnit by default, so no extra installation is needed.

Test files go in the tests folder, usually Feature or Unit.

Use descriptive test method names starting with test for clarity.

Summary

PHPUnit helps test Laravel apps to catch bugs early.

Create tests with php artisan make:test and run them with php artisan test.

Write simple tests to check your app's pages and features work as expected.

Practice

1. What is the primary purpose of using PHPUnit in a Laravel project?

easy

A. To test the application and catch bugs early

B. To deploy the application to a server

C. To write database migration scripts

D. To create user interface designs

Solution

1. Step 1: Understand PHPUnit's role

   PHPUnit is a testing framework used to check if code works correctly.

2. Step 2: Connect PHPUnit to Laravel usage

   In Laravel, PHPUnit helps find bugs early by running automated tests.

3. Final Answer:

   To test the application and catch bugs early -> Option A

4. Quick Check:

   Testing = Catch bugs early [OK]

Hint: PHPUnit is for testing, not deployment or design [OK]

Common Mistakes:

• Confusing testing with deployment
• Thinking PHPUnit creates UI or migrations
• Assuming PHPUnit runs the app

2. Which command correctly creates a new test class in Laravel using Artisan?

easy

A. php artisan make:test UserTest

B. php artisan create:test UserTest

C. php artisan test:make UserTest

D. php artisan generate:test UserTest

Solution

1. Step 1: Recall Laravel Artisan test creation command

   The correct command to create a test is php artisan make:test.

2. Step 2: Match the command with options

   Only php artisan make:test UserTest uses the correct syntax: php artisan make:test UserTest.

3. Final Answer:

   php artisan make:test UserTest -> Option A

4. Quick Check:

   Make test command = make:test [OK]

Hint: Use 'make:test' to create tests with Artisan [OK]

Common Mistakes:

• Using incorrect Artisan command verbs
• Mixing test creation with test running commands
• Misspelling 'make:test'

3. Given this test method in Laravel, what will be the output when running php artisan test if the home page returns status 200?

public function test_home_page_status()
{
    $response = $this->get('/');
    $response->assertStatus(200);
}

medium

A. Test fails with status code error

B. Test passes with success message

C. Syntax error in test method

D. Test is skipped automatically

Solution

1. Step 1: Analyze the test method

   The test sends a GET request to '/' and expects HTTP status 200.

2. Step 2: Check expected vs actual response

   If the home page returns 200, the assertion assertStatus(200) passes.

3. Final Answer:

   Test passes with success message -> Option B

4. Quick Check:

   Correct status = test passes [OK]

Hint: If status matches assertStatus, test passes [OK]

Common Mistakes:

• Assuming test fails if status is 200
• Confusing assertStatus with assertSee
• Thinking test skips without reason

4. You wrote this test but it fails with an error:

public function test_example()
{
    $response = $this->get('/home');
    $response->assertStatus(200)
}

What is the likely cause?

medium

A. Test method name is invalid

B. Wrong HTTP method used in get()

C. Missing semicolon after assertStatus(200)

D. Route '/home' does not exist

Solution

1. Step 1: Check syntax in test method

   The line $response->assertStatus(200) lacks a semicolon at the end.

2. Step 2: Understand PHP syntax rules

   Missing semicolon causes a syntax error and test fails to run.

3. Final Answer:

   Missing semicolon after assertStatus(200) -> Option C

4. Quick Check:

   Semicolon missing = syntax error [OK]

Hint: Always end PHP statements with semicolon [OK]

Common Mistakes:

• Ignoring missing semicolon errors
• Assuming wrong HTTP method causes syntax error
• Thinking test method name causes syntax error

5. You want to run only tests related to user authentication in Laravel. Which command helps you run tests in the tests/Feature/AuthTest.php file only?

hard

A. php artisan test --run=AuthTest

B. php artisan make:test AuthTest

C. php artisan test --only=AuthTest

D. php artisan test --filter=AuthTest

Solution

1. Step 1: Identify how to filter tests in Laravel

   Laravel's test command supports --filter to run specific tests.

2. Step 2: Match correct syntax for filtering

   php artisan test --filter=AuthTest uses php artisan test --filter=AuthTest, which runs tests matching 'AuthTest'.

3. Final Answer:

   php artisan test --filter=AuthTest -> Option D

4. Quick Check:

   Filter option runs specific tests [OK]

Hint: Use --filter to run specific test files or methods [OK]

Common Mistakes:

• Using nonexistent options like --only or --run
• Confusing make:test with running tests
• Not specifying filter correctly