Purpose of running one test on multiple nodes is checking if one functionality working on all versions of IE for example. So if I have multiple versions of IE, each on one node, then if I send test to hub with matching capability ie, it should match all of my nodes.
This way I am testing that one functionality is working on all versions of some browser and if not, I can tell on which one it doesn't, and...it works in parallel so I'm cutting testing time which is really important for automation testing...
I understand from documentation and posts, that test execution is not attribute of the grid, but distribution to nodes is, and here is only matter of design choice, are you stopping with first matched node or you passing test to all nodes that complies with criteria(for example, type of browser)...
Anyway, back to the subject, problem here is that in order to run one test on multiple versions of the browser I have only two options:
-run same test in loop with different parameters(different versions of same browser) - which will run sequentially, so if I have 5 nodes, only one at the time is running test, other are idle
-clone same test and pass different version parameter in each clone, then run using test engine which supports parallelism - in this case it will run in parallel, but my test code now is pretty messy
Both solutions are compromise and kind of a hack because grid doesn't support fully parallelism in its core, I was wondering is there a way to solve this...
Thank you