You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: