Project

General

Profile

Actions

action #71308

closed

coordination #69130: [functional][y][epic] Extend test coverage for firstboot

[y][timeboxed:20h] Figure out most used module for the first boot

Added by riafarov over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Target version:
Start date:
2020-09-14
Due date:
2020-10-20
% Done:

0%

Estimated time:

Description

We need to decide which modules to enable further and act on those.

We now have test suite with custom xml: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10856

We need to understand how to cover all the modules, which we have for first boot.

Expected outcome of the research:

  1. List of the first boot modules is identified along with conflicting modules/clients and grouping for the test suite is proposed
  2. Priorities are also clarified using data from bugzilla to know which modules/clients are used
  3. Follow-up tickets based on the findings are filed
  4. Details are documented at least in this ticket, so not lost
Actions #1

Updated by riafarov over 4 years ago

  • Subject changed from [y] Figure out most used module for the first boot to [y][timeboxed:20h] Figure out most used module for the first boot
  • Description updated (diff)
  • Assignee deleted (riafarov)
Actions #2

Updated by riafarov over 4 years ago

  • Status changed from New to Workable
Actions #3

Updated by riafarov about 4 years ago

  • Project changed from openQA Tests (public) to qe-yam
  • Category deleted (Spike/Research)
Actions #4

Updated by syrianidou_sofia about 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia
Actions #5

Updated by riafarov about 4 years ago

  • Due date changed from 2020-10-06 to 2020-10-20
Actions #6

Updated by riafarov about 4 years ago

  • Project changed from openQA Tests (public) to qe-yam
Actions #7

Updated by syrianidou_sofia about 4 years ago

After investigating previous bugs on yast2-firstboot, the scenarios for extending the coverage:
1) Enchance yast2_firstboot module to enable inst_lan for network configuration (There could be a bug here. Enabling the module in /etc/YaST2/firstboot.xml doesn't do the trick.)

2) Modify yast2_firstboot_custom test suite, so that different configuration is covered. Replace /etc/sysconfig/firstboot and /etc/YaST2/firstboot.xml files in order for the firstboot to:

  • Display customized welcome message.
  • Change language for both system and keyboard.
  • Set autologin checked by default for new user.
  • Change the current root password.
  • Display customized license.
  • SHOW_Y2CC_CHECKBOX="yes"
  • Display customized finish text.

before proceeding to firstboot configuration, abort and reboot in order to verify that firstboot will run again.

3) Enable yast2_firstboot in textmode with necessary customization, module replacement and new needles.

Actions

Also available in: Atom PDF