Yes, please. It would be even better to have init, run and final merged together so that the whole testing procedure can be written into a single file. Something like
# cat test.sh setup (aka init) east# setup something east# setup something else west# setup something ... test (run & final) west# ... east# ... west# ... ... clean-up (subset of final) east# ... west# ... east# ... ... When I want to know what test actually does, I can get a pretty precise picture from config files and test.sh. -- Ondrej On Thu, Jul 27, 2017 at 5:33 PM, Andrew Cagney <[email protected]> wrote: > I'm trying to set up a test that needs to co-ordinate operations > between east, west, nic, and road (and perhaps north) and I'm finding > having lots of separate script files cumbersome. > > I've got to wonder if it would all be easier if there was a single > file (called run.sh say), that looked like: > > east# so something > west# do something else > ... > > it would certainly make manipulating the sequence easier; the down > side is that the script wouldn't be runable. > > thinking out loud, > Andrew > > PS: this is starting to get very like expect, or expunit > _______________________________________________ > Swan-dev mailing list > [email protected] > https://lists.libreswan.org/mailman/listinfo/swan-dev _______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
