Closed cjekal closed 2 years ago
What's weird is that the error seems to be around not finding a Test Strategy Adapter. I've tried matching my Docker container's gradle version to my host's gradle version (7.2) and that did not seem to resolve things. It seems weird that serenity-bdd gets past the No Test Strategy Adapter found: To run JUnit tests in Serenity make sure that either the Serenity JUnit 4 (serenity-junit) or JUnit 5 (serenity-junit5) dependency is available.
just fine locally, but not within a container. Any tips/tricks for troubleshooting classpath issues?
Hmmm, I've never come across this. The Serenity smoke tests and demo tests are run routinely on Github with Github Actions (e.g. https://github.com/bdd-in-action/flying-high-acceptance-tests/blob/main/.github/workflows/maven.yml and https://github.com/serenity-bdd/serenity-core/blob/master/.github/workflows/smoketest_chrome.yml) - maybe they could give you some clues.
Thanks @wakaleo I've tried a Docker container with gradle 7.3, gradle 7.2, and maven 3.6.3. I've also tried selenium/selenium-chrome
and selenium/node-chrome
. Do you have any sample github actions that run the gradle side of things? (i'm personally a bigger fan of gradle ^_^)
We think we figured it out. We were trying to run this in Docker with a random user, and so when gradle downloaded dependencies, it was ending up in a '?' folder. Switching to a real user fixes the issue. Thanks @wakaleo for your help and input!
Hello, I'm trying to run this repo as is (no changes) using
gradle test
, but I'm getting an error. I'm using thegradle:jdk11
docker image. Here's the output I'm getting:Any hints or preferred docker images to use?