Cleanup #47160
Updated by Ramana Raja over 3 years ago
The test_volumes has become unwieldy with growing number of non-trivial tests to test growing set of features in mgr/volumes. Adding/reviewing tests during code development and tracking down qa test run failures has become harder. Solution as As per Patrick Donnelly: "To " To be clear: this is as simple as breaking the volumes tests into separate classes in teh same file. Then the yaml fragment [1] would be split into multiple yaml fragments that each refer to a specific class of tests." [1] https://github.com/ceph/ceph/blob/d2a3fcc728c31b25166aeb55c99b9ccf8d4985bb/qa/suites/fs/basic_functional/tasks/volumes.yaml#L20