Level 22
I have the same issue when I have a setUp method in my tests. But ...
/**
* Setup the test
*/
public function setUp()
{
parent::setUp();
$this->beginDatabaseTransaction();
}
Fixes it
1 like
Sep 13, 2015
5
Level 3
DatabaseTransactions does not roll back after each test
I'm writing the tests where the record gets added to a table with a unique email column. I'm using DatabaseTransactions trait, but when I run the test I get:
Illuminate\Database\QueryException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'cmd@gmail.com' for key 'users_email_unique'
The beginDatabaseTransaction method of the trait seem to run the rollBack for beforeApplicationDestroyed, which would indicate that it runs from within the tearDown method before the next test, but I still get the error above. However - if I manually call:
$this->app->make('db')->rollBack();
at the end of each test - the error is gone.
Any thoughts?
Level 3
Thanks @Bloomanity - but that starts new transaction for each test with the previous one still opened.
Level 14
If I'm understanding you, rather than DatabaseTransactions you might want to look at DatabaseMigrations.
From the docs...
"Using Migrations
One option is to rollback the database after each test and migrate it before the next test. Laravel provides a simple DatabaseMigrations trait that will automatically handle this for you. "
1 like
Level 8
This only applies to MySQL: One thing that tripped me up once was that my table type was set to MyISAM which does not support transactions and the laravel testing trait just silently ignored that. Once I switched over to InnoDB, everything worked as I expected.
1 like
Level 8
Run the following command and you should see your tests running smoothly again.
php artisan config:clear
1 like
Please or to participate in this conversation.