Full App Tests and Server Start about meteor-mocha HOT 4 CLOSED

I'm not sure that in general it would be best practice to have migrations running for tests, even full app/end-to-end tests. Can you wrap your migrations in if (!Meteor.isAppTest) so that they don't run, and then insert whatever data you need for your tests in a mocha before hook?

from meteor-mocha.

Otherwise you can have an async before hook that checks for the necessary data every second using setInterval and doesn't call done until it's there.

from meteor-mocha.

Eric, I like your second suggestion. I was not aware that in the before
hook, there was a 'done' api...

As for database migrations, they need to run as part of the continuous
integration pipeline. Those migrations contain more than data inserts, they
also contain schema changes. We're doing continuous delivery and those
scripts will be run in production as part of the app being deployed. We
need to test those scripts as much as we need to test the new code.

Thank you for your suggestions!

On Wed, May 11, 2016 at 6:23 PM Eric Dobbertin [email protected]
wrote:

Otherwise you can have an async before hook that checks for the necessary
data every second using setInterval and doesn't call done until it's
there.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#1 (comment)

Rémy Gendron
Ingeno / Be the Revolution

418 809-8585
[email protected]
remy.gendron (Skype)
http://ingeno.ca

from meteor-mocha.

OK, yeah it all depends on what your process is.

from meteor-mocha.