| 17 Apr 2024 |
ibizaman | In reply to @infinidoge:matrix.org I need to figure out a better way to test module stuff than shoving it in my NixOS configuration and opening the flake repl In my repo I’m having module tests (example) with evalModule and integration tests (example) with nixosTests and it’s all run together with flake checks. | 14:06:08 |
ibizaman | In reply to @nbp:mozilla.org https://www.youtube.com/watch?v=lw7PgphB9qM ibizaman https://www.youtube.com/watch?v=-Bfo3Byjwyg djacu If you prefer a written version of the talk (which is not cut at the end) you can read here :) https://shb.skarabox.com/contracts.html | 14:08:07 |
Infinidoge | In reply to @ibizaman:matrix.org In my repo I’m having module tests (example) with evalModule and integration tests (example) with nixosTests and it’s all run together with flake checks. I more so mean ad-hoc testing of random module things, as opposed to proper module tests, however that is something I should also do | 14:17:03 |
ibizaman | In reply to @infinidoge:matrix.org I more so mean ad-hoc testing of random module things, as opposed to proper module tests, however that is something I should also do Ah I see. The only other example I can offer is related to testing functions like here. That being said, it’s also written tests. I can’t think of an intermediate way between this and load in the repl, even outside of nix modules. | 14:20:17 |
Infinidoge | I think me using the word 'testing' is too loaded of a term lol | 14:23:04 |
Infinidoge | I just mean messing around like you would with a repl :) | 14:23:28 |
Infinidoge | It's just that defining and working with modules in the repl gets a bit annoying so I usually shove it in my NixOS configuration and let that eval the module | 14:24:04 |