-
-
Notifications
You must be signed in to change notification settings - Fork 513
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
Caused by: java.lang.ClassNotFoundException: net.thucydides.core.model.TestStep after updating Serenity version >= 4 #3318
Comments
@wakaleo There is one more issue, when running with serenity |
Here is what I could find:
I would probably recommend removing webdriver-overload and the custom driver, and rewriting the tests using more idiomatic Serenity features (see https://github.com/serenity-bdd/serenity-core/tree/main/serenity-smoketests or https://github.com/serenity-dojo/swaglabs-serenity-cucumber.git for example). |
@wakaleo Thanks pointing this out, it worked after bumping Could you please let us know if what causes this? |
To get the browserstack status updates when running with Cucumber 7 you need to run with a recent version (e.g. 4.0.29) and include the serenity-browserstack plugin in the dependencies. |
@wakaleo Acknowledged. Have tried the suggestion. Still, I'm not getting status updates on the above sample. There are no such errors, plugin seems to be working since it's marking the session name on BrowserStack correctly. |
Could you try with this repo? https://github.com/serenity-bdd/serenity-todomvc-demo/tree/browserstack (The video camera icon indicates that the BrowserStack integration is working) |
What happened?
Getting below exception when trying to bump Serenity version v4+ :
What did you expect to happen?
Tests should run on BrowserStack with proper session name and status.
Serenity BDD version
LTS (4.0.19)
JDK version
17
Execution environment
How to reproduce the bug.
https://github.com/kamal-kaur04/serenity-tests
How can we make it happen?
Hire the Serenity BDD team
The text was updated successfully, but these errors were encountered: