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

Remove redundant tests from InfinispanOperatorProvisionerTests #173

Open
fabiobrz opened this issue May 14, 2024 · 1 comment
Open

Remove redundant tests from InfinispanOperatorProvisionerTests #173

fabiobrz opened this issue May 14, 2024 · 1 comment

Comments

@fabiobrz
Copy link
Member

Remove redundant tests from InfinispanOperatorProvisionerTests, i.e. those testing the Java models can be merged into a single test method, using a single application. Also the basicProvisioningTest() method should be deleted and the test coverage for the lifecycle should be moved into ProvisionerCleanupTestCase (once renamed).

--

  • Environment: testsuite/integration-tests
  • Steps to reproduce: run integration tests.
@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Sep 19, 2024
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 19, 2024
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Oct 19, 2024
@fabiobrz fabiobrz reopened this Oct 19, 2024
Copy link

dosubot bot commented Jan 20, 2025

Hi, @fabiobrz. I'm Dosu, and I'm helping the intersmash team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Proposal to optimize InfinispanOperatorProvisionerTests.
  • Suggests consolidating Java model tests into a single method.
  • Recommends eliminating the basicProvisioningTest() method.
  • Suggests transferring lifecycle test coverage to ProvisionerCleanupTestCase.
  • No comments or further activity since the issue was opened.

Next Steps:

  • Is this issue still relevant to the latest version of the intersmash repository? If so, please comment to keep the discussion open.
  • If there is no further activity, the issue will be automatically closed in 30 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Jan 20, 2025
@fabiobrz fabiobrz removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Jan 21, 2025
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