How to write tests if there are no migrations in the project

Level 60

Duplicate your current database, it can be empty, only tables, relations, foreign keys are required. Then make sure to remove every entry after you run the tests, you could use tearDown for this

private $user;

protected function setUp(): void
{
	$this->user = User::factory()->create();
}

// your tests

protected function tearDown(): void
{
	$this->user->delete();
}

1 like

Level 1

@Sergiu17 Thanks for solution

Level 80

@freddie2415 Why on earth are migrations in another project?

Level 1

@martinbean I have 2 project one is shop another is admin panel. And one of them has migrations another doesn't

Level 80

@Freddie2415 And the benefit of splitting them across two repositories was…? They’re clearly the same app if they need the same database and migrations, and then presumedly models too.

Level 1

@martinbean There are 4 repositories:

shop - contain migrations, models, shop window for unauthorized clients and SEO, and API for client's personal account.
client's personal account - it is SPA react application for authorized clients
admin-backend - doesn't have migrations, its task is to update the content by synchronizing data from another external application (1C) and it contain API for "admin-panel" SPA
admin-panel - SPA (react app) it is admin panel for some data which not syncing from another external application (1C) for example Blog, Articles...

shop and admin-backend applications have common models

Level 80

@Freddie2415 Right? I still don’t see why they’ve been split into separate repositories if it’s all the same app. It clearly is all the same app if you’re needing access to migrations files in more than one repository.

automica

Level 55

@Freddie2415 so shop and backend are both apis? sounds like they should be 1 repo.

Level 1

@martinbean

I have 2 backend application. One works as a synchronization service and as an api for the admin panel (SPA react app). Another is serving customers. Where a client can view the catalog, log in and place an order.

I didn't want it to be one big monolithic application. Am I not thinking right?

Level 1

@automica They perform different tasks. And during design, I decided to divide into different services

Level 80

I didn't want it to be one big monolithic application.

@Freddie2415 But like I’ve said a few times now, they clearly are the same application if they’re all working from the same database and migrations, and now you need those migrations to write tests.

alessandro.mirabelli