11–20 of 44 posts
pytest is by far the most productive testing framework I've ever tried, for any language. It's so good that it switched me from treating tests as a necessary chore to actively enjoying writing them.
Using ctypes to exercise a C module like this is brilliant - especially the mechanisms used here to work around segmentation faults.
Reminds me of SQLite, which is written in C but uses TCL for most of its test suite.
@pytest.fixture def libfact(): yield CDLL("./fact.so") FWIW that's pretty confusing as it gives the impression the library is reloaded for every test, but iirc dlopen() will just return a handle to the existing one. I don't think ctypes has a good way to unload dlls so it should probably be `fixture(scope='session')`. That gets more relevant when on-the-fly compilation is added to the mix, spawning a compiler for eve…
Shameless self-plug since I recently made a small header-only C testing "framework": https://github.com/rubenvannieuwpoort/c_unit_tests Feels a bit more in line with the spirit of C (small language, few dependencies).
It is used at my company to test our firmware written in C with python and was developed by a colleague.
Shameless self-plug since I recently made a small header-only C testing "framework": https://github.com/rubenvannieuwpoort/c_unit_tests Feels a bit more in line with the spirit of C (small language, few dependencies).
We've had a lot of success combining that approach (cffi instead of ctypes) with property-based testing ( https://github.com/HypothesisWorks/hypothesis ) for the query engine at backtrace: https://engineering.backtrace.io/2020-03-11-how-hard-is-it-t... .
Shameless self-plug since I recently made a small header-only C testing "framework": https://github.com/rubenvannieuwpoort/c_unit_tests Feels a bit more in line with the spirit of C (small language, few dependencies).
Nice. Now how could I get this to work on a small embedded device compiker (gbdk using lcc), which likely doesn't have that constructor attitude.
How would you go to do this for c++? Specifically for classes and templates, is there an easy way to call code without having to manually write the demangled names of the functions?
Shameless self-plug since I recently made a small header-only C testing "framework": https://github.com/rubenvannieuwpoort/c_unit_tests Feels a bit more in line with the spirit of C (small language, few dependencies).
Nice. Now how could I get this to work on a small embedded device compiker (gbdk using lcc), which likely doesn't have that constructor attitude.
You don't need malloc if using local variables either, which is helpful when your target doesn't have malloc or when debugging memory problems on targets that do. It's nice to know the test framework cannot be leaking or use-after-free anything.