Start unti testin for an existing Laravel project

@tisuchi Hi thanks for your answer . But in unit testing for some tests we need to delete some data and create others ... also I want to implement the CI/CD

@GodziLaravel Here is my thought:

• Make sure you have a seeder for seeding the entire application's data.

• (Make sure) you have all the migration files.

• Then write tests slowly for your project.

  • If you want to use automated (paid) service, then you can try this
  • Alternatively, you can ask Github co-pilot to write test for a function. You just need to confirm the test based on the co-pilot's suggestion.

• A free package blueprint might be helpful for you to generate the test but needs some adjustment/tweaking. You can get some starting point here also.

BTW, also you can check out this discussion to get some idea.

@tisuchi Thanks

@tisuchi another question : is it possible to use some services to generate migration like : https://github.com/kitloong/laravel-migrations-generator, because the existing migration is full of errors

@GodziLaravel

is it possible to use some services to generate migration like...

Of course, it's possible.

But, my opinion is to create a completely new branch that contains the fix of the migrations because this migration will be used in local project setup, CICD and ....

Why not use the extra package?

• Because it's very trivial to fix the migration.
• Reducing the dependency of the package (arguable)!
• ...

@GodziLaravel I would start by running php artisan schema:dump that would give a copy of the current database structure, then you can use that to migrate your test database.

@Tray2 thanks