30dcc19d1f
I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ``` (cherry picked from commit 68c81c737571794f7246db53fb4774e94fcf4b7e)
30 lines
814 B
Nix
30 lines
814 B
Nix
with builtins;
|
|
|
|
let
|
|
|
|
matches = pat: s: match pat s != null;
|
|
|
|
splitFN = match "((.*)/)?([^/]*)\\.(nix|cc)";
|
|
|
|
in
|
|
|
|
assert matches "foobar" "foobar";
|
|
assert matches "fo*" "f";
|
|
assert !matches "fo+" "f";
|
|
assert matches "fo*" "fo";
|
|
assert matches "fo*" "foo";
|
|
assert matches "fo+" "foo";
|
|
assert matches "fo{1,2}" "foo";
|
|
assert !matches "fo{1,2}" "fooo";
|
|
assert !matches "fo*" "foobar";
|
|
assert matches "[[:space:]]+([^[:space:]]+)[[:space:]]+" " foo ";
|
|
assert !matches "[[:space:]]+([[:upper:]]+)[[:space:]]+" " foo ";
|
|
|
|
assert match "(.*)\\.nix" "foobar.nix" == [ "foobar" ];
|
|
assert match "[[:space:]]+([[:upper:]]+)[[:space:]]+" " FOO " == [ "FOO" ];
|
|
|
|
assert splitFN "/path/to/foobar.nix" == [ "/path/to/" "/path/to" "foobar" "nix" ];
|
|
assert splitFN "foobar.cc" == [ null null "foobar" "cc" ];
|
|
|
|
true
|