QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Motivation¶

There is a new option in grub for the Live ISO to test a Rescue system in Agama.
Basically mask all services (you can see that editing the grub entry).

References:
https://trello.com/c/Kgaovgu8/4810-1-friday-aft-task-feat-rescue-system-menu-entry
https://confluence.suse.com/pages/viewpage.action?pageId=1806565501

Question is, can we make this e2e scenario a bit more realistic, like once we login using the rescue entry, mount another system chroot to repair it at least checking that we have tools like e2fsck, fsck.

Scope¶

Apparently should be available for all archs except s390x.

Regarding booting it would require some adjustment in our Page Object in similar fashion than for check media.

Acceptance criteria¶

• AC1: Compare with the Rescue system in YaST installer and share doubt or missing functionality with developers.
• AC2: Automate rescue system option in Agama being able to use new grub entry and validate that those masked services are not started in the rescue system.
• AC3: Consider for further validation to be able to fix a system, just being able to mount it, chroot and check that the tools (research which ones) are available for this.