lix/tests/functional/lang/eval-fail-foldlStrict-strict-op-application.nix at 3392020710cdb21345802af8a70a29a72a37a845 - aleksanaa/lix - Lix Systems

aleksanaa/lix

forked from lix-project/lix

John Ericson 30dcc19d1f Put functional tests in tests/functional

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)

2023-12-01 12:06:43 -05:00

5 lines

190 B

Nix

Raw Blame History

 # Tests that the result of applying op is forced even if the value is never used
 builtins.foldl'
   (_: f: f null)
   null
   [ (_: throw "Not the final value, but is still forced!") (_: 23) ]