[Updated PR#1476] Add explanation for database migration resets

[divine]

This PR was recreated from #1476 with updated branch or resolved conflicting files.

--

Add Database Testing to index.
use DatabaseMigrations; instead of use RefreshDatabase; for laravel 5.6 compatibility issue (#1475)

Co-Authored-By: theminer3746 [email protected]

[Giacomo92]

I think both RefreshDatabase and DatabaseMigrations needs more tests. I have tried to use them without success. Next week I will have to work with this also for my projects. I will keep you updated @divine @Smolevich

[divine]

I think both RefreshDatabase and DatabaseMigrations needs more tests. I have tried to use them without success. Next week I will have to work with this also for my projects. I will keep you updated @divine @Smolevich

Sure, I'm just trying to update/resolve PRs that doesn't have a breaking change, after that we could focus on actual bugs.

Thanks!

[Giacomo92]

Yep, I saw. Good job @divine
Sooner or later all pull requests will be closed

[Giacomo92]

I have added some tests on demo application here. @divine @Smolevich
I think it is better to write:

• use DatabaseMigrations; -> working
• use DatabaseTransactions; -> not working for now
• use RefreshDatabase; -> not working for now

in order to avoid other issues to be opened.

[divine]

@Smolevich @Giacomo92 @rennokki what you think guys?

[Smolevich]

@Smolevich @Giacomo92 @rennokki what you think guys?

i think that it's ok