QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Motivation¶

As settings seems to be the preferred way to do this, because they are set in mediums and we might need even pair of settings from two different products in the same job, for example for migration, we can remove this functionality. Referring to this:
my $addons = get_test_suite_data()->{addons}; in console/scc_cleanup_reregister.pm
Next function will use SCC_ADDONS by default internally.
Check where this was used with test data and change it so we simplify this module.

Acceptance criteria¶

• AC1: Addons are provided via settings and not via test data mechanism.
• AC2: Other uses of this test module where test data is passed are changed to use settings instead.