Actions
action #36994
closedDynamic test flow definition + override
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
SUSE QA (private) - Milestone 25
Start date:
2018-06-08
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
Linked to UC4 as well as UC7. As a bug assignee or QA contact I want openQA to execute a custom scenario with only limited test modules and optional override test or investigation code to be able to reproduce bugs easily which are most easily or only reproduced in openQA context without needing to adapt the normal validation test code
Acceptance criteria¶
- AC1: A list of test modules to be scheduled can be specified on job trigger time overriding main.pm
- AC2: Override code for test modules can be specified
- AC3: New test modules can be defined
Suggestions¶
- openQA workers download additional test assets if specified by variables to allow injecting new test modules or override modules on-the-fly before isotovideo is called, e.g. using the existing openQA feature of downloading test assets using variables which specify the '_URL' suffix on test parameters.
- A test schedule can be specified completely by a test variable, e.g.
MODULES=boot/boot_to_desktop,qa_automation/patch_and_reboot,my_code
, skipping over all other loadtest calls loadtest
within main.pm looks in the pool directory if any override exists and loads that with preference over any that is specified in the test distribution. This should also work if the specified module does not even exist in the test distribution
Further details¶
Keep security considerations in mind, e.g. do not just allow everybody to execute random code from untrusted remote sources. openQA using the _URL
test variables already checks against a "whitelist" of trusted sources so maybe we are covered already.
Actions