-
Epic
-
Resolution: Can't Do
-
Normal
-
None
-
None
-
Evaluate and improve upstream CI coverage of barbican operator
-
False
-
-
False
-
-
?
-
No Docs Impact
-
OSPRH-4834 - Barbican Improvement
-
?
-
?
-
0% To Do, 0% In Progress, 100% Done
-
-
-
DFG Security: UC Sprint 86, DFG Security: UC Sprint 88, DFG Security: UC Sprint 91, DFG Security: UC Sprint 92
-
2023Q4
The barbican-operator will need full CI upstream including tempest unit tests
- Functional Testing
- KUTTL Testing
- Tempest Testing
- Code will need to be added for all of the services to communicate with barbican as it is required in OSO.
- Tempest tests run within the openstack-operator
- These indirectly test the barbican-operator
- Should we run the full suite of barbican tests within the openstack-operator?
- If not, where should those tests run?
- Determine the best place, how and where to run the barbican tempest tests.
- Tempest tests run within the openstack-operator
- Code will need to be added for all of the services to communicate with barbican as it is required in OSO.
There are no Sub-Tasks for this issue.
