I haven't looked at plugins specific to Alembic. People typically refer to the .upgrade() and .stamp() commands at an API level to have migrations run as part of the test suite.
On Jun 3, 2014, at 8:11 PM, Ali-Akber Saifee <a...@indydevs.org> wrote: > Hi, > > I'm hoping to use alembic to manage database migrations for an existing > project which doesn't use sqlalchemy (or any other orm) for its database > models. I'm planning to use raw sql executes in each revision solely to > benefit from database schema versioning. > > I want to still be able to do an 'upgrade head' before all my tests run > (using nosetests) so that the tests target the eventual production > environment. > > Wondering if anyone has had any experience doing this type of thing and how > they approached it. Would a nose-alembic type plugin be useful for others? > There already exists https://github.com/jsok/nose-alembic-attrib, but it only > kicks in when tests declare a dependency on a specific version of the > database. > > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy-alembic" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy-alembic+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy-alembic+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
