John Ericson 4de54b2190 Unit test the "common protocol" too ... Copy the relevant tests to ensure the new interfaces added in the last commit are tested. Perhaps I should try to deduplicat these tests some more. However its not clear how to do that outside of a big ugly C++ macro. https://github.com/google/googletest/blob/main/docs/advanced.md has some stuff but it is cumbersome and I didn't figure it out yet. This is done in a separate commit in order to be sure that the first commit really didn't change any behavior; if we changed the implementation and the tests at once, it would be harder to tell whether or not some behavioral changes slipped in what is supposed to be a "pure refactor". Co-Authored-By: Valentin Gagarin <valentin.gagarin@tweag.io>		2023-10-09 16:57:03 -04:00
..
content-address.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
drv-output.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
optional-content-address.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
optional-store-path.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
realisation.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
set.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
store-path.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
string.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00
vector.bin	Unit test the "common protocol" too	2023-10-09 16:57:03 -04:00