Project

General

Profile

Actions

action #89938

closed

Implement single and stable way to check if YaST module is closed

Added by oorlov about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
SUSE QA - SLE 15 SP3
Start date:
2021-03-11
Due date:
% Done:

0%

Estimated time:

Description

Motivation

There are a lot of cases when test has to wait for module to be closed, e.g. test changes something in YaST module, then closes the module and has to check in console that the changes were applied.

Right now there is no single way to check that the app is closed - almost all the ways (if not all) are using needles. And for all the different cases the appropriate needles should be created. In order to reduce the amount of used needles and to make tests more abstract and stable regardless of the UI state, there should be a way to determine if a module is closed.

Task

  1. Implement ability to check if YaST module is closed;
  2. Use this method in the existing test modules that validates YaST modules (yast2_lan_hostname_dhcp_no, yast2_lan_hostname_dhcp_yes, yast2_lan_hostname_dhcp_yes_eth);
  3. Possible place to keep this method is YaST::Module class.
Actions #1

Updated by riafarov about 3 years ago

  • Target version set to SLE 15 SP3
Actions #2

Updated by riafarov about 3 years ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions #3

Updated by JERiveraMoya almost 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya
Actions #4

Updated by JERiveraMoya almost 3 years ago

  • Status changed from In Progress to Feedback
Actions #6

Updated by JERiveraMoya almost 3 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF