Laravel provides several types of tests including unit, feature, browser (Dusk), and Pest tests. 1. Unit tests focus on isolated parts like methods or classes, are fast, and don’t involve the full framework. 2. Feature tests simulate HTTP requests to test routes, controllers, and workflows end-to-end. 3. Browser tests via Dusk automate real user interactions for JavaScript-heavy interfaces but are slower. 4. Pest tests offer a concise syntax for Laravel testing, reducing boilerplate while supporting all test types. Each serves a specific purpose, allowing developers to choose based on what they need to test effectively.

Laravel comes with a solid testing foundation out of the box, and understanding the different types of tests it supports helps you write better, more reliable test suites. The main types you’ll work with are unit tests and feature tests, but there are also others like browser tests and Pest tests if you're using Pest PHP.

Unit Tests

Unit tests are for testing small, isolated parts of your application — like individual methods or classes. They don’t involve HTTP requests or interact with the full framework stack. This makes them fast and focused.

• Good candidates for unit tests include helper functions, value objects, or business logic that doesn't depend on Laravel’s full runtime.
• In Laravel, unit tests typically extend PHPUnit\Framework\TestCase, not Tests\TestCase, which means they don’t boot the entire Laravel framework before running.
• Example: Testing a method that calculates tax based on location without touching the database or routing system.

One thing to note is that many developers skip writing pure unit tests in Laravel because most of their logic tends to be tied into the framework (like controllers or Eloquent models). But when possible, unit tests can speed up your test suite significantly.

Feature Tests

Feature tests are what most Laravel developers use day-to-day. These simulate full HTTP requests and allow you to test how different parts of your app work together — including routes, middleware, controllers, and even database interactions.

• Feature tests extend Tests\TestCase and boot the full Laravel application before running.
• You can make actual HTTP calls using methods like $this->get('/url'), $this->post('/url', $data), and chain assertions like ->assertStatus(200) or ->assertSee('text').
• You can test complex workflows like user registration, login, form validation, and authorization checks.

Here's a quick example:

$this->post('/login', [
    'email' => 'test@example.com',
    'password' => 'wrong-password'
])->assertRedirect('/');

This type of test gives you confidence that your features behave correctly from the outside-in, just like a real user would experience.

Browser Tests (Dusk)

If you need to test JavaScript-heavy pages or browser interactions, Laravel Dusk provides an expressive API for browser automation using ChromeDriver.

• Dusk tests simulate real user behavior in a browser — clicking buttons, filling forms, checking if elements appear after AJAX calls.
• These tests are slower than feature tests, so it's best to keep their number limited and focus on critical paths like payment flows or complex UI interactions.
• Setup involves installing Laravel Dusk via Composer and running php artisan dusk:install.

You might write a Dusk test to confirm that a modal pops up after clicking a button, or that a dropdown menu updates dynamically when you select something.

Pest Tests (if you're using Pest PHP)

Pest is a modern, lightweight testing framework built specifically for Laravel. It works alongside PHPUnit and offers a more concise and expressive syntax.

• Pest tests are mostly used for feature testing but can also handle unit and browser tests.
• It reduces boilerplate code by removing the need for verbose class definitions and repetitive setup.
• For example, instead of creating a class with multiple test methods, Pest lets you define tests using closures inside a simple PHP file.

A basic Pest test looks like this:

test('user can view homepage', function () {
    $this->get('/')->assertStatus(200);
});

It's gaining popularity because it improves readability and developer experience while keeping all the power of Laravel's testing tools.

So depending on what you're trying to test — whether it's a single function, a whole HTTP flow, or complex frontend behavior — Laravel has a test type that fits. Unit and feature tests cover most cases, and tools like Dusk and Pest add flexibility where needed.

The above is the detailed content of What are the different types of tests in Laravel (unit tests, feature tests)?. For more information, please follow other related articles on the PHP Chinese website!