Projects in the topic openqa
openQA is an automated test tool for operating systems and the engine at the heart of op

Today OpenQA mostly runs on virtual machines, but it can get really tricky to find bugs triggered by real hardware. There are only few interfaces required to interact with a machine though:

using perl's Inline::Python module, it should be possible to define openQA test modules in python instead of perl.

SCC doesn't require an email address, so could you automatically generate random keys until one matches and effectively 'steal' SCC licenses from customers?

CodeMirror is a text editor implemented in JavaScript for the browser, openQA introduced CodeMirror in its source viewer, this project is learn more things from CodeMirror and trying to improving the source viewer in openQA, already had a ticket related, even can polish source viewer more, eg. file folding, etc.

To make OpenQA work with real ARM devices, we need to control

There is a running gag built into openQA called interactive mode. It goes like this: "if you need the interactive mode, it's broken". The reason: the so called interactive mode is a collection of hacks - in theory making it possible to update needles in a running test.

This is an idea that's been kicking around for a while... maybe it's finally time to "make it so."

openQA has a well earned reputation as a 'full system' testing tool, able to test a system end-to-end from the operating system to it's applications on a number of different platforms and architectures, including VM's & Bare Metal.

1. currently when you navigate to Test Results page - it will load everything before show you the page. I plan to change this model into "load on demand" approach
2. Test Details page currently show you thumbnails for all modules. Want to add expand/collapse functionality for thumbnails - by default you will not see them for passed modules. But you will have ability to expand them. Also I will add "Expand All"/"Collapse All"

HTTPBoot was added into UEFI SPEC since 2.5. It aims to replace PXE and provides more features. Actually, the concept of HTTPBoot is similar to PXE. It starts with the HTTP URL from the DHCP server and fetches the data with the HTTP protocol. The key difference between HTTPBoot and PXE is the support of DNS. With DNS, the firmware and the bootloader can resolve the domain name so it's possible to pass the well-known URL to download the image instead of the explicit IP URL. Besides, HTTP is designed to cross different domains, while tftp (PXE) is only for the local network.