Combine migrations, fixtures and tests...

[bobmulder]

I have a plugin which has tests which works great. However, people started mention me because the migration failed. So that made me think:

• should I test my migrations?
• why aren't my migrations used as fixture, at least to initialize the table?

Please explain me what I am missing because the fact that migrations are not tested doesn't feel good... If I'm missing nothing we should think about a way to integrate migrations into fixtures...

[markstory]

why aren't my migrations used as fixture, at least to initialize the table?

Not everyone uses CakePHP's migrations.

should I test my migrations?

I would test backfills, but schema changes should be covered by the application/plugin's tests.

[HavokInspiration]

There's the possibility to test your migrations... in some way.
You can use the Migrations class which will allow you to run migrations in a non-shell environment. You can see the doc for this class here.

This should allow you to test that your migrations are correctly running in the various environments you are testing your plugin with.

[dereuromark]

Closing as a possible solution has been pointed out.