fix: config tests without script

some tests only assert correct configuration generation, let's call
them "config tests" as opposed to "runtime tests"/"e2e tests".

Those configuration tests, don't expose a runtime script. So they
should not be taken into account for any orchestrated runtime script.
This commit is contained in:
David Arnold 2021-05-10 14:59:04 -04:00
parent a3464f6857
commit 4707557ba3
No known key found for this signature in database
GPG key ID: 6D6A936E69C59D08
2 changed files with 8 additions and 4 deletions

View file

@ -22,10 +22,13 @@ let
''
else t.script;
tests = builtins.trace testing pkgs.linkFarm "${testing.name}-tests" (map (t: {
path = toTestScript t;
name = "${t.name}_test.py";
}) testing.tests);
tests = pkgs.linkFarm "${testing.name}-tests" (
map (t: {
path = toTestScript t;
name = "${t.name}_test.py";
})
( filter (t: t.script != null) testing.tests )
);
testScript = pkgs.writeScript "test-${testing.name}.sh" ''
#!/usr/bin/env bash