From f5cf15a680e18d06be711c81f21b98ef247ff398 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=A0t=C4=9Bp=C3=A1n=20N=C4=9Bmec?= Date: Fri, 5 Nov 2021 12:39:10 +0100 Subject: tests: shell: README: clarify test file name convention MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- tests/shell/README | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'tests/shell') 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 -- cgit v1.2.3