[Swan-dev] test script limitation
andrew.cagney at gmail.com
Wed Oct 13 15:52:55 UTC 2021
(I'm referring to the *.sh scripts within a test)
Traditional test directories, such as dpd-02, contain the script files:
$ ls *.sh
so that more complicated sequences could be built, this was extended to
allow arbitrary names with a lexicographic ordering. This way, the above
can be broken down and carefully sequenced making it more robust:
$ ls -1 *.sh
(It's an IKEv1 test so the test needs to check that east is established
before west can send a ping, the file names I'm using are arbitrary).
While it works, I'm finding it very much write-only: the *.console.txt
files don't reflect the above order making deciphering failures confusing
and updates fragile. For instance, if there's a problem on west, the first
difference is on east (because it is compared first).
I'm now wondering if having a merged file (both input and output) so
everything can be read inline would be better:
east# ipsec start
west# ipsec start
west# ping-once --up east
(we want to make writing tests easy). In this scenario, the differences
could be shown in context.
just playing with ideas
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Swan-dev