[jakub_g]

Very similar conceptually to a tool (Attester) that our team has released a couple of months ago. https://github.com/ariatemplates/attester/

We use it as a distributed way to perform tests in our main project (Aria Templates: https://github.com/ariatemplates/ariatemplates). The tool is able to use PhantomJS (configurable number of instances) and "normal" browsers which can connect in the same manner (by opening a URL). We use PhantomJS on Travis for continuous integration builds before merging pull requests, and real browsers before each release (every 3 weeks).

We support only our own tests so far (eating the own food), but we may add support for other types as well.

Behind the scenes, the tool first gathers a set of classpaths of the tests to run (recursively); then it dispatches them to active browsers (e.g. when you have a couple of people connected via IE8, each of them will receive a subset of tests to run and effectively the test suite finishes earlier).

You can also run the test suite entirely in the command line (PhantomJS), and if you have multicore processor, you may increase the number of PhantomJS instances to parallelize the suite.

Looking forward for comments and forks!

[ozanonline]

Cool, you might be interested in Testacular also, a similar project to yours. The main differentiator for Thrill/Queen will be that Queen acts as a central server which anyone in the network can execute tests on. So if you have many developers, they don't each have to setup their own browser pool.