[Swan-dev] testing libipsecconf
Paul Wouters
paul at nohats.ca
Mon Dec 22 02:55:05 EET 2014
On Tue, 25 Nov 2014, D. Hugh Redelmeier wrote:
[late reply]
> [tl;dr] see my actual questions, highlighted with ==>
> Now I need to test if my changes are sound. So I want to use
> testing/scripts/readwriteconf-*
>
> ==> Do these tests actually run in "make check"? They don't seem to in mine.
Not yet. We could put it into a kvm test for now and run the tests.
> I want to test them on my desktop machine. It doesn't have all the
> KVM paraphernalia. But I would think that that ought to be OK for
> testing scripts.
> I can get rid of this problem by changing testing/scripts/readwriteconf-01/runit.sh:
> -args="--rootdir=$ROOTDIR/testing/baseconfigs/all --config $ROOTDIR/testing/baseconfigs/west/etc/ipsec.conf --verbose --verbose"
> +args="--rootdir=$ROOTDIR --config $ROOTDIR/testing/baseconfigs/west/etc/ipsec.conf --verbose --verbose"
> This line dates back to 2006 October 11
That was in uml days, so yes we probably never fixed that up.
> ==> Is this only a problem in my context?
Nope
> ==> Has this test ever worked?
Years ago.
> ==> Is these something wrong with my fix to runit.sh?
I don't think so
> ==> what is the best way of testing libipsecconf changes?
running the ipsec readwriteconf tests.
Paul
More information about the Swan-dev
mailing list