Project

General

Profile

Actions

action #150992

closed

coordination #58184: [saga][epic][use case] full version control awareness within openQA

coordination #48641: [epic] Trigger openQA tests in pull requests of any product github pull request

[timeboxed][spike solution:20h] openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-opensuse/ size:M

Added by okurz about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

[timeboxed][spike solution:20h] openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-opensuse/
https://progress.opensuse.org/issues/150992

Motivation

With #126950 we have good experience with automatically triggered openQA tests in pull requests to os-autoinst-distri-openQA. We should now explore triggering openQA tests to os-autoinst-distri-opensuse

Acceptance criteria

  • AC1: New pull requests in github.com/os-autoinst/os-autoinst-distri-opensuse provide feedback to the pull request creator and reviewers from at least one test scenario executed for the pull request before merge

Suggestions

  • Follow the documentation and consider the existing use case in https://github.com/os-autoinst/os-autoinst-distri-example/blob/main/.github/workflows/openqa.yml
  • Read about what needed to be done for #126950 for openQA-in-openQA tests
  • Extend the concept to os-autoinst-distri-opensuse
  • Define one or multiple scenarios that is/are always run, for example "default" or "textmode", maybe configurable? For this task just hardcode
  • Allow an easy way to specify a scenario to run e.g. a validation job or parameters for scheduling
  • Consider to only run a very much stripped down test, e.g. just "boot_to_desktop" of an existing image that takes only 1m and convinces everybody

Out of scope

  • Run workflows on GitLab or involving osd - likely this can be implemented separately

Related issues 3 (1 open2 closed)

Related to openQA Project (public) - action #151249: Cover changed code in PRs on github.com/os-autoinst/os-autoinst-distri-opensuse with openQA test runsNew2023-11-21

Actions
Copied from openQA Project (public) - action #126950: [openQA-in-openQA] openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-openQA/ size:MResolvedjbaier_cz2023-03-30

Actions
Copied to openQA Project (public) - action #152170: Run openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-opensuse/ size:MResolvedokurz

Actions
Actions #1

Updated by okurz about 1 year ago

  • Copied from action #126950: [openQA-in-openQA] openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-openQA/ size:M added
Actions #2

Updated by livdywan about 1 year ago

  • Description updated (diff)
Actions #3

Updated by livdywan about 1 year ago

  • Subject changed from [timeboxed][spike solution:20h] openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-opensuse/ to [timeboxed][spike solution:20h] openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-opensuse/ size:M
  • Description updated (diff)
  • Status changed from New to Workable
  • Assignee set to mkittler
Actions #4

Updated by okurz about 1 year ago

  • Related to action #151249: Cover changed code in PRs on github.com/os-autoinst/os-autoinst-distri-opensuse with openQA test runs added
Actions #5

Updated by mkittler about 1 year ago

  • Status changed from Workable to Feedback

I created https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18182 to implement the last suggestion. I created #151249 for running more useful tests which you've already linked.

Actions #6

Updated by mkittler about 1 year ago

  • Status changed from Feedback to Resolved
Actions #7

Updated by okurz about 1 year ago

  • Copied to action #152170: Run openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-opensuse/ size:M added
Actions #8

Updated by okurz about 1 year ago

Next time please make sure that follow up is planned accordingly. Created now #152170

Actions

Also available in: Atom PDF