Project

General

Profile

Actions

action #50723

closed

[functional][y] Automate yast2 hostname using libyui-rest-api for tumbleweed

Added by riafarov over 5 years ago. Updated 10 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2019-04-25
Due date:
% Done:

0%

Estimated time:

Description

Motivation

I, as a QA engineer would like to learn potential issues when running tests using new framework vs needles

Documentation for the framework can be found here: https://github.com/libyui/libyui-rest-api

Idea is to write test for the module which already has automated test and run both for some time and compare efforts for the maintenance and review.

Acceptance criteria

  1. Test for yast2 hostname using libyui-rest-api is running in parallel to screen based test

Related issues 1 (0 open1 closed)

Blocked by qe-yam - action #50726: [functional][y][timeboxed:16h] Explore different ideas which technologies to use with libyui-rest-apiResolvedJERiveraMoya2019-04-252019-07-16

Actions
Actions #1

Updated by riafarov over 5 years ago

#50726 should be resolved first, so in case it's not, please, move to the next sprint.

Actions #2

Updated by riafarov over 5 years ago

  • Due date changed from 2019-06-04 to 2019-06-18
Actions #3

Updated by riafarov over 5 years ago

  • Blocked by action #50726: [functional][y][timeboxed:16h] Explore different ideas which technologies to use with libyui-rest-api added
Actions #4

Updated by riafarov over 5 years ago

  • Status changed from New to Blocked
  • Assignee set to riafarov
Actions #5

Updated by riafarov over 5 years ago

  • Due date changed from 2019-06-18 to 2019-07-30
  • Target version set to Milestone 27
Actions #6

Updated by riafarov over 5 years ago

  • Due date changed from 2019-07-30 to 2019-09-24
  • Target version changed from Milestone 27 to Milestone 30+
Actions #7

Updated by riafarov about 5 years ago

  • Due date changed from 2019-09-24 to 2019-10-22

We are getting closer, but not in the next sprint.

Actions #8

Updated by riafarov about 5 years ago

  • Due date changed from 2019-10-22 to 2019-11-19
Actions #9

Updated by riafarov about 5 years ago

  • Due date changed from 2019-11-19 to 2020-02-11
Actions #10

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

Actions #11

Updated by riafarov almost 5 years ago

  • Due date changed from 2020-02-11 to 2020-04-07
  • Target version changed from Milestone 30 to Milestone 33
Actions #12

Updated by riafarov over 4 years ago

  • Due date deleted (2020-04-07)
Actions #13

Updated by riafarov over 4 years ago

  • Target version changed from Milestone 33 to future
Actions #14

Updated by riafarov about 4 years ago

  • Project changed from openQA Tests to qe-yam
  • Status changed from Blocked to New
  • Assignee deleted (riafarov)
Actions #15

Updated by okurz about 3 years ago

  • Priority changed from Normal to Low

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. The ticket will be set to the next lower priority of "Low" as discussed with qe-yast PO oorlov (https://suse.slack.com/archives/C02LECV2R0X/p1636974668013200)

Actions #16

Updated by JERiveraMoya 11 months ago

  • Target version deleted (future)
Actions #17

Updated by JERiveraMoya 11 months ago

  • Parent task deleted (#50672)
Actions #18

Updated by JERiveraMoya 10 months ago

  • Status changed from New to Rejected

Backlog clean-up.

Actions

Also available in: Atom PDF