Motivation / Problem

Right now, our QA team tests YaST with OpenQA very much based on keyboard shortcuts: Set the keyboard focus to the "User Name" input field with Alt-U, enter a user name, [Tab] to get to the next field, enter more text, finally Alt-N to activate the "Next" button.

Quite a big part of openQA is testing the installation of SUSE products. All of them are installed by YaST. So a big quantity of problems found during openQA testruns are YaST problems. To find out what has gone wrong during installation YaST developers need to download the tarball containing the logs, unpack it and find the y2log among many other log files. That makes it quite complicated to just have a quick view on a problem.

Deploy an openQA on my locally virtual machine and create 3 openQA test case for nautilus.

A social network for Bugs and test cases! Connecting bugs with test cases, products and each other. Making them depressed and easily mislead. Allowing us to interfere with their elections and sell them solutions to problems they didn't even know they had.

Idea is to write FF plugin which would process raw autoinst log and display it in more readable form .

Project Description

openSUSE claims quite a lot of Arm boards to be supported. But we lack testing on that boards.

Project Description

This Hack Week i want to figure out how to best use Playwright to test Mojolicious applications like openQA in unit tests. Playwright is a (mostly better) alternative to Selenium for browser automation. I'd like to find a way to write entire unit tests in JavaScript, and have those run right next to existing Perl tests with the same test runner using Node Tap and the Test Anything Protocol.