Document the "applicationName" capability

[lukeis]

Originally reported on Google Code with ID 3660

As said on https://groups.google.com/group/selenium-users/browse_thread/thread/3d1b0405c6e93653?hl=es&noredirect=true


There is an undocumented way to select a node in a grid to test your 
application. You can use the "applicationName" capability to do this. 
Currently, there is no way for  Selenium to diference between 32 and 
64 bits version of a given OS. So if you want to test with a specific 
version you could setup the nodes as: 

NODE1: 
java -jar selenium-server-standalone-2.20.0.jar -role node -hub 
http://HUB_IP:4444/grid/register -browser 
browserName=firefox,version=11,maxInstances=1,platform=WINDOWS,applicationName=windows7_32bits_firefox_11


NODE2: 
java -jar selenium-server-standalone-2.20.0.jar -role node -hub 
http://HUB_IP:4444/grid/register -browser 
browserName=firefox,version=11,maxInstances=1,platform=WINDOWS,applicationName=windows7_64bits_firefox_11


In your tests you have to add 
"applicationName=windows7_32bits_firefox_11" to your desired 
capabilities array. 

It would be very nice this "undocumented" feature turns "oficial" by documenting and
maintaining it.

Reported by jaruzafa on 2012-04-04 10:23:07

[lukeis]

Reported by francois.reynaud on 2012-04-04 10:48:02

[lukeis]

TODO : document the capability matcher interface

Reported by francois.reynaud on 2012-04-04 10:48:54

• Labels added: Type-Enhancement
• Labels removed: Type-Defect

[lukeis]

Reported by barancev on 2012-05-04 18:37:51

• Labels added: Component-Grid, Component-Docs

[lukeis]

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

Reported by eduardomcerqueira on 2012-05-05 00:47:09

[lukeis]

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

Reported by francois.reynaud on 2012-10-10 08:16:32

• Status changed: NeedsClarification

[lukeis]

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

?

Reported by a.u.savchuk on 2013-09-10 14:13:06

[lukeis]

Reported by luke.semerau on 2015-09-17 17:44:49

• Labels added: Restrict-AddIssueComment-Commit