Driver Browser Compatibility

[jaridmargolin]

I initially thought I would post the countless issues filed on protractor and various testing frameworks regarding the issue, but really I don't think I need to. If you work on any selenium related projects, you know that occasionally driver versions become incompatible with browser versions. The errors displayed to the end user, supply little useful information on what is happening.

I think with community backing, a list of supported browser/driver pairings could be maintained (or possibly a list of known incompatibilities). With this list and sniffing, upstream tools can be smarter about how to proceed (whether it involves automatically installing the latest driver, or notifying the user of possible unexpected behavior).

I do see the documentation provided here: https://github.com/angular/webdriver-manager/blob/master/docs/protractor.md

I am curious if it would be possible for data like this to be automated and formatted for consumption.

While the idea has been stirring in my head for a while, I decided to file an issue here based on the discussion at jaridmargolin/inspect-process#36 (comment)

[cnishina]

@jaridmargolin I agree.

Background on protractor.md:

The matrix was my experiments. The idea was to hopefully stop getting bugs on Firefox 48+ in combination with selenium-standalone-server 3.x. Since this markdown file would require maintenance and pull requests to maintain it, this is probably better on StackOverflow (in hindsight).

Docs on StackOverflow

We could have a better community driven list of supported drivers. These would probably be best listed in StackOverflow under the webdriver-manager tag or under the Protractor documentation (not sure which is better). @igniteram @AlexCE @priyanshus any thoughts? (By the way, nice job on StackOverflow Protractor documentation!)

I'm thinking the matrix could have a list of Protractor versions, working driver version, working selenium-standalone-server version, browser versions. I've also received issues with early versions of Protractor testing Internet Explorer 9 and I didn't know how to direct them other than look up the webdriver-manager config in the tagged Protractor version.

[igniteram]

@cnishina The matrix would be very helpful to the users, I have seen that kinda info in couple of other repo's. It would be good to have separate SO docs for webdriver-manager & protractor. Also the matrix for protractor should list mobile versions as well!

I created webdriver-manager SO doc proposal , we need atleast 5 approvals for that be created!

[priyanshus]

@cnishina This is the thing, I was always missing(Though I never thought of having such kind of matrix on Protractor Doc) but I agree with your suggestion. Such matrix would really help the automators.

In my opinion, the matrix should go under Protractor docs as when we search for browser compatibility we rarely think about webdriver-manager and prefer to look into protractor repo.

[cnishina]

I see. We'll remove the action item to release version 13.0.0-beta.1. I'll have to create an issue in Protractor.