-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Improved Subtest-bypass control #125
Comments
Enabling tests via ``--args`` on autotest command line or running all tests is default. No convenient way to disable a test from inside dockertest. The new ``disabled`` option, accepts subtest or subsubtest CSV to bypass. Signed-off-by: Chris Evich <cevich@redhat.com>
dang, in fact, we can't have |
To address #114, one idea might be to use a special character like "~" to invert meaning of |
This issue has been resolved by extending |
In
0.7.x
we have adisabled
CSV list that can be more or less hard-coded to force subtests and sub-subtests to raiseTestNAError
. However this is exploiting faulty logic (this exception is suppose to be a signal for environment or pre-requesite problems). The central issue is we have no access to read from configuration within thecontrol
file, and no existing way to pass information fromcontrol
into subtests.One possible way we can resolve this, is if the
control
file is given write-only access to record informational/advisory values into a dedicated config. file. In other words, every time the harness runs,control
could write a newconfig_custom/control.ini
. This could then be consulted by subtests/sub-subtests to consider appropriate action.The text was updated successfully, but these errors were encountered: