Provisioner test coverage overlapping

[fabiobrz]

We have some overlapping in provisioning test coverage. Mostly in ProvisionerCleanupTestCase vs. *ProvisionerTest::basicProvisioningTest.

ProvisionerCleanupTestCase::undeploy is expected to be testing the full lifecycle (configure->predeploy->deploy->postUndeploy->dismiss) for each operator in order to verify that the namespace is left clean after it. Currently this is implemented to work just for a few provisioners, but we want for such test coverage to be applied to all of the supported provisioners.

On the other side, almost each provisioner is also tested for it's lifecycle to be properly working by a *ProvisionerTest::basicProvisioningTest, e.g.: ActiveMQOperatorProvisionerTest::basicProvisioningTest.

Optimizing this by removing the overlapping would make the test suite run faster.

---

• Environment: testsuite
• Steps to reproduce: N/A

[dosubot]

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

Issue Summary:

• The issue highlights overlapping test coverage in the provisioning tests.
• Redundancy exists between ProvisionerCleanupTestCase and *ProvisionerTest::basicProvisioningTest.
• The goal is to optimize the test suite by removing this overlap to improve efficiency.
• No comments or further activity have been made on this issue.

Next Steps:

• Please confirm if this issue is still relevant to the latest version of the intersmash repository by commenting on this issue.
• If no further activity occurs, this issue will be automatically closed in 30 days.

Thank you for your understanding and contribution!