Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parallel test running. Documentation, recommendations. #178

Open
Kostanos opened this issue May 25, 2016 · 5 comments
Open

Parallel test running. Documentation, recommendations. #178

Kostanos opened this issue May 25, 2016 · 5 comments

Comments

@Kostanos
Copy link

Hi, I'm playing with parallel test running.
My main goal is to speed up the tests.
In my case, 70 tests, mostly client-side.
Running without parallel and with parallel 2 or 4 processes, has no changes to the test execution time at all (2 minutes in my case).

I guess, one of the reason is running only one meteor instance, one browser instance?

Is there any recommendations, documentation about how can tests be optimized to run in parallel.

@apendua
Copy link
Member

apendua commented May 27, 2016

@Kostanos How exactly you're using the parallel test runner?

@Kostanos
Copy link
Author

Kostanos commented May 27, 2016

gagarin -p 2

Actually I just realized, I used it wrong, but now half of my tests are failing.
They share the DB right? so, if I use the same fixture in two parallel tests, and one of the tests changing it, the second one will fail because this change also will affect it, no?

@apendua
Copy link
Member

apendua commented May 28, 2016

@Kostanos You are right. If you want to run them in parallel you will need to make sure that each test is operating on a separate database. But in fact, this is the default behavior so if you are experiencing these problems it probably means that you've turned it off. Correct?

@Kostanos
Copy link
Author

I didn't changed any settings regarding using DB, I didn't even knew they exists.

So I run the tests with default settings.

@apendua
Copy link
Member

apendua commented May 28, 2016

@Kostanos If that's the case then I don't see a reason the test may be failing. Sometimes I got timeout errors if I use too many parallel instances because my processor cannot handle it. Are your errors messages specific to your tests or maybe they look like internal Gagarin errors?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants