Open edoddridge opened 7 years ago
Yes, I think at this stage the thing to do is to have the test suite be developer-facing, and possibly add user-facing self-tests in the future. When it comes into being, the user-facing suite should indeed not depend on valgrind :)
Having two of the tests fail because of a missing dependency (namely, valgrind) is suboptimal.
We should definitely keep valgrind in the test suite, but perhaps we don't set it to run every time.
Alternatively, we decide that the test suite is just for developers and Travis (as suggested in #32), so having some dependencies is not an issue.