[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] A few comments and fixes to the documentation
From: |
Christian Grothoff |
Subject: |
Re: [GNUnet-developers] A few comments and fixes to the documentation |
Date: |
Sun, 7 Jan 2018 14:31:56 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 |
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