Related to #20

I have a project where in some tables i have inserted some constants, like this

$table->addColumn('name', 'string');
// $table->addColumn(...);
$table->create();
$table->insert([
    [
        'id' => \App\Model\Entity\ArticleStates::ARTICLE_NEW,
        'name' => 'New',
        // ...
    ],
    // ....
]);
$table->save();

When using the migrator, if migrations changed, I bake fixtures but this results empty because the migrator truncates it.

// tests/bootstrap.php
$migrator = \CakephpTestMigrator\Migrator::migrate();
$modified = $migrator->getConnectionsWithModifiedStatus();
if (count($modified)) {
   // re-bake fixtures... 
   // here i would need the db not truncated
   // and call "truncate()" manually
}

A solution could be passing an options array for second parameter of Migrator::migrate()

Do you have plans to make this part of the migrations plugin directly? This would probably help especially plugins a lot to verify their migrations.

They already have a require-dev usually on Migrations So having an easy to use test harness then would be super useful I would imagine.

Hi!

I would like to check if there is a migration pending, but instead of runing migrations, i would launch another command.

In my case this command runs migrations, run some other commands and bake some fixtures (e.g ACL acos table)

I think that adding a wrapper for isStatusChanged would suffice. So I can do something like this:

$migrator = CakephpTestMigrator\Migrator(true);
$migrator->configReader->readMigrationsInDatasources();
$migrator->configReader->readConfig([
   ['plugin' => 'Acl'],
   []
]);
if ($migrator->isStatusChanged()) {
   // launch commands, run migrations, re-bake fixtures, etc
}

If you agree i can try open a PR

Thanks for the plugin!

Today I wanted to load the Tags Plugin into a cakephp 3.10 project with fixture_factories 1.5. As with another project of mine with cake4, I wanted to load the Tags Plugin fixtures with Migrator::migrate( [['connection' => 'test'], ['plugin' => 'Tags']], ['verbose' => true]);, but it gave me the error that the Plugin can't be loaded. It seems like the PluginCollection.php class in cake4 will create a plugin if it isn't loaded, as can be seen in: https://github.com/cakephp/core/blob/bed4b6f09550909beea5440627d5a6ff85fb1934/PluginCollection.php#L213. In Cake3 it just throws an error and I have no idea how to load a plugin in tests/bootstrap.php as there is no Plugin::load() anymore. It might not be a issue of fixture_factories, but I haven't found anything in the docs that point out how to load a plugin. It must work somehow, beacause otherwise I couldn't explain why there even is a config parameter plugin in Migrator::migrate. Do you have an example how to load a plugin fixture with cake3 and fixture_factories? Thank you!

Hello!

I am trying to use this plugin in an existing CakePHP 4 project. However, after changing the PHPUnit configuration file, my tests no longer run. The error it presents is:

Base table or view not found: 1146 Table 'database.table' doesn't exist.

In all my current fixtures, I import the table definition of the default connection, using public $import = ['table' => 'table_name'];

How can I use the plugin but keep the current tests working?

In the CI / CD pipeline we execute a .sql file with all CREATE TABLE in the default connection. We do not use the Migrations plugin, as we have a legacy system since the time of Cake 1. Migrations at that time did not meet our requirements. In the pipeline it will be easy to execute this SQL file in the test connection, but I think what it would be like in a development environment when running a single test class. Currently, the complete database contains almost 300 tables. Performing the creation of all of these tables before a single test would be costly.

Hello @pabloelcolombiano

I'm there again ^^ Hope you're going well.

I was upgrading an app from 4.2x to 4.3x. and so vierge-noire packages. After upgrading, a really simple TestCase that implies no database interaction was badly delayed at start (I was previously using skipTablesTruncation trait).

By now, I'm on 4.3.8 for cakephp and 2.5 for migrator on this app.

I've first applied the "fixture upgrade" but it didn't help.

The culprit is the migrator that was running truncations on all tables though no migration have been deployed. I've disabled truncation as explained and now it rocks again.

BUT I'm wondering why this test was launching so quickly in the previous setup and not in the new ? By the way, why choosing to truncate tables as default after a migration in the test environment that should be "hand-cleaned" if needed before the TestCase/test ?

Unfortunately, I don't have any time by now to figure it out so I'm opening this issue . If it seems non relevant to you, feel free to close it 😄

Closes #23

Implementation based on comment on that issue

In the test its required to clean the connection first, as other test before can leave it migrated.

The dropping of the schema should be independent of the test suite light.

Schema droppers should be implemented for all SQL engines.

The tests dedicated .env files will be moved in the tests folder.