Closed digitalcircuit closed 4 years ago
Now that https://github.com/fuzzball-muck/fuzzball/pull/539 is merged, the fundamentals of this are established! :tada: Thank you @woggle.
I'll go ahead and close this issue. If I'm mistaken, feel free to re-open it.
Eventually, Fuzzball should have some form of automated tests that run locally, perhaps a separate
make test
step. Ideally, this would include testing normal and SSL connections, running the MUF regression set, and validating that at least basic commands work, if not all commands.Travis CI and Appveyor could make use of these tests and make sure that new changes don't accidentally break old functionality.
This is a long-term issue, perhaps after the build system is unified, and should involve careful investigation of available testing frameworks (e.g. Google Test), or, if needed, writing one from scratch (e.g. Bitlbee's approach).