Project

General

Profile

action #44420

coordination #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 about 3 years ago. Updated 10 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 23
Start date:
2018-11-28
Due date:
% Done:

0%

Estimated time:
Difficulty:

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 developmentResolved2017-01-23

Related to openQA Project - action #46667: Define version-able and human readable format for job scheduling-related tablesResolved2019-01-25

Copied to openQA Tests - action #47921: [functional][y] Apply new scheduling mechanism for any installation scenario in YaST job group which is also executed on o3Resolved2018-11-282019-03-26

History

#2 Updated by okurz almost 3 years ago

  • Due date set to 2019-02-12

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

#3 Updated by okurz almost 3 years ago

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

#4 Updated by okurz almost 3 years 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 almost 3 years 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 almost 3 years 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 almost 3 years 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 almost 3 years ago

  • Status changed from Workable to Feedback

#9 Updated by riafarov almost 3 years ago

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

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

#10 Updated by cdywan almost 3 years ago

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

#11 Updated by riafarov almost 3 years 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 almost 3 years ago

  • Target version changed from Milestone 22 to Milestone 23

#13 Updated by riafarov almost 3 years ago

  • Status changed from Feedback to Resolved

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

#14 Updated by okurz 10 months ago

  • Due date deleted (2019-02-26)

Also available in: Atom PDF