-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
storage-no-skips
-
Product / Portfolio Work
-
77
-
- Storage tests are explicitly selected to run based on what is meant to be tested without skipping based on runtime information.
- no-doc
- no-ux
-
Green
-
To Do
-
VIRTSTRAT-334 - 2024 Code Quality
-
-
43% To Do, 14% In Progress, 43% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
-
Goal
Have zero (0) programmatic skips in our T1 and T2 test code.
User Stories
- As a CNV tester I would like to run a subset of the my tests (e.g snapshot-related tests) on a cluster. If the cluster does not have the required hardware/configuration for the test to pass, the test must fail rather than silently skipped. If I want to run the storage test suite on such cluster, I must explicitly deselect snapshot-related tests.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
kubevirt$ (cd tests/storage; git grep -E 'Skip\(|checks\.' | wc -l)
74
There should be none.
- blocks
-
VIRTSTRAT-515 Establish and Achieve Quality and Stability Metrics in v4.21
-
- New
-
- clones
-
-
- New
-
- is cloned by
-
-
- New
-
1.
|
upstream roadmap issue |
|
New | 
|
Unassigned |
2.
|
upstream design |
|
New |
|
Unassigned |
3.
|
upstream documentation |
|
New |
|
Unassigned |
4.
|
upgrade consideration |
|
New |
|
Unassigned |
5.
|
test plans in polarion |
|
New |
|
Unassigned |
6.
|
automated tests |
|
New |
|
Unassigned |
7.
|
downstream documentation merged |
|
New |
|
Unassigned |