On 01/06/2018 08:03 PM, ng0 wrote: >> A problem, I have no solution for right now, is testing the bindings. >> Unittesting doesn't make sens, since the bindings requires gnunet-arm >> and the services to be running. Help will be appreciated in this >> regard. > I think Grothoff or any other dev could answer most of these questions > technically more correct than I would be able to at this point. I could > explain it, but I want to avoid causing confusion. >
Well, it may not be technically unit-testing, but the common style we follow in this case is to create a test (that is run as part of 'make check') which simply launches the peer (via ARM), runs the tests, and then stops the peer. For multi-peer tests, we have the testbed API (C) or the gnunet-testbed-profiler (shell scripts, etc). But aside from this slightly more evolved setup/teardown, it is best practice to write such tests to try to achieve code coverage, just like you might do with unit tests.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
