lix/tests/functional/test-libstoreconsumer
John Ericson 68c81c7375 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/
```
2023-10-06 09:05:56 -04:00
..
local.mk Put functional tests in tests/functional 2023-10-06 09:05:56 -04:00
main.cc Put functional tests in tests/functional 2023-10-06 09:05:56 -04:00
README.md Put functional tests in tests/functional 2023-10-06 09:05:56 -04:00

A very simple C++ consumer of the libstore library.

  • Keep it simple. Library consumers expect something simple.
  • No build hook, or any other reinvocations.
  • No more global state than necessary.