Project

General

Profile

action #62387

easily pluggable reproducer injection

Added by msmeissn over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Support
Target version:
Start date:
2020-01-20
Due date:
2020-04-04
% Done:

0%

Estimated time:
Difficulty:

Description

(This might be a task with a bit more discussion.)

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.


Related issues

Related to openQA Project - action #48644: Dynamic scheduling of small script snippets to execute, e.g. scripts as downloadable assetsNew2018-06-08

History

#1 Updated by okurz over 1 year ago

  • Project changed from openQA Tests to openQA Project
  • Category set to Support
  • Status changed from New to Feedback
  • Assignee set to okurz
  • Target version set to Current Sprint

This is actually a duplicate of #48644 . I have recorded your user story into the other ticket. It is hard to give a generic solution to "just run a script" because the prerequisities might differ a lot, e.g. do you want to boot to a graphical desktop or just textmode. What is already easily possible: With http://open.qa/docs/#_triggering_tests_based_on_an_any_remote_git_refspec_or_open_github_pull_request you can trigger tests easily on production instances where you would just do minor changes to existing tests, e.g. fork https://github.com/os-autoinst/os-autoinst-distri-opensuse , adjust where needed and trigger as described in the docs. You can select "interesting test modules" when triggering tests as well, e.g. then you could add the test parameters "SCHEDULE=tests/boot/boot_to_desktop,tests/my_test" to just execute the two modules for booting and your custom script.

May I ask, what do you need openQA for in this particular case? Why not for example a container or OBS run?

#2 Updated by okurz over 1 year ago

  • Related to action #48644: Dynamic scheduling of small script snippets to execute, e.g. scripts as downloadable assets added

#3 Updated by okurz over 1 year ago

  • Due date set to 2020-04-04

#4 Updated by okurz over 1 year ago

  • Status changed from Feedback to Resolved

see recommendations in #62387#note-1

Also available in: Atom PDF