Testing with Nix | 105 Members | |
| 26 Servers |
| Sender | Message | Time |
|---|---|---|
| 24 Jan 2026 | ||
| 22:12:56 | ||
| 28 Jan 2026 | ||
| Hello : One question here about | 13:30:14 | |
| Also, could anyone help package this : https://discourse.imfreedom.org/t/barev-xmpp-flavoured-p2p-protocol/348/2 | 13:31:35 | |
| where should I ask otherwise ? -- Thank you for any indication however. -- | 13:31:46 | |
| last question,
| 13:32:04 | |
| @er10:matrix.org This channel is about automated systems testing. For user support, please use #users:nixos.org | 23:56:28 | |
| 27 Oct 2022 | ||
| 14:32:17 | ||
| i guess everything. improve quality with any method i established the term "package tests" in the manual, i do manual tests before release, i test prs like the gui installer, i test pantheon as part of it's maintainer team, i review prs, i create automated test, i improve and extend the manual, i try to establish a vision for nixpkgs, ..... | 14:36:31 | |
| i professionally work in QA and our team does manual tests for release und automate testing where possible. i think that belongs in one team, to have a common goal. there can still be people that only work in one area and maybe separate chat rooms if it helps decluttering, but we should coordinate the efforts more | 14:42:14 | |
| 14:46:13 | ||
| 14:48:09 | ||
| i just do my own thing and have my own standards for quality (often too perfectionistic). i would like to have a consensus on what level of quality we work towards and a combined effort on that. maybe even policies or recommendations. it's often unclear to me what and to i do things. so i try to learn how it is done or propose something and hope the reviewers are satisfied. i got a lot of such into the manual, like "how to deprecate packages" | 14:49:16 | |
| I think VM-based NixOS tests are seriously cool | 14:50:08 | |
| We have a few at work but almost nobody knows how to properly write them | 14:50:26 | |
| the ones who do learned by looking at random nixpgks code | 14:51:00 | |
| * i just do my own thing and have my own standards for quality (often too perfectionistic). i would like to have a consensus on what level of quality we work towards and a combined effort on that. maybe even policies or recommendations. it's often unclear to me what and how to do things. so i try to learn how it is done or propose something and hope the reviewers are satisfied. i got a lot of such into the manual, like "how to deprecate packages" | 14:52:23 | |
| also, maybe a NixOS Containers based variant could make sense. for when you're testing rather high-level things and test performance is more important than precise control over kernel version | 14:54:58 | |
| 14:57:41 | ||
| has anybody tried integrating GUI test automation like appium or robot framework into these? would it make sense? | 14:58:29 | |
| maybe i should bring up the idea of a QA team in the forum? | 14:59:28 | |
| Robert Hensing (roberth): I had one question about testing, which is: Are nixpkgs/lib tests ever executed? When I was working on modules I added them to the release.nix files of Nixpkgs, but never saw it being reported on Hydra. | 15:01:20 | |
In reply to @davidak:matrix.orgwould that be QA-for-nixpkgs or using-nix-for-QA? (or both) | 15:01:29 | |
In reply to @whentze:matrix.orgi don't know of any container based tests. using testing frameworks make sense. we use language based test tools like pytest | 15:01:41 | |
| there is one gui test using that x11 framebuffer tool. j want to document that | 15:02:28 | |
| I have at some point made a nixos test that would start a single VM with a bunch of nixos containers in it. that also cut down the test runtime a bunch | 15:02:34 | |
In reply to @nbp:mozilla.orgthere's a github action CI that runs nix-build --arg pkgs import ./. {} ./lib/tests/release.nix. I don't think there's a hydra job for it, but that doesn't seem necessary. | 15:03:51 | |
In reply to @whentze:matrix.orga qa team for our project, nixos, nixpkgs etc | 15:04:01 | |
| * there is one gui test using that x11 framebuffer tool. i want to document that | 15:04:50 | |
| does nixpkgs (the repo) implement the "no rocket science" rule btw? | 15:04:51 | |
| the one that says CI on main must always be green, no exceptions, and this should be automatically enforced | 15:05:25 | |