Right now, we have pure C++ unit tests (not enough of them but more to come of course) as part of our build.
What I also do is test from the Python end that generated .so, the binary Python extension, actually works. I have a very minimal test script here which I could easily expand into Python unit tests - except if I use the install target to setup.py then it installs this yet-to-be tested binary into my Python path!
Right now I cheat, by having a symbolic link from the build directory that I haven't checked in which makes it all work.
We need to resolve this and then write some actual unit tests and demonstrations in Python.
Right now, we have pure C++ unit tests (not enough of them but more to come of course) as part of our build.
What I also do is test from the Python end that generated .so, the binary Python extension, actually works. I have a very minimal test script here which I could easily expand into Python unit tests - except if I use the
install
target tosetup.py
then it installs this yet-to-be tested binary into my Python path!Right now I cheat, by having a symbolic link from the build directory that I haven't checked in which makes it all work.
We need to resolve this and then write some actual unit tests and demonstrations in Python.