Testing and Automation
Welcome to KernelCI
You're all welcome to the KernelCI project's new home
KernelCI is a project dedicated to testing the upstream Linux kernel.
Originally created by Linaro in 2014, it started a new chapter by
becoming a Linux Foundation project in October 2019.
Its future looks
bright, with plenty of opportunities for new contributors to join.
The chosen one
The upstream kernel testing landscape is pretty wide, rich and
diverse, in the same ways that the Linux kernel is. But as there is
only one upstream kernel, it became clear that there should also be
one main test system associated with it. KernelCI was chosen to
fulfil this role, being rather neutral, versatile and based on a
distributed architecture.
A welcoming place
While the project now has a governing board via the Linux Foundation
membership, its involvement with the kernel community is only getting
stronger. It is of utmost importance to keep the roadmap aligned with
expectations from maintainers and developers to preserve the integrity
and overall purpose of project. In fact, it now needs to become an
easy tool to use by anyone who wants to add tests for their subsystem
or their hardware and for anyone to reproduce those tests locally.
An exciting year ahead
This is a new beginning for KernelCI, with many of its prior
limitations now being removed thanks to the framework provided by the
Linux Foundation. Contributors to the code, tests, hardware labs and
new project members will all have a great influence by joining the
project at this very special point in time. Now is the time to come
and help shape it as a successful project for the years to come.
Slides: gtucker-kernelci-fosdem-2020.pdf
Additional information
| Type | devroom |
|---|
More sessions
| 2/1/20 |
In this talk we will explore some of the FOSS specific mentalities and practices that may discourage adoption of comprehensive automated testing, and present advice for promoting and sustaining automated testing in FOSS projects.
|
| 2/1/20 |
See how Red Hat’s CKI project uses GitLab CI to test kernel patches as soon as they're posted to maillists.
|
| 2/1/20 |
Overview of SUSE's Linux kernel testing in OpenQA, how we keep track of known issues, explore test results and other features of JDP. The JDP framework is written in Julia, uses Redis as a distributed data cache and Jupyter for interactive reporting. OpenQA is a large application used for testing operating systems and displaying the results.
|
| 2/1/20 |
What benchmark? How many VMs? How big each VM is? Are they all equal or are they different? What's the host OS? What are the guest OSes? I.e., when wanting to do virtualization performance testing, the matrix of test cases tends to explode pretty quickly. This talk will show how we enhanced an existing benchmarking suite, MMTests, in order to be able to deal a little bit better with such complexity. And what our further activities and plans are, for even more and better automation.
|
| 2/1/20 |
OCS stands for Openshift Container storage. It provides container-based storage for OCP(Openshift container platform). It’s easily scalable to bare metal, VMs and cloud platforms. Auto healing is a property of OCS cluster that auto heals a cluster component automatically when passes through an unexpected condition. A component can be a node, a network interface, a service, etc. To make sure auto heals just fine, we introduced negative testing. Negative Testing is defined as, a testing type ...
|
| 2/1/20 |
OpenTAP is a project aimed at automation in the test and measurement space. It is designed for test and measurement of hardware in R&D and manufacturing, but is moving more towards software testing e.g. with usage in cloud infrastructure testing. The project started as an internal product by Keysight Technologies and is used as the core of many products and solutions deployed around the world. As of 2019, we have released OpenTAP under the Mozilla Public License v2 and are working on building a ...
|
| 2/1/20 |
Since several years, software quality tools have evolved, CI systems are more and more scalable, there are more testing libraries than ever and they are more mature than ever and we have seen the rise of new tools to improve the quality of code we craft. Unfortunately, most of our CI system still launch a script and check the return code, most of the testing libraries don't allow to select finely which tests to launch and most of CI advanced innovations, parallel running, and remote execution, ...
|
