From: Štěpán Němec Date: Fri, 5 Nov 2021 11:39:10 +0000 (+0100) Subject: tests: shell: README: clarify test file name convention X-Git-Tag: v1.0.1~20 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f5cf15a680e18d06be711c81f21b98ef247ff398;p=thirdparty%2Fnftables.git tests: shell: README: clarify test file name convention Since commit 4d26b6dd3c4c, test file name suffix no longer reflects expected exit code in all cases. Move the sentence "Since they are located with `find', test files can be put in any subdirectory." to a separate paragraph. Fixes: 4d26b6dd3c4c ("tests: shell: change all test scripts to return 0") Signed-off-by: Štěpán Němec Signed-off-by: Phil Sutter --- diff --git a/tests/shell/README b/tests/shell/README index 4dd595d9..ea2b0b98 100644 --- a/tests/shell/README +++ b/tests/shell/README @@ -10,8 +10,11 @@ To run the test suite (as root): # ./run-tests.sh Test files are executable files matching the pattern <>, -where N is the expected return code of the executable. Since they -are located with `find', test files can be put in any subdirectory. +where N should be 0 in all new tests. All tests should return 0 on +success. + +Since they are located with `find', test files can be put in any +subdirectory. You can turn on a verbose execution by calling: # ./run-tests.sh -v