Project

General

Profile

coordination #38876

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

[functional][y][epic] Automate yast2 hostname test suite using YaST framework which is not relying on shortcuts

Added by riafarov over 3 years ago. Updated about 1 year ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
SUSE QA - Milestone 22
Start date:
2018-06-13
Due date:
2019-01-11
% Done:

100%

Estimated time:
(Total: 13.00 h)

Description

Motivation

As an outcome of #37324, we should start with simpler things to get results before investing to much time in the long-term solution due to missing details.

yast2 hostname is one of the simplest test modules, the only missing functionality from YCP testing framework is work with tables.
Therefore, first task would be to implement this functionality in libyui for ncurses/qt/gtk first and then extend it.

Acceptance criteria

  1. yast2 hostname is tested using YaST specific GUI testing framework

Suggestions

We already have many parts included in YCP, which can be reused, but technical solution should take into consideration that it may get dropped and replaced with ruby,
so framework has to be extended in that way, that these parts can be reused. Consult with YaST team about the details.


Subtasks

action #37327: [sle][functional][y] Improve YaST GUI testing framework to operate on tablesResolvedcwh

action #38879: [functional][y] Implement yast2 hostname test using ncurses with YCPRejected

History

#1 Updated by riafarov over 3 years ago

  • Subject changed from [functional][y][epic] Automate yast2 hostname test suite using YCP player framework to [functional][y][epic] Automate yast2 hostname test suite using YaST framework which is not relying on shortcuts
  • Description updated (diff)

#2 Updated by riafarov over 3 years ago

  • Due date changed from 2018-12-31 to 2018-08-28

due to changes in a related task

#3 Updated by okurz over 3 years ago

  • Category set to Enhancement to existing tests
  • Target version set to Milestone 18

#4 Updated by okurz over 3 years ago

  • Due date changed from 2018-08-28 to 2018-10-15

due to changes in a related task

#5 Updated by okurz over 3 years ago

  • Target version changed from Milestone 18 to Milestone 20

#6 Updated by riafarov over 3 years ago

  • Due date changed from 2018-10-15 to 2018-11-02

due to changes in a related task

#7 Updated by riafarov over 3 years ago

  • Due date changed from 2018-11-02 to 2018-11-16

due to changes in a related task

#8 Updated by riafarov about 3 years ago

  • Due date changed from 2018-11-16 to 2018-08-06

due to changes in a related task

#9 Updated by riafarov about 3 years ago

  • Due date changed from 2018-08-06 to 2018-12-14

due to changes in a related task

#10 Updated by riafarov about 3 years ago

  • Due date changed from 2018-12-14 to 2018-12-28

due to changes in a related task

#11 Updated by okurz about 3 years ago

  • Target version changed from Milestone 20 to Milestone 21

#12 Updated by riafarov about 3 years ago

  • Due date changed from 2018-12-28 to 2019-01-11

due to changes in a related task

#13 Updated by riafarov about 3 years ago

  • Copied to coordination #43742: [functional][y][epic] Separate YaST UI framework to individual project added

#14 Updated by riafarov about 3 years ago

  • Copied to deleted (coordination #43742: [functional][y][epic] Separate YaST UI framework to individual project)

#15 Updated by riafarov almost 3 years ago

  • Due date changed from 2019-01-11 to 2019-01-15

due to changes in a related task

#16 Updated by okurz almost 3 years ago

  • Target version changed from Milestone 21 to Milestone 22

#17 Updated by riafarov almost 3 years ago

  • Due date changed from 2019-01-15 to 2019-01-29

due to changes in a related task

#18 Updated by okurz almost 3 years ago

@riarafov could you please help link this epic without any left open subtasks accordingly to the other tickets referenced in the parent ticket? Or would you also reject this one in favor of the others?

#19 Updated by riafarov almost 3 years ago

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

okurz wrote:

@riarafov could you please help link this epic without any left open subtasks accordingly to the other tickets referenced in the parent ticket? Or would you also reject this one in favor of the others?

To be honest, I considered rejecting it when I saw it, as it considered completely different strategy. I still believe hostname is a good candidate to start with. But let's reject it for now.

#20 Updated by szarate about 1 year ago

  • Tracker changed from action to coordination

Also available in: Atom PDF