Skip to content
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

Serenity upgrade from 1.2.2 to latest 2.2.x #2165

Closed
nshiveg opened this issue Jul 14, 2020 · 3 comments
Closed

Serenity upgrade from 1.2.2 to latest 2.2.x #2165

nshiveg opened this issue Jul 14, 2020 · 3 comments
Labels

Comments

@nshiveg
Copy link

nshiveg commented Jul 14, 2020

Hi John and team,

Can we upgrade serenity core and other components(serenity-cucumber and serenity rest assured) to the latest 2.2.x
Is it possible? or it is not feasible. I have attached my POM here.

By the way you people are really doing wonders. It is really good to see the way things are shaped in serenity. We in Nokia completely into the serenity.

pom.zip

@wakaleo
Copy link
Member

wakaleo commented Jul 14, 2020

Hard to say from just the pom - a lot of the underlying libraries (such as Cucumber and rest assured) have had lots of breaking changes since version 1.2.2, so you will probably need to change your code as well.

@nshiveg
Copy link
Author

nshiveg commented Jul 14, 2020

Hi John,

Thanks a lot for your response.
Code change is fine for us. But upgrade is supported is it?
There will not be any change in the cucumber feature file writing?, I mean what we had written in 1.1.23 serenity cucumber we don't need to change them correct. Since we have 5000 cases changing that would be really difficult.

@wakaleo
Copy link
Member

wakaleo commented Jul 14, 2020

Between Cucumber 1 and Cucumber 5+ there are many many API changes so your glue code will need to be updated fairly extensively.

@wakaleo wakaleo closed this as completed Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants