On Tue, Mar 06, 2018 at 10:33:10AM +0100, Neels Hofmeyr wrote:
> My plan was to instead provide convenience "set up the network" functions
> to call from the test.

Just remembered: also, I initially had the idea of being able to have net
components running across tests. The idea was to have one, like, "0_setup"
test that would start test components, and pass ownership of the running
processes a level up to the scenario, so that the processes remain running
and are available for all of the remaining tests of that scenario (as it
is now, all processes are shut down when the test case ends).

The only benefit here is that a number of test cases don't each setup and
tear down the core net, so they would be a bit faster. And there's also
the drawback of complexity about handling situations where one test
manages to crash a program which then affects subsequent tests -- but I
guess I would just let all remaining tests fail then.

So I guess all I would implement would be some convenience function that
allows reducing code dup across the test functions, for tests that just
want a working network with the modems subscribed, ready for testing.


Attachment: signature.asc
Description: PGP signature

Reply via email to