rails distributed parallel tests

Question

How can I run paralell tests on dual core machines connected via SSH on the same network ?

https://github.com/grosser/parallel_tests runs fine for local workers, but there is no way to run it on multiple machines

https://github.com/qxjit/deep-test - I've had no luck upon running it, there is a line in the example like

t.distributed_hosts

which throws an error

With Hydra I got an issue waiting forever for ssh workers

I tried the alpha version of Buffet, created a test repo and ran it but with no luck

fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git

I want to run only standard unit / integration / functional tests

No fancy stuff at all.

Building your own parallel/distributed testing setup can be quite a challenge. We've had great luck using a service called TDDium (tddium.com) that manages this for you, using a git remote server like Heroku to accept batches of code to run. I highly recommend them. — Winfield
– Winfield, Commented Apr 19, 2012 at 18:34
In the same vain as Winfield, we use CircleCi (circleci.com) to parallelize our tests with great success. — Mitch
– Mitch, Commented Oct 29, 2013 at 20:50
Why is parallel_tests not suitable for multiple machines? And what error does deep-test throw? — Jeremy Rodi
– Jeremy Rodi, Commented Nov 6, 2013 at 16:29
You could just run your own Travis or Jenkins Setup and run on push or do you want Guard/Autotest Style Remote Tests? — Max Schulze
– Max Schulze, Commented Nov 15, 2013 at 22:24

pungoyal · Accepted Answer · 2014-02-11 05:58:14Z

1

do try out http://test-load-balancer.github.io/ i have had great success with it in the past.

answered Feb 11, 2014 at 5:58

pungoyal

1,79815 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

jake · Accepted Answer · 2014-09-26 06:50:14Z

If you are willing to run your tests on a hosted CI service, then there are quite a few good options. To list a few here in no particular order:

Travis CI (there is pro version for private repos)
Semaphore (Heroku addon present) parallelism even on the free plans
Tddium (already mentioned above)
Codeship (Heroku addon present, unsure of any out of the box support)
Circle CI (Parallelism on paid plans)
Snap-CI (Pipeline parallelism allow you greater control but with some configuration. Also they might be adding more out of box support in future)

I have tried all of them in my projects to varying levels, and they all work well. The differences would be mostly in how the services are priced. If you dont mind paying for the subscriptions, it would be best to rely on these services instead of trying to deal with hassle of splitting out the tests into processes. Of course, the exception would be if you doing it at a sufficiently large scale which might justify the cost savings in that case.

Some other points to keep in mind:

Parallelism within the same process can still give you good results on a sufficiently beefy box (with more cores) without much effort should be your first chocie, unless you have have already run out of option.
If your eventual goal is to speed up tests, do look at some benefits Travis-CI offers by with a better file system and an in memory database. (I not sure about this one)
If you still planning on setting up this on your own, you should look at GoCD, in combination with TestLoadBalancer (mentioned earlier).
Keep in mind if the problem your trying to solve is a growing test suite on sufficiently large project, you might want to actively start thinking about splitting your test suites logically and actually speeding them up, since parallelism only manages to delay the ultimate problem of a long running test suite it does not solve it completely.

Community · Accepted Answer · 2017-05-23 10:29:03Z

0

Although not particularly related to how to run parallel_tests in multiple machine in the network, here are the issues I encountered and how I solved them when using parallel_test.

tests getting killed in the middle of a run using parallel_tests

edited May 23, 2017 at 10:29

CommunityBot

11 silver badge

answered Dec 17, 2013 at 19:17

lsaffie

1,8241 gold badge18 silver badges24 bronze badges

Comments

Community · Accepted Answer · 2017-05-23 11:55:15Z

0

I think problem in git configuration. check your git configuration

try this link

Whats the best way to work with Github and multiple computers?

edited May 23, 2017 at 11:55

CommunityBot

11 silver badge

answered Apr 19, 2014 at 10:33

Kanna

1,0401 gold badge13 silver badges30 bronze badges

Comments

user125941 · Accepted Answer · 2015-05-02 05:04:48Z

0

You can also use Shippable http://www.shippable.com continuous service for parallel test

answered May 2, 2015 at 5:04

user125941

1

Collectives™ on Stack Overflow

rails distributed parallel tests

5 Answers 5

Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related