action #44420

action #15132: [saga][epic] Better structure of test plans in main.pm

[functional][y][timeboxed:6h] proof-of-concept of declarative test schedule definition, e.g. in YAML file(s)

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

Status:ResolvedStart date:28/11/2018
Priority:LowDue date:26/02/2019
Assignee:riafarov% Done:

0%

Category:Enhancement to existing tests
Target version:SUSE QA tests - Milestone 23
Difficulty:
Duration: 65

Description

Goal

Show what can be done in a yaml file and have a base for discussion


Related issues

Related to openQA Project - action #16188: Easier way to clone jobs for test development Resolved 23/01/2017
Related to openQA Project - action #46667: Define version-able and human readable format for job sch... Resolved 25/01/2019
Copied to openQA Tests - action #47921: [functional][y] Apply new scheduling mechanism for any in... Resolved 28/11/2018 26/03/2019

History

#2 Updated by okurz about 1 year ago

  • Due date set to 12/02/2019

pre-fill last sprint in M22 with all tickets within milestone not yet assigned to sprints

#3 Updated by okurz about 1 year ago

  • Related to action #16188: Easier way to clone jobs for test development added

#4 Updated by okurz about 1 year ago

  • Status changed from In Progress to Workable
  • Priority changed from Normal to Low

PR has enough feedback but I don't fancy working on this ATM.

#5 Updated by riafarov about 1 year ago

Don't you mind if I take over? I would spend a bit more time on that to provide solution which we could start using at least inside Y-team.

#6 Updated by okurz about 1 year ago

  • Assignee changed from okurz to riafarov

sure, go ahead. I would be happy to see you working based on my ideas or a different approach with own ideas just as same.

#7 Updated by riafarov about 1 year ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6741

We have provided 2 working PoC, so let's gather feedback and decide how to proceed. I've also had a nice conversation with @kalikiana, and on of outcomes was that there might be new layer introduced, so we could introduce settings for combinations of mediums and machines, which would greatly simplify certain scheduling problems like choosing correct bootloader.

#8 Updated by riafarov about 1 year ago

  • Status changed from Workable to Feedback

#9 Updated by riafarov about 1 year ago

  • Due date changed from 12/02/2019 to 26/02/2019

We need more feedback to decide upon follow-up steps.

#10 Updated by cdywan about 1 year ago

  • Related to action #46667: Define version-able and human readable format for job scheduling-related tables added

#11 Updated by riafarov about 1 year ago

  • Copied to action #47921: [functional][y] Apply new scheduling mechanism for any installation scenario in YaST job group which is also executed on o3 added

#12 Updated by okurz about 1 year ago

  • Target version changed from Milestone 22 to Milestone 23

#13 Updated by riafarov about 1 year ago

  • Status changed from Feedback to Resolved

As I've created #47921, I believe this is more than done. So I resolve it.

Also available in: Atom PDF