Project

General

Profile

action #50723

coordination #36712: [saga] Use YaST specific framework for GUI testing

coordination #50672: [funtional][y][epic] Use libyui-rest-api for YaST modules testing

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

Added by riafarov over 2 years ago. Updated 23 days ago.

Status:
New
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

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

History

#1 Updated by riafarov over 2 years ago

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

#2 Updated by riafarov over 2 years ago

  • Due date changed from 2019-06-04 to 2019-06-18

#3 Updated by riafarov over 2 years ago

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

#4 Updated by riafarov over 2 years ago

  • Status changed from New to Blocked
  • Assignee set to riafarov

#5 Updated by riafarov over 2 years ago

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

#6 Updated by riafarov over 2 years ago

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

#7 Updated by riafarov about 2 years ago

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

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

#8 Updated by riafarov about 2 years ago

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

#9 Updated by riafarov about 2 years ago

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

#10 Updated by mgriessmeier almost 2 years ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

#11 Updated by riafarov almost 2 years ago

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

#12 Updated by riafarov over 1 year ago

  • Due date deleted (2020-04-07)

#13 Updated by riafarov over 1 year ago

  • Target version changed from Milestone 33 to future

#14 Updated by riafarov about 1 year ago

  • Project changed from openQA Tests to qe-yast
  • Status changed from Blocked to New
  • Assignee deleted (riafarov)

#15 Updated by okurz 23 days 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)

Also available in: Atom PDF