serenity-bdd / serenity-cucumber4

Other
13 stars 10 forks source link

Receiving error in cucumber4 #26

Open JeffGaly opened 4 years ago

JeffGaly commented 4 years ago

02:59:34 [ERROR] - Found neither Cucumber 2.x.x nor Cucumber 4.x runtime in classpath 02:59:34 [WARN ] - Failed to load requirements: Found neither Cucumber 2.x.x nor Cucumber 4.x runtime in classpath java.lang.RuntimeException: Found neither Cucumber 2.x.x nor Cucumber 4.x runtime in classpath at net.thucydides.core.requirements.model.cucumber.CucumberParser.loadCucumberFeatures(CucumberParser.java:118) ~[serenity-model-2.0.83.jar:2.0.83]

wakaleo commented 4 years ago

Have you tried with serenity-cucumber5?

JeffGaly commented 4 years ago

No i haven't tried.But with same cucumber4 i have few projects working fine.

wakaleo commented 4 years ago

This error means you don’t have a cucumber dependency in your project

JeffGaly commented 4 years ago

I have cucumber java 4.2.0 and serenity cucumber4

JeffGaly commented 4 years ago

P.S.Im getting this error after the test execution completes and success.

wakaleo commented 4 years ago

It's during report generation. Make sure you have the correct version of cucumber for the version of serenity (see https://github.com/serenity-bdd/serenity-core#what-is-the-latest-stable-version-i-should-use).

JeffGaly commented 4 years ago

@wakaleo Im utilizing the below

serenity core | serenity-cucumber4 | Cucumber | restassured 2.0.83 | 1.0.21 | 4.2.0|3.3.0

robertLacasandile commented 11 months ago

Hello @wakaleo any update on this issue? i am encuntering this one even though i already have updated the versions compatible. but my Java version is 17

wakaleo commented 11 months ago

Use the latest versions of the libraries - look at the starter projects to see what these are.

robertLacasandile commented 11 months ago

we do have restrictions in libraries to be used, that's why we can't use the latest one. here is the versions that we are using: Serenity core: 2.0.55 Serenity Cucumber 4: 4.2.0 io. cucumber : 1.0.21 this was encountered when I have upgraded my IDE to another version of eclipse.

wakaleo commented 11 months ago

Using such old versions will be a problem for you, particularly if you are moving to Java 17. We could have a look as part of a commercial support package, but there may be library conflicts that can only be resolved by upgrading.