Skip to content
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

[WIP][DISCUSSION] Fully replace QA_TESTSUITE approach by QA_TESTSET #6955

Closed
wants to merge 1 commit into from

Commits on Mar 4, 2019

  1. [WIP][DISCUSSION] Fully replace QA_TESTSUITE approach by QA_TESTSET

    os-autoinst#4132 with title
    "qa_automation: add new design for QA:HEAD tests" added the use of the test
    variable QA_TESTSUITE whereas qam uses QA_TESTSET only. Checked with
    https://github.com/okurz/scripts/blob/master/openqa-db_query_last_use_of_module
    and found no QAM job running execute_test_run.
    https://openqa.suse.de/admin/test_suites shows that there are mainly QAM jobs
    using QA_TESTSET however some others as well. QA_TESTSUITE is not used for
    anything with a prefix like "qam". To me it looks like both are doing more or
    less the equivalent except that based on QA_TESTSET shows the output of
    individual test modules and also there is no module "execute_test_run" that
    would fail and is hard to label.
    
    The approach based on QA_TESTSET seems to provide much better visualization of
    test results using the more recent openQA feature to show "External results".
    
    Related progress issue: https://progress.opensuse.org/issues/44138
    okurz committed Mar 4, 2019
    Copy the full SHA
    beeff44 View commit details
    Browse the repository at this point in the history