When writing feature tests there’s often a lot of boilerplate code that you might have to add to your tests. The default testing framework with Laravel is PHPUnit, a reliable if not somewhat difficult testing tool at time. It’s heavily based on JUnit, a testing cool for Java libraries. Normally if we want to add something to our tests setup we have to implement a Setup method which can be a bit tedious if we’d using the same one over lots of tests. Of course, we could also just add things to the setup method of our TestCase class but then that’s going to run for every test and sometimes we just need for particular tests. Luckily Laravel already has a mechanism baked into its own TestCase that we can modify to switch on and off with our traits.

An Example Trait

So first we need a trait. For the example I’m going to use something simple that pretty much everyone will have to do if making a feature tests, generate users for authentication.

So often a bit of code for a test this might look like this:

$user = factory(User::class) >create();

$this >actingAs($user)
     >get('/home')
     >assertOk();

This can be a bit redundant as our tests get more complicated and we’re left creating a user for authentication for each test. Instead we’re going to put this into a trait that will create the user for each test at set up.

What this will mean is we no longer have to generate our User model or even specify the user when we want to authenticate the request to the API, simply bringing in the trait will give us a user property in our test case.

We still have to change our TestCase to make this happen though. We’ll do this by adding a setUpTraits method to the TestCase class found in tests/TestCase.php which is made with every fresh Laravel application.

The setUpTraits method is actually a part of the parent TestCast. This is how Laravel normally knows how to do things like refresh databases etc. It works by checking what traits are applied to a test. In this case the parent class method is doing this for us and just returns those traits to us as an array. We can then check if there is a key for the Trait we’re using. If there is we want it to set up the user using the setUpUser method found in our Authentication trait.

Now when we produce a test we only need use the trait Authentication and it’ll create a user. For example we can create the test below to open the home page for a user and then see if our user’s name is printed on the page.

	<?php
	namespace TestsFeature;
Tags: Laravel testing Laravel testing Previous Laravel Request wantsJson() isJson() Next Laravel dynamic roles and permissions package Categories All BackEnd Development (59) Career & Freelancing (16) Recent posts December 23, 2025 Laravel InertiaJS Movie App December 22, 2025 Laravel Roles and Permissions with Gates and Policies Full Tutorial for Beginners December 22, 2025 Laravel 9: New Designs! Popular tags Laravel JavaScript search dotnet React testing php laravel9 api beginners crud tutorial magic bestpractices database rolesandpermissions fresher fontawesome svg alpinejs tailwindcss model todayilearned linux GitHub manytomanyrelationship audit Message Sent Successfully Thank you for contacting us. We will get back to you shortly. Have a great day! Close Error Oops! Something went wrong, please try again. Close