Closed heychazza closed 2 years ago
Hey @heychazza! That's kinda confusing to me, because it looks like the RefreshDatabase
trait defers to migrate:fresh
under the hood. (https://github.com/laravel/framework/blob/9.x/src/Illuminate/Foundation/Testing/RefreshDatabase.php#L73)
When you're running tests, are you using the SingleStore driver? If your test DB is set up to use the MySQL driver but is pointed at a SingleStore db, you might get that error.
Hey @heychazza! That's kinda confusing to me, because it looks like the
RefreshDatabase
trait defers tomigrate:fresh
under the hood. (https://github.com/laravel/framework/blob/9.x/src/Illuminate/Foundation/Testing/RefreshDatabase.php#L73)When you're running tests, are you using the SingleStore driver? If your test DB is set up to use the MySQL driver but is pointed at a SingleStore db, you might get that error.
Apologies in the delay, that was a good spot! Always annoying when its that pesky phpunit.xml
file with the override.
Hi,
When attempting to run a series of tests that involve the RefreshDatabase trait, I am greeted with the following error:
This only applies within tests, as manually doing
php artisan migrate:fresh
doesn't cause this. However my tests all rely on refreshing.