Be able to prevent Sauce Labs Node from accidental test runs

[EricCline]

We have a grid setup with three nodes, two are local and the third is the Sauce Node. We'd like to be able to only route tests to Sauce that aren't covered by our nodes. The HandleUnspecifiedCapabilities:true parameter breaks down when multiple nodes can handle a test, because the hub will route tests to the node with the fewest tests currently running.

If there was a way to set the seldom used applicationName parameter for the Sauce Node, then tests could be routed manually, bypassing all the routing logic in the hub and the Sauce Node that makes this scenario difficult. See this post for more context: https://code.google.com/p/selenium/issues/detail?id=3660&q=applicationName&colspec=ID%20Stars%20Type%20Status%20Priority%20Milestone%20Owner%20Summary

Another solution would be to make the HandleUnspecifiedCapabilities parameter be more rigid so as to not accept tests just because the other nodes are currently running a test.

[elgalu]

@EricCline did you solve your problem with -capabilityMatcher ?

[diemol]

@EricCline, a bit late, but we have implemented Zalenium based on this plugin's idea, maybe you can check it and perhaps it helps you.