Replies: 1 comment
-
Guess you've already figured this out - but for any future visitors you can run the migrations via artisan This will run once for the first test. use DatabaseTransactions;
protected static $initialized = false;
protected function setUp(): void
{
parent::setUp();
if (!self::$initialized) {
$this->artisan('vendor:publish', [
'--tag' => 'permission-migrations'
]);
self::$initialized = true;
}
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm creating a package that relies upon this package and this new package add a new functionality that I don't want to add to the main package.
This "new functionality" adds new migrations and add new columns to the main package's migrations so, my problem is:
How to use the migrations from the main package in this new package? (hope this makes sense xD)
Right now I'm doing something like this in my TestCase file:
But I'm not sure if this is the right approach.
Beta Was this translation helpful? Give feedback.
All reactions