README

A tool to run migrations prior to running tests

The Migrator

For CakePHP 3.x

composer require --dev vierge-noire/cakephp-test-migrator "^1.0"

For CakePHP 4.x

composer require --dev vierge-noire/cakephp-test-migrator "^2.0"

For CakePHP 4.3+

The migrator was integrated into the migration plugin (see the doc). The present package will not be further maintained.

Introduction

CakePHP fixtures handle the test DB schema in a paralell manner to the default DB. On the one hand you will write migrations for your default DB. On the other hand you either hard coded describe the schema structure in your fixtures, or meme the default DB. The later is simpler, but it forces you to have two DBs. And in CI tools, you will have to run the migrations on your default DB, and the fixtures meme the default DB. So why not running migrations directly on the test DB?

With the CakePHP Test Migrator, the schema of both default and test DB are handled exactly in the same way. You do not necessarily need a default DB. Tables are not dropped between test suites, which speeds up your tests. And migrations are part of the whole testing process: they get indirectly tested.

Setting

The package proposes a tool to run your migrations once prior to the tests. In order to do so, you may place the following in your tests/bootstrap.php:

\CakephpTestMigrator\Migrator::migrate();

This command will ensure that your migrations are well run and keeps the test DB(s) up to date. Since tables are truncated but never dropped by the present package's fixture manager, migrations will be run strictly when needed, namely only after a new migration was created by the developer.

The Migratorapproach presents the following advantages:

• it improves the speed of the test suites by avoiding the creation and dropping of tables between each test case classes,
• it eases the maintenance of your tests, since regular and test DBs are managed the same way,
• it indirectly tests your migrations.

You may pass true as the second argument for a verbose output on the console.

Options

You can pass a boolean as options, it will be used as verbose

\CakephpTestMigrator\Migrator::migrate([], true);
// is the same as
\CakephpTestMigrator\Migrator::migrate([], ['verbose' => true]);

Multiple migrations settings

You can pass the various migrations directly in the Migrator instantiation:

\CakephpTestMigrator\Migrator::migrate([
    ['connection' => 'test', 'source' => 'TestFolder'],       
    ['plugin' => 'FooPlugin', 'connection' => 'FooConnection'],      
    ['source' => 'BarFolder'],
    ...
 ], ['verbose' => true]);

You can also pass the various migrations directly in your Datasource configuration, under the key migrations:

// In config/app.php
'test' => [
    'className' => Connection::class,
    'driver' => Mysql::class,
    'persistent' => false,
    'timezone' => 'UTC',
    'flags' => [],
    'cacheMetadata' => true,
    'quoteIdentifiers' => false,
    'log' => false,
    'migrations' => [
        ['plugin' => 'FooPlugin'],      
        ['source' => 'BarFolder'],
    ],
],

You can set migrations simply to true if you which to use the default migration settings.

Migrations status

Information on a connection's migration status will be obtained as follows:

$migrator = Migrator::migrate();
$connectionsWithModifiedStatus = $migrator->getConnectionsWithModifiedStatus();

the method getConnectionsWithModifiedStatus returning a list of the connections with down migrations prior to running the migrations.

Data truncation

Use truncate option to truncate (or not) after migrations are done. This is useful if you need to do other tasks in the test suite bootstrap

$migrator = Migrator::migrate([], ['truncate' => false]);
// do something with the migrated database (bake fixtures, etc)
$migrator->truncate();

What happens if I switch branches?

If you ever switched to a branch with nonexistent up migrations, you've moved to a branch in a past state. The Migrator will automatically drop the tables where needed, and re-run the migrations. Switching branches therefore does not require any intervention on your side.

What if I do not use migrations?

The Migrator::dump() will help you import any schema from one or several sql file. Run for example:

Migrator::dump('test', 'path/to/file.sql')

or with multiples files

Migrator::dump('test', [
    'path1/to/file1.sql',
    'path2/to/file2.sql',
])

or for a verbose output

Migrator::dump('test', 'path/to/file.sql', true)

The first argument is the name of the connection, the second the file(s) to dump, the third the verbosity (boolean).

This method will however drop the schema prior to recreating it, which presents a significant loss of performance in comparison to the migration-based solution.

Trouble shooting

It might be required, right after you installed or updated the plugin, to drop and recreate your test database. If the problem persists, feel free to open an issue.

Authors

• Juan Pablo Ramirez
• Nicolas Masson

Support

Contact us at vierge.noire.info@gmail.com for professional assistance.

You like our work?

License

The CakephpTestMigrator plugin is offered under an MIT license.

Copyright 2020 Juan Pablo Ramirez and Nicolas Masson

Licensed under The MIT License Redistributions of files must retain the above copyright notice.