Project

General

Profile

Actions
Copy link

action #51470

closed

coordination #51362: [functional][u][epic] Ensure consistence and semantic of INSTALLONLY tests

[functional][u] Research about usage of YML schedule and POST_INSTALLATION to get rid of misused INSTALLONLY setting

Added by SLindoMansilla almost 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
mgriessmeier
Category:
Spike/Research
Target version:
SUSE QA - Milestone 31
Start date:
2019-05-14
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Acceptance criteria

  • AC1-A: It is confirmed that YML schedule can be used.
  • AC1-B: It is confirmed that POST_INSTALLATION can be used.

Tasks

  • Create a sub task of the epic for the implementation
Actions
Copy link
 #1

Updated by SLindoMansilla almost 5 years ago

  • Subject changed from [functional][u] Research about usage of YML schedule to get rid of misused INSTALLONLY setting to [functional][u] Research about usage of YML schedule and POST_INSTALLATION to get rid of misused INSTALLONLY setting
  • Description updated (diff)
Actions
Copy link
 #2

Updated by SLindoMansilla almost 5 years ago

  • Description updated (diff)
  • Category changed from Enhancement to existing tests to Spike/Research
  • Status changed from New to Workable
  • Priority changed from High to Normal
  • Target version set to Milestone 26

As discussed in the grooming meeting, this ticket will only handle research. Please, create another sub task of the epic for the implementation.

Actions
Copy link
 #3

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 26 to Milestone 27
Actions
Copy link
 #4

Updated by SLindoMansilla over 4 years ago

  • Estimated time set to 42.00 h
Actions
Copy link
 #5

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 27 to Milestone 28
Actions
Copy link
 #6

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 28 to Milestone 31
Actions
Copy link
 #7

Updated by SLindoMansilla about 4 years ago

  • Status changed from Workable to Resolved
  • Assignee set to mgriessmeier

Team decided to use YAML schedule

Actions
Copy link

Also available in: Atom PDF