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

State held by beans in tests #607

Open
shawkins opened this issue Dec 15, 2021 · 2 comments
Open

State held by beans in tests #607

shawkins opened this issue Dec 15, 2021 · 2 comments

Comments

@shawkins
Copy link
Contributor

shawkins commented Dec 15, 2021

Similar to the issue of having a module wide mock server, it appears that other beans default to this as well:

If you run
mvn install -Dtest=KafkaClusterTest,IngressControllerManagerTest

You'll see the test issue that I had thought clearing the mock server state would address - occurred here after clearing the state https://github.com/bf2fc6cc711aee1a0c2a/kas-fleetshard/runs/4529467650?check_suite_focus=true

@shawkins
Copy link
Contributor Author

I guess I should have assumed this was the behavior after seeing the default for test resources. There doesn't appear to be a simple workaround. For example we could try to use a profile then it will force Quarkus to restart - but only if the profile is different between affected tests and we previously saw that we couldn't have more than 1 profile or even reuse the same profile. So we'll likely need to add methods to reset the bean state and log an upstream issue.

@shawkins
Copy link
Contributor Author

shawkins commented Mar 6, 2023

This will be addressed by fabric8 6

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

No branches or pull requests

1 participant