|author||Laura Garcia Liebana <firstname.lastname@example.org>||2018-03-07 22:51:10 +0100|
|committer||Pablo Neira Ayuso <email@example.com>||2018-03-09 12:45:16 +0100|
tests: shell: autogenerate dump verification
Complete the automated shell tests with the verification of the test file dump, only for positive tests and if the test execution was successful. It's able to generate the dump file with the -g option. Example: # ./run-tests.sh -g testcases/chains/0001jumps_0 The dump files are generated in the same path in the folder named dumps/ with .nft extension. It has been avoided the dump verification code in every test file. Signed-off-by: Laura Garcia Liebana <firstname.lastname@example.org> Signed-off-by: Pablo Neira Ayuso <email@example.com>
Diffstat (limited to 'tests/shell/README')
1 files changed, 4 insertions, 1 deletions
diff --git a/tests/shell/README b/tests/shell/README
index 3ffe642c..e6d83bce 100644
@@ -1,5 +1,5 @@
This test-suite is intended to perform tests of higher level than
-the other reggresion test-suite.
+the other regression test-suite.
It can run arbitrary executables which can perform any test apart of testing
the nft syntax or netlink code (which is what the regression tests does).
@@ -15,6 +15,9 @@ test-files can be spread in any sub-directories.
You can turn on a verbose execution by calling:
% ./run-tests.sh -v
+And generate missing dump files with:
+ % ./run-tests.sh -g <TESTFILE>
Before each call to the test-files, `nft flush ruleset' will be called.
Also, test-files will receive the environment variable $NFT which contains the
path to the nftables binary being tested.