Home / Questions / 381083
Accepted
Shassain
Asked: 2020-08-11 19:11:59 +0800 CST 2020-08-11 19:11:59 +0800 CST

How to perform a unit test in Laravel without logging the test data to the database?

  • 772

I have the following test:

public function testExample()
{
    $user = factory(User::class)->create();
    $response = $this->actingAs($user,'api')->json('POST', 'api/rangos?api_token='.$user->api_token,
        [
            "denominacion"=>"Visitante",
            "nivel"=>"1"
        ]
    );
    $response->assertStatus(201);
    $response->assertJsonStructure([
        "id",
        "denominacion",
        "nivel",
        "miembros",
        "updated_at",
        "created_at"
    ]);
}

The function I'm unit testing is as follows:

public function store(Request $request){
    $data=new Rango($request->all());
    $data->save();
    return response()->json($data->load("miembros"),201);
}

The unit test passes successfully, the problem is that when executing the test the data is stored in the database. ie if I run the test 10 times the data is logged 10 times and I want to prevent that from happening.

How do I get it to pass the test without the data being permanently recorded in the database?

Edition

I already tried to do it with the trait RefreshDatabaseand what happens with RefreshDatabase is that it deletes any other data inside my database, that is, it cleans the entire database, and I don't want that either.

laravel

2 Answers

  1. What happens is that the method create(), in addition to creating an instance of the model, inserts the data into the database, what you are looking for is the method make(), which only creates models but does not save them in the database.

    $user = factory(User::class)->make();

    Edit:

    If you necessarily have to insert data in BD. Then you should use RefreshDatabaselaravel's Trait, specified here . Which does a roll-backto the database after each test.

    Edit:

    Another solution is to work with transaccioneswhen doing a test, Laravel provides the methods setUp()and tearDown(), therefore, it can be handled like this:

    public function setUp()
{
    parent::setUp();
    DB::beginTransaction();
}

public function tearDown()
{
    parent::tearDown();
    DB::rollBack();
}

    These methods must be inside your test class.

    • 2
  2. Best Answer

    you could also use DatabaseTransactions , its use would be the following:

    use Illuminate\Foundation\Testing\DatabaseTransactions;
use Tests\TestCase;
class ExampleTest extends TestCase
{
use DatabaseTransactions;
    ...
}
    • 1