Closed jeffscottbrown closed 6 years ago
Replacing testRuntime "org.seleniumhq.selenium:selenium-api:3.6.0"
with testCompile "org.seleniumhq.selenium:selenium-api:3.6.0"
gets around the specific problem mentioned above but then gets to other dependency problems.
I think we should have a set of dependencies and GebConfig.groovy
created by default that will work with the HtmlUnitDriver without any special config changes.
I should clarify.. bringing back HtmlUnitDriver isn't really what I am advocating, but some headless solution.
If I change testRuntime "org.seleniumhq.selenium:selenium-api:3.6.0"
to testCompile "org.seleniumhq.selenium:selenium-api:3.6.0"
and run with the following, it does appear to work...
./gradlew -Dgeb.env=chromeHeadless iT
Replacing
testRuntime "org.seleniumhq.selenium:selenium-remote-driver:3.6.0"
testRuntime "org.seleniumhq.selenium:selenium-api:3.6.0"
with:
testCompile "org.seleniumhq.selenium:selenium-remote-driver:3.6.0"
testCompile "org.seleniumhq.selenium:selenium-api:3.6.0"
solve the issue.
I am able to execute the tests with:
./gradlew check
It executes the tests in the firefox environment.
See the project at https://github.com/jeffbrown/gebdependencies.
The combination of dependencies in a newly created 3.3.2 web profile app appear to be problematic.
See comments at https://github.com/jeffbrown/gebdependencies/blob/4f17453dd8d413522d343318f0cea8b08018c479/build.gradle#L63-L73...
This appears to be related to recent changes made at https://github.com/grails-profiles/base/commit/bc1db3bdaee34d922a8593fdb9d454c466b08275#diff-85591e57e3c09fdfb19080a3c7368f83.