mobile web testing - Githubissues

nwlunatic / appium-autoregister

Automatically register connected devices or emulators to selenium grid with appium on runtime

MIT License

11 stars 5 forks source link

mobile web testing #10

Open serhatbolsu opened 9 years ago

serhatbolsu commented 9 years ago

Hey, I became fond of what you did here. I see that you are using browserName in order to route to appium nodes. In that case, how do you handle mobil web automation, since there you need to set browserName to like "Chrome", "Browser" for android.

I have written an custom capabilitiy matcher inside hub, just considering your solution but this is an important blocker for me that if you have a solution for this.

nwlunatic commented 9 years ago

Hey! I agree, that using browserName is not the right solution, but I did it because:

that was the fastest solution
it's working "out of the box" with grid for native app's
I've needed to see device name in grid

I'd rather prefer to use deviceName and custom capability matcher. The only problem is I need to see device name in grid, but I think I can write some kind of servlet for node properties api. Maybe you can share your matcher, so I can use it?

serhatbolsu commented 9 years ago

Hey Igor,

Thank you for reply.

This is our capability matcher early version : https://gist.github.com/serhatbolsu/40ca473991232c578173 It is simple and enough to use deviceName and simply dont bother browserName.
In order to see deviceName in grid/console, there is a simple way you might not know. you can hower mouse to browser icon or device name or null value inside node windows. It shows all desiredCapabilities for that node.

Only problem I have right now is that; if appium selects with deviceName and use browserName for say "chrome". For some reason /grid/console does not work. Node and hub execute fine but you can not observe the site.

BR, Serhat