Set up the testing environment using Laravel’s built-in phpunit.xml and .env.testing with SQLite in memory. 2. Write feature tests to test full HTTP interactions, using helpers like $this->post() and assertRedirect(). 3. Write unit tests for isolated classes like services, ensuring they are fast and do not depend on the database unless necessary. 4. Use Laravel factories and RefreshDatabase trait to generate and manage test data. 5. Test API endpoints with the json() method and assert JSON responses, using Sanctum for authentication if needed. 6. Follow best practices such as clear test names, one assertion per test, and consider using Pest PHP for cleaner syntax. Starting with feature tests and leveraging Laravel’s testing tools significantly improves application reliability.
Writing tests in Laravel is straightforward thanks to built-in support for PHPUnit and Laravel-specific testing helpers. Laravel encourages both feature tests (testing how parts of your app work together) and unit tests (testing individual classes or functions in isolation). Here’s how to get started and write effective tests.

? 1. Set Up Your Testing Environment
Laravel comes with a phpunit.xml
file and a tests
directory out of the box.
-
Test files go in the
tests/Feature
andtests/Unit
directories. - Use SQLite for testing — it's fast and works in-memory.
- Update your
.env.testing
file (create it if it doesn't exist) to set the DB connection:
DB_CONNECTION=sqlite DB_DATABASE=:memory:
Run tests using:

php artisan test
Or with PHPUnit directly:
./vendor/bin/phpunit
? 2. Writing Feature Tests (Recommended for Most Cases)
Feature tests check full HTTP routes and user interactions.

Example: Test a User Can Login
// tests/Feature/LoginTest.php use Illuminate\Foundation\Testing\RefreshDatabase; use Tests\TestCase; class LoginTest extends TestCase { use RefreshDatabase; public function test_user_can_login_with_correct_credentials() { $user = \App\Models\User::factory()->create([ 'email' => 'test@example.com', 'password' => bcrypt('password'), ]); $response = $this->post('/login', [ 'email' => 'test@example.com', 'password' => 'password', ]); $response->assertRedirect('/dashboard'); $this->assertAuthenticatedAs($user); } public function test_user_cannot_login_with_invalid_password() { $user = \App\Models\User::factory()->create([ 'email' => 'test@example.com', 'password' => bcrypt('password'), ]); $response = $this->post('/login', [ 'email' => 'test@example.com', 'password' => 'wrong-password', ]); $response->assertSessionHasErrors('email'); $this->assertGuest(); // User is not logged in } }
Key Helpers:
$this->get('/url')
,$this->post('/url', $data)
assertStatus(200)
,assertRedirect()
,assertSee()
assertValid()
/assertInvalid()
for form validationassertDatabaseHas('users', ['email' => '...'])
? 3. Writing Unit Tests
Unit tests focus on single classes like Jobs, Services, or Helpers.
Example: Test a Custom Service Class
// app/Services/OrderService.php class OrderService { public function getTotal($items) { return collect($items)->sum(fn($item) => $item['price'] * $item['quantity']); } } // tests/Unit/OrderServiceTest.php use App\Services\OrderService; use Tests\TestCase; class OrderServiceTest extends TestCase { public function test_calculates_total_correctly() { $service = new OrderService(); $items = [ ['price' => 10, 'quantity' => 2], ['price' => 5, 'quantity' => 4], ]; $total = $service->getTotal($items); $this->assertEquals(40, $total); } }
?? Note: Unit tests don’t use
RefreshDatabase
unless needed. They should be fast and isolated.
? 4. Using Factories and Database Testing
Laravel factories help seed test data.
use App\Models\User; use Illuminate\Foundation\Testing\RefreshDatabase; public function test_user_can_view_their_profile() { $user = User::factory()->create(); $response = $this->actingAs($user)->get('/profile'); $response->assertStatus(200); $response->assertSee($user->name); }
Use RefreshDatabase
to reset the DB after each test (migrations run once per test suite).
? 5. Testing API Endpoints
For JSON APIs, use json()
and assert JSON responses.
public function test_api_returns_user_data() { $user = User::factory()->create(); $response = $this->actingAs($user, 'api') ->json('GET', '/api/user'); $response->assertStatus(200) ->assertJson(['id' => $user->id]); }
Or if using Laravel Sanctum:
use Laravel\Sanctum\Sanctum; public function test_protected_api_route() { $user = User::factory()->create(); Sanctum::actingAs($user); $this->get('/api/dashboard')->assertOk(); }
? 6. Best Practices
- Use
RefreshDatabase
instead ofDatabaseMigrations
orDatabaseTransactions
for cleaner state. - Name tests clearly:
it_returns_403_for_unauthorized_users
instead oftestSomething()
. - Test one thing per test method.
- Use Pest PHP (optional): Laravel now supports Pest — a more elegant syntax:
// PestPHP style it('has welcome page', function () { $this->get('/')->assertStatus(200); });
Basically, just start with feature tests for your routes, use factories, and lean on Laravel’s helpers. It’s not complex — but makes a huge difference in long-term app reliability.
The above is the detailed content of How to write tests in Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three main ways to set environment variables in PHP: 1. Global configuration through php.ini; 2. Passed through a web server (such as SetEnv of Apache or fastcgi_param of Nginx); 3. Use putenv() function in PHP scripts. Among them, php.ini is suitable for global and infrequently changing configurations, web server configuration is suitable for scenarios that need to be isolated, and putenv() is suitable for temporary variables. Persistence policies include configuration files (such as php.ini or web server configuration), .env files are loaded with dotenv library, and dynamic injection of variables in CI/CD processes. Security management sensitive information should be avoided hard-coded, and it is recommended to use.en

Laravel's configuration cache improves performance by merging all configuration files into a single cache file. Enabling configuration cache in a production environment can reduce I/O operations and file parsing on each request, thereby speeding up configuration loading; 1. It should be enabled when the application is deployed, the configuration is stable and no frequent changes are required; 2. After enabling, modify the configuration, you need to re-run phpartisanconfig:cache to take effect; 3. Avoid using dynamic logic or closures that depend on runtime conditions in the configuration file; 4. When troubleshooting problems, you should first clear the cache, check the .env variables and re-cache.

When choosing a suitable PHP framework, you need to consider comprehensively according to project needs: Laravel is suitable for rapid development and provides EloquentORM and Blade template engines, which are convenient for database operation and dynamic form rendering; Symfony is more flexible and suitable for complex systems; CodeIgniter is lightweight and suitable for simple applications with high performance requirements. 2. To ensure the accuracy of AI models, we need to start with high-quality data training, reasonable selection of evaluation indicators (such as accuracy, recall, F1 value), regular performance evaluation and model tuning, and ensure code quality through unit testing and integration testing, while continuously monitoring the input data to prevent data drift. 3. Many measures are required to protect user privacy: encrypt and store sensitive data (such as AES

To enable PHP containers to support automatic construction, the core lies in configuring the continuous integration (CI) process. 1. Use Dockerfile to define the PHP environment, including basic image, extension installation, dependency management and permission settings; 2. Configure CI/CD tools such as GitLabCI, and define the build, test and deployment stages through the .gitlab-ci.yml file to achieve automatic construction, testing and deployment; 3. Integrate test frameworks such as PHPUnit to ensure that tests are automatically run after code changes; 4. Use automated deployment strategies such as Kubernetes to define deployment configuration through the deployment.yaml file; 5. Optimize Dockerfile and adopt multi-stage construction

Laravel's EloquentScopes is a tool that encapsulates common query logic, divided into local scope and global scope. 1. The local scope is defined with a method starting with scope and needs to be called explicitly, such as Post::published(); 2. The global scope is automatically applied to all queries, often used for soft deletion or multi-tenant systems, and the Scope interface needs to be implemented and registered in the model; 3. The scope can be equipped with parameters, such as filtering articles by year or month, and corresponding parameters are passed in when calling; 4. Pay attention to naming specifications, chain calls, temporary disabling and combination expansion when using to improve code clarity and reusability.

User permission management is the core mechanism for realizing product monetization in PHP development. It separates users, roles and permissions through a role-based access control (RBAC) model to achieve flexible permission allocation and management. The specific steps include: 1. Design three tables of users, roles, and permissions and two intermediate tables of user_roles and role_permissions; 2. Implement permission checking methods in the code such as $user->can('edit_post'); 3. Use cache to improve performance; 4. Use permission control to realize product function layering and differentiated services, thereby supporting membership system and pricing strategies; 5. Avoid the permission granularity is too coarse or too fine, and use "investment"

The core idea of PHP combining AI for video content analysis is to let PHP serve as the backend "glue", first upload video to cloud storage, and then call AI services (such as Google CloudVideoAI, etc.) for asynchronous analysis; 2. PHP parses the JSON results, extract people, objects, scenes, voice and other information to generate intelligent tags and store them in the database; 3. The advantage is to use PHP's mature web ecosystem to quickly integrate AI capabilities, which is suitable for projects with existing PHP systems to efficiently implement; 4. Common challenges include large file processing (directly transmitted to cloud storage with pre-signed URLs), asynchronous tasks (introducing message queues), cost control (on-demand analysis, budget monitoring) and result optimization (label standardization); 5. Smart tags significantly improve visual

To build a PHP content payment platform, it is necessary to build a user management, content management, payment and permission control system. First, establish a user authentication system and use JWT to achieve lightweight authentication; second, design the backend management interface and database fields to manage paid content; third, integrate Alipay or WeChat payment and ensure process security; fourth, control user access rights through session or cookies. Choosing the Laravel framework can improve development efficiency, use watermarks and user management to prevent content theft, optimize performance requires coordinated improvement of code, database, cache and server configuration, and clear policies must be formulated and malicious behaviors must be prevented.
