Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dealing with browser mismatched versions #4

Open
kastork opened this issue Jan 27, 2016 · 0 comments
Open

Dealing with browser mismatched versions #4

kastork opened this issue Jan 27, 2016 · 0 comments

Comments

@kastork
Copy link

kastork commented Jan 27, 2016

I had a problem today getting Firefox driver to work. The problem was that the Firefox version on my machine was too new. What I mean is, the geb plugin calls for selenium 2.47.1. So logically, one would add the firefox driver for that same selenium version. 2.47.1. This fails, but updating to the most recent firefox driver version (2.49.1) is all it takes to get it working. But now I've got a geb system that doesn't match my driver version. The alternative would have been to 'downgrade' my local firefox installation to the one that's assumed by 2.47.1.

Web browser versions are likely to move faster than versions of the geb plugin, so I'm wondering if there's a way (and if it is advisable) to structure the plugin so that you can pick the selenium version that will be used without having to change the plugin itself. If this could be worked out then the grails build.gradle file would be the single source of truth for selenium configuration of grails functional tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant