TODO : document the capability matcher interface

Thank you very much for this post. I have searched for this solution for more than 1
week in all forums, groups, discussions etc.

It sounds perfect for what I need in my GRID.

here is the piece of the code we have in DefaultCapabilityMatcher class:

  public DefaultCapabilityMatcher() {
    toConsider.add(CapabilityType.PLATFORM);
    toConsider.add(CapabilityType.BROWSER_NAME);
    toConsider.add(CapabilityType.VERSION);
    toConsider.add("applicationName");

  }

My suggestion is in next Selenium version to have at least more 2 capabilities like

toConsider.add("environment");
toConsider.add("arch");

it would be helpful for many people I am sure.

thx,
Eduardo

Hello,

I don't see a reason to change the default matcher.It should remain super simple.

Have you considered creating your own matcher ? You can specify it using the -capabilityMatcher
option when you start the hub. That way you can add all the custom capabilities that
are specific yo tour setup.
thanks,
François

Hi!

Am i right that this issue just about documenting CapabilityMatcher at:

* interface CapabilityMatcher API docs
* default implementation DefaultCapabilityMatcher API docs
* interface/implementation/extending CapabilityMatcher at Grid2 wiki

?