Sequence of test execution in framework does not make sense
Closed this issue · 2 comments
In the current state of things, many gluster-related operations (e.g. peer probe, volume creation, mount) are being performed by complex tests, before these operations are actually being tested by the basic (unit) tests.
This means that if a bug exist in these basic operation, instead of having a basic (unit) test fail, a complex test will fail, which makes the basic (unit) tests pretty useless.
The proper sequence of events is for the framework to start by running tests for the most basic operations and then progress to running complex tests which involves multiple, more basic operations.
Thank you for your contributions.
Noticed that this issue is not having any activity in last 3 months! We are marking this issue as stale because it has not had any recent activity and we have decided not to fix it while triaging.
It will be closed in 14 days if no one responds with a comment here.
Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to reopen it.