mirror of
http://github.com/valkey-io/valkey
synced 2024-11-22 00:52:38 +00:00
5b1fd222ed
The core idea was to take a lot of the stuff from the C unity framework and adapt it a bit here. Each file in the `unit` directory that starts with `test_` is automatically assumed to be a test suite. Within each file, all functions that start with `test_` are assumed to be a test. See unit/README.md for details about the implementation. Instead of compiling basically a net new binary, the way the tests are compiled is that the main valkey server is compiled as a static archive, which we then compile the individual test files against to create a new test executable. This is not all that important now, other than it makes the compilation simpler, but what it will allow us to do is overwrite functions in the archive to enable mocking for cross compilation unit functions. There are also ways to enable mocking from within the same compilation unit, but I don't know how important this is. Tests are also written in one of two styles: 1. Including the header file and directly calling functions from the archive. 2. Importing the original file, and then calling the functions. This second approach is cool because we can call static functions. It won't mess up the archive either. --------- Signed-off-by: Madelyn Olson <madelyneolson@gmail.com> |
||
|---|---|---|
| .. | ||
| build-release-packages.yml | ||
| call-build-linux-arm-packages.yml | ||
| call-build-linux-x86-packages.yml | ||
| ci.yml | ||
| codecov.yml | ||
| codeql-analysis.yml | ||
| coverity.yml | ||
| daily.yml | ||
| external.yml | ||
| reply-schemas-linter.yml | ||
| spell-check.yml | ||