Commentator2.0
5daddad39a
Due to nix-store making its paths read-only, pytest was unable to remove the test files and hence the entire temporary directory, screaming all over the place in stderr about that, getting worse for each test run. By making the nix fixture first yield nix and then, after the test finished running, changing the file permissions to include read on all files and directories within the temp folder, pytest is able to properly remove old test runs again Additionally added more clear instructions for file deletion to the pytest configuration Change-Id: Ia7e3d195665968ac80a57d0e525691b28be7f503
functional2 tests
This uncreatively named test suite is a Pytest based replacement for the shell framework used to write traditional Nix integration tests. Its primary goal is to make tests more concise, more self-contained, easier to write, and to produce better errors.
Goals
- Eliminate implicit dependencies on files in the test directory as well as the requirement to copy the test files to the build directory as is currently hacked in the other functional test suite.
- You should be able to write a DirectoryTree of files for your test declaratively.
- Reduce the amount of global environment state being thrown around in the test suite.
- Make tests very concise and easy to reuse code for, and hopefully turn more of what is currently code into data.
- Provide rich ways of calling
nixwith pleasant syntax.
- Provide rich ways of calling
TODO: Intended features
- Expect tests (pytest-expect-test) or snapshot tests (pytest-insta) or, likely, both! We::jade prefer to have short output written in-line as it makes it greatly easier to read the tests, but pytest-expect doesn't allow for putting larger stuff in external files, so something else is necessary for those.
- Web server fixture: we don't test our network functionality because background processes are hard and this is simply goofy. We could just test it.
- Nix daemon fixture.
- Parallelism via pytest-xdist.