action #110236: Create unit test for YAML schedule with reusable flows - qe-yam - openSUSE Project Management Tool

Actions

Copy link

action #110236

closed

coordination #104829: [Epic] Improve schedules for test suite in YaST group

Create unit test for YAML schedule with reusable flows

Added by JERiveraMoya over 2 years ago. Updated over 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

rainerkoenig

Target version:

Current

Start date:

2022-04-25

Due date:

% Done:

Estimated time:

Description

Motivation¶

We need some basic unit testing coverage for new feature that reuse flows to schedule modules via YAML files.

Acceptance criteria¶

AC1: Unit testing covering positive and negative cases in t/ folder.

Suggestions¶

For positive cases we could just create mini schedules/defaults/flows files and check for expected list of modules.
Consider the case where we overwrite the same key in more than one file.
For negative cases we should check for potential errors, keys which do not exists, openQA settings not provided.

Further info¶

PR where new feature was introduced: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14241

Actions

Copy link

Updated by JERiveraMoya over 2 years ago

Description updated (diff)

Actions

Copy link

Updated by JERiveraMoya over 2 years ago

Tags deleted (~~qe-yast-refinement~~)
Status changed from New to Workable

Actions

Copy link

Updated by JERiveraMoya over 2 years ago

Priority changed from High to Normal

Actions

Copy link

Updated by tinawang123 over 2 years ago

Assignee set to tinawang123

Actions

Copy link

Updated by tinawang123 over 2 years ago

Status changed from Workable to In Progress

Actions

Copy link

Updated by tinawang123 over 2 years ago

Status changed from In Progress to Blocked

Set it to blocked as not understand the description.

Actions

Copy link

Updated by JERiveraMoya over 2 years ago

Status changed from Blocked to Workable
Assignee deleted (~~tinawang123~~)

We don't use status 'Blocked' anymore, as we should not be blocked by our own internal dependencies.
In this case assuming nobody in the team could help you with this (which surprise me ...but we are in summer season) we should set "New" and apply tag again with "qe-yast-refinement'. But in this case as I'm pretty sure others could help you, I will just set to workable and unassigned.

Actions

Copy link