Project

General

Profile

action #33931

[sle][functional][yast][y][easy] verify that there is no "No textdomain configured" text in the y2log

Added by riafarov about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Start date:
2018-03-28
Due date:
2018-05-08
% Done:

0%

Estimated time:
Difficulty:
easy
Duration: 30

Description

Motivation

"No textdomain configured" warning is critical one and means that dialog cannot work properly. Even though it can get unnoticed, or led to behavior which is not that easy to link to root problem.
As a request from YaST team (namely lslezak), we want to check that there is no such a warning in the yast logs.

Tasks

  1. Understand how investigate_yast2_failure works in opensusbasetest and integrate these parts together
  2. Introduce check after we conduct installation for all sle scenarios (ay, upgrades, migration, etc.) and fail test module if problem is detected (but don't fail the test suite, check that fatal flag is not set for test module)
  3. Introduce separate test suite which opens as many dialogs as feasible (no changes are required) to increase chances of finding such a problem and assert that warning is not in the yast logs (INSTALLONLY scenario)

Acceptance criteria

  1. "No textdomain configured" warnings are detected by openQA and are not hidden

Further details

Keep in mind that there will be more checks like this, so we should think of scalable solution where we can easily add text and handle those scenarios

History

#1 Updated by riafarov about 2 years ago

  • Subject changed from [sle][functional][yast] verify that there is no "No textdomain configured" text in the y2log to [sle][functional][yast][y] verify that there is no "No textdomain configured" text in the y2log
  • Description updated (diff)
  • Due date set to 2018-05-08
  • Category set to New test
  • Status changed from New to Workable
  • Target version set to Milestone 15

#2 Updated by okurz about 2 years ago

  • Target version changed from Milestone 15 to Milestone 16

Correcting milestone

#3 Updated by okurz about 2 years ago

  • Subject changed from [sle][functional][yast][y] verify that there is no "No textdomain configured" text in the y2log to [sle][functional][yast][y][easy] verify that there is no "No textdomain configured" text in the y2log
  • Difficulty set to easy

#4 Updated by JERiveraMoya about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya

#5 Updated by JERiveraMoya about 2 years ago

On Installation we already have a module logs_from_installation_system without fatal flag, which calls save_upload_y2logs which calls investigate_yast2_failure where we can refactor for being more scalable:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4958

#6 Updated by JERiveraMoya about 2 years ago

  • Status changed from In Progress to Feedback

#7 Updated by JERiveraMoya about 2 years ago

According the developer, this warning is logged when the YaST code tries to use a translation (via () method) but the text domain has not been set (yet) so YaST does not know which .mo file to use, and because the translations (()) are mainly used in UI we need to open some dialogs to have good test coverage.
For an specific test which whould fail hard, just to not overlook those soft-failures, I chose configuration from test suite RAID=0, as contains many dialogs. Added to OSD new test suite detect_yast2_failures with settings FATAL=1 INSTALLONLY=1 RAIDLEVEL=0
PR for including FATAL setting: (in progress)

#8 Updated by JERiveraMoya about 2 years ago

  • Status changed from Feedback to In Progress

#9 Updated by JERiveraMoya about 2 years ago

  • Status changed from In Progress to Feedback

#10 Updated by JERiveraMoya about 2 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF