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

Pico container lifecycle changes #2771

Closed
mszalbach opened this issue Jun 26, 2023 · 9 comments · Fixed by #2772
Closed

Pico container lifecycle changes #2771

mszalbach opened this issue Jun 26, 2023 · 9 comments · Fixed by #2772
Assignees

Comments

@mszalbach
Copy link

👓 What did you see?

The Pico container lifecylce changed between 7.11.2 and 7.12.1 because of this issue #2724

The dispose method is not called after each Scenario like before, but only once after the first scenario. In the following runs the state is not started anymore and the dispose method is not called anymore. Also affects the start and stop methods.

@after works like before.

✅ What did you expect to see?

The same behavior like in 7.11.2 or a hint that there was a breaking change and disposable should not be used anymore.

📦 Which tool/library version are you using?

Java, cucumber-bom:7.12.1

🔬 How could we reproduce it?

See example project https://github.com/mszalbach/CucumberDisposable

Readme shows the difference state outputs when running with different versions.

Run with ./mvnw test

@mpkorstanje
Copy link
Contributor

@jkronegg I think it's worth reverting #2725 now.

@jkronegg
Copy link
Contributor

@mszalbach sorry for the issue. The code repository https://github.com/mszalbach/CucumberDisposable gives me a 404 not found. Can you make the project visible or correct the URL ?

@mszalbach
Copy link
Author

@jkronegg Sorry I thought the repo was already public. That should be fixed now.

@jkronegg
Copy link
Contributor

@jkronegg I think it's worth reverting #2725 now.

As the issue is fixed by #2772, I don't see any advantage to revert #2725. With the original code, the test harness was insufficient: lifecycle events were tested only on the first test scenario, not when using multiple test scenarios.

@jkronegg jkronegg self-assigned this Jun 30, 2023
@jkronegg
Copy link
Contributor

jkronegg commented Jul 2, 2023

@mszalbach thanks for the detailed bug report. This should be corrected with the fresh new Cucumber v7.13.0. Please excuse me for the wasted time.

@mszalbach
Copy link
Author

Thanks a lot. I am looking forward to use this as soon as the release hits Maven central.

@mpkorstanje
Copy link
Contributor

That maybe take a minute. The key expired. https://github.com/cucumber/cucumber-jvm/actions/runs/5437899604/jobs/9888762794

@mpkorstanje
Copy link
Contributor

Release has been made.

@mszalbach
Copy link
Author

Thanks. Release works and my job is back in the green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants