action #48644
Updated by okurz about 4 years ago
## Motivation
Linked to [UC4](https://progress.opensuse.org/projects/openqav3/wiki#Use-case-4) as well as [UC7](https://progress.opensuse.org/projects/openqav3/wiki#Use-case-7). 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 and not needing a complete fork of [gh#os-autoinst/os-autoinst-distri-opensuse](https://github.com/os-autoinst/os-autoinst-distri-opensuse)
## Acceptance criteria
* **AC1:** Override code for test modules or parts of test modules can be specified as downloadable asset
## 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.
## Further details
From #62387 "easily pluggable reproducer injection"
From security point of view, we occasionaly want to add security reproducer testcases easily to openqa.
one case would be e.g. ImageMagick and GraphicsMagick.
Here our security reproducers usually fall into:
* identify IMAGE -> crash
* valgrind identify IMAGE -> valgrind errors / and leaks
* convert IMAGE output.jpg -> crash
* valgrind convert IMAGE output.jpg -> valgrind errors / and leaks
As there is a small number of possible testscenarios adding of testimages could even be done without any adjustments to run scripts, or more trivial adjustments.
So something in the form of "data/imagemagick/bg_script.sh", but more simple.
What I want to avoid is that we need to setup our own openqa just to test it, but more throw it over the fence style submissions.