summaryrefslogtreecommitdiffstats
path: root/tests/shell
diff options
context:
space:
mode:
authorŠtěpán Němec <snemec@redhat.com>2021-11-05 12:39:09 +0100
committerPhil Sutter <phil@nwl.cc>2021-11-05 14:21:26 +0100
commitae5b4617fdbd4d3e0d933c1eac22f41e53365407 (patch)
tree11e620560829c50172bdbbbefe9154c7c9f3e88b /tests/shell
parentdf133965379f39d9143500e6d83c9ff722cf045c (diff)
tests: shell: README: $NFT does not have to be a path to a binary
Since commit 7c8a44b25c22, $NFT can contain an arbitrary command, e.g. 'valgrind nft'. Fixes: 7c8a44b25c22 ("tests: shell: Allow wrappers to be passed as nft command") Signed-off-by: Štěpán Němec <snemec@redhat.com> Signed-off-by: Phil Sutter <phil@nwl.cc>
Diffstat (limited to 'tests/shell')
-rw-r--r--tests/shell/README2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/shell/README b/tests/shell/README
index 35f6e378..4dd595d9 100644
--- a/tests/shell/README
+++ b/tests/shell/README
@@ -21,7 +21,7 @@ And generate missing dump files with:
Before each test file invocation, `nft flush ruleset' will be called.
Also, test file process environment will include the variable $NFT
-which contains the path to the nft binary being tested.
+which contains the nft command being tested.
You can pass an arbitrary $NFT value as well:
# NFT=/usr/local/sbin/nft ./run-tests.sh