DatabaseTransactions trait does not function correctly when Mockery is used.

[36degrees]

The DatabaseTransactions trait does not roll back correctly if Mockery::close throws an exception, as the loop over beforeApplicationDestroyedCallbacks is never executed (the exception takes us out of that context).

This results in queries in tests run after taking a very long time, before finally failing with

Illuminate\Database\QueryException: SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction (SQL: [...]))

Moving Mockery::close to the last call in the tearDown function (i.e. after the callbacks) appears to fix this, but I'm not sure if this could have any other negative impact.

To recreate this, assert something 'invalid' with Mockery and add debug statements to the tearDown method in src/Testing/TestCase.php – they will never get run for the test with the failed Mockery assertion in.

I imagine this will also be happening with the DatabaseMigrations trait, but haven't tested this.

[GrahamCampbell]

Closing due to inactivity.

[mikefrancis]

@36degrees Hey there, did you get anywhere with this? Having the same problem in Laravel 5.4

Only way to get our test suite not to error is to remove the trait, but this randomly breaks a bunch of tests 😢

[36degrees]

Afraid I've changed job and haven't worked with Laravel in a couple of years, and no longer have access to the source code, so I can't tell you what we did! Sorry!