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. But one area of weakness is it's usefulness as a testing tool for developers or packagers. openQA can easily test a package once it's INSIDE a distribution, but how do you test that package BEFORE submitting it to the distribution?

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"

COREWAR is a programming game in which two or more programs (warriors or viruses) compete for the control of a virtual computer. The programs are written in Redcode, an abstract assembly language. - Learn about optimizing assembly: reading Redcode guides and manuals (individually or in group)

OpenStack is, undoubtedly, a really huge ecosystem of cooperative services. Rally is a benchmarking tool that answers the question: “How does OpenStack work at scale?”. To make this possible, Rally automates and unifies multi-node OpenStack deployment, cloud verification, benchmarking & profiling. Rally does it in a pluggable way, making it possible to check whether OpenStack is going to work well on, say, a 1k-servers installation under high load. Thus it can be used as a basic tool for an OpenStack CI/CD system that would continuously improve its SLA, performance, and stability. <img src="https://wiki.openstack.org/w/images/thumb/e/ee/Rally-Actions.png/850px-Rally-Actions.png" width="700">

Implement a basic file search for a given OBS project. An example of basic functionality can already be found for Ubuntu or Debian. The goal is to implement,

Features

Nightwatch.js is a Node.js based End-to-End (E2E) testing solution for browser based apps. It's based on Webdrive, meaning it's a very reliable way for me to test HAWK UI! It's a great opportunity to learn Webpack, PhantomJS nightwatch and to set up a TDD approach with any new features written with vue.js, the framework which we will be using in HAWK from now on.

The purpose of this project is to implement an Android application which shows some images (or dice) which you must use to create a short story. The requirements and desired features for the app are:

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. Part1:

I want to use this Hackweek to explore (Functional) Reactive Programming to be able to use it in my day-to-day work. This includes checking out basic literature about (F)RP as well as domain modelling to get a better understanding, when this paradigm makes sense to use, as well as looking into concrete implementation of (F)RP libraries.

Take the source rpm of a package (e.g. systemd), find the upstream tests, run them, store the results to a database that a web ui can access and display them. Now, do this automatically, for every qam-sle update.