XLibre Test Drivers

Welcome to the XLibre Test Drivers! This program is designed to get us all involved in making XLibre better software for everyone.

If you already know the program, you may want to skip to the List of Test Drivers. If you are unsure whether to add something or make a change to this page, just talk about it.

Background

Due to the sheer amount of hardware architectures, operating systems, distributions, compilers, libraries, graphics cards, X11 clients, and everything else out there, it is nearly impossible to test all these combinations with a finite number of developers. But on the other hand, we can distribute the testing effort among each of us in addition to the developer tests.

So the idea was born that every test driver tests their specific and beloved setup on the hardware they already own and everything else at their fingertips. Preferably during normal use to keep the effort involved to a minimum. Overall, these individual and highly specific tests can thus deliver comprehensive results and a broad coverage, closing the gaps and squashing even hidden bugs.

The Test Driving Process

As soon as a new feature has been developed or a new version of XLibre is due, the test drivers will be kindly asked in the corresponding issues whether they can test them on their machine. When handing over the issue, specific steps are described as to what needs to be done. The selection of the involved test drivers will be made taking into account the respective requirements in accordance with the information in the table below.

To provide the software under test, we are looking into creating easily usable beta package repositories. In the cases where this is not feasible, we will provide detailed build instructions. In the future, we also want to develop dedicated test cases and request them specifically with the option to automatically run them locally.

Of course, this is all voluntary, and each test driver can decide on a case-by-case basis whether they want to participate.

Becoming a Test Driver

To become a test driver, please add your Github handle, short description of hardware and distribution to the list. If you have some special use case like a not so common C library, non GCC compiler, utilization of specific hardware features, APIs or platforms like Nvidia CUDA etc., then please add this information to your row too. Thank you very much. Now get your helmet ready and check your seatbelt! ;-)

List of Test Drivers

Tester	Hardware	Distro	special use case
@AmerXz	Intel hd 4600 + Nvidia Gtx 765M	Gentoo	Nvidia 470 hybrid , 3D Games
@callmetango	Intel Alder Lake-P GT2	Gentoo	musl libc
@kake26	Intel Kaby Lake i5-8350U	Devuan	Touchscreen
@hendrack	Intel 620, Nvidia	FreeBSD, Gentoo	Nvidia CUDA, Wine-WoW64
@soccera1	Intel 1255u + Iris Xe	Gentoo	Touchscreen with pen and finger support
@tseli0s	AMD Radeon RX 550	Artix	clang compiler
@barthess	AMD Radeon RX 7600	Gentoo	VRR, 3D games, Steam, Proton/Wine
@maydeafmute	Intel Raptor Lake i9-13900KF + Nvidia RTX 3060OC	Archlinux	Steam, Proton/Wine
@kiyoshispreclerg	AMD Radeon Vega + Nvidia Gtx 1650	Kubuntu	Games, Vtubing, Livestreaming
@Radeon897	AMD 9800x3D + Asus 9070XT	CachyOS	Steam, Proton, RDNA 4 + radv , HDR, FSR4
@ironswordX	Intel Celeron N4020 + Intel UHD Graphics 600	Alpine	Chromebook running Linux + musl libc
@r1w1s1	Intel HD 3000 + Iris Xe Graphics	Slackware-current	Slackware packaging, legacy & modern Intel GPUs
@drewbinomicon	AMD Ryzen 7 5700U + AMD Radeon Integrated GPU + 64 gb of RAM	Ubuntu 24	Lightweight Window Managers like Fluxbox and Window Maker, QGIS, PDF/TXT parsing, deep historical research, little python, light gaming.
@GrandBIRDLizard	Intel Quad Core, 8th gen i5-8265U+Intel WhiskeyLake-UGT2[UHD 620] usually used as a "proving ground for performance", & mobile coding.	Void, Arch, Mint,	Using C(libc am learning musl), Zig, Bash, OpenGL, Fragments, various shader engines, Systems-level implementations and Kernel tweaking, Scheduling Policies, I've got old, Intel(CPU+iGPU), old Intel+Nvidia(i7-7700HQ+1060), New AMD(9900X3D+9070xt)

Ending the Test Driving

We all know that life's focus may shift, priorities change, and time slots become smaller in favor of other things. No problem. To leave the XLibre Test drivers program, simply remove the row with your name and other data from the table above. We would also appreciate it if you could leave a comment at the discussion of this page so that we can thank you warmly and say goodbye. Maybe until next time.