Project

General

Profile

action #32149

Create ay using customer profile to track regression from bsc#954908

Added by riafarov almost 5 years ago. Updated 10 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
2018-02-22
Due date:
% Done:

0%

Estimated time:

Description

We have a profile in https://bugzilla.suse.com/show_bug.cgi?id=954908 which didn't work well. To verify that we don't get this regression again, we should add integration test using profile from that.

Acceptance criteria

  1. AY integration test based on given profile is added
  2. Test suite is enabled and works for SLE 12 and SLE 15

History

#1 Updated by riafarov almost 5 years ago

  • Target version changed from Milestone 16 to Milestone 17

#2 Updated by okurz over 4 years ago

  • Subject changed from [sle][functional][yast][bsc#954908][regression] create ay using customer profile to track regression from bsc#954908 to [sle][functional][y][yast][bsc#954908][regression] create ay using customer profile to track regression from bsc#954908

#3 Updated by okurz over 4 years ago

  • Target version changed from Milestone 17 to Milestone 21+

#4 Updated by okurz over 4 years ago

  • Target version changed from Milestone 21+ to Milestone 21+

#5 Updated by okurz about 4 years ago

  • Target version changed from Milestone 21+ to future

#6 Updated by riafarov over 2 years ago

  • Project changed from openQA Tests to qe-yam
  • Subject changed from [sle][functional][y][yast][bsc#954908][regression] create ay using customer profile to track regression from bsc#954908 to Create ay using customer profile to track regression from bsc#954908
  • Category deleted (New test)

#7 Updated by okurz about 1 year ago

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).

#8 Updated by slo-gin 10 days ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Also available in: Atom PDF