emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

testsuite: allow tests to work in paths containing spaces

Browse Source 
Tweak some tests so they work when the path to the test directory or
$HOME contains spaces.

Signed-off-by: Ron Yorston <rmy@pobox.com>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
Ron Yorston 2018-02-09 09:52:52 +00:00 committed by Denys Vlasenko
parent 9db344a0f4
commit 1f27fa9838
5 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
testsuite/grep.tests
View File

@ -15,7 +15,7 @@
testing "grep (exit with error)" "grep nonexistent 2> /dev/null ; echo \$?" \ testing "grep (exit with error)" "grep nonexistent 2> /dev/null ; echo \$?" \
"1\n" "" "" "1\n" "" ""
testing "grep (exit success)" "grep grep $0 > /dev/null 2>&1 ; echo \$?" "0\n" \ testing "grep (exit success)" "grep grep '$0' > /dev/null 2>&1 ; echo \$?" "0\n" \
"" "" "" ""
# Test various data sources and destinations # Test various data sources and destinations

2
testsuite/printf.tests
View File

@ -20,7 +20,7 @@ testing "printf produces no further output 2" \
"" "" "" ""
testing "printf repeatedly uses pattern for each argv" \ testing "printf repeatedly uses pattern for each argv" \
"${bb}printf '%s\n' foo \$HOME" \ "${bb}printf '%s\n' foo '$HOME'" \
"foo\n$HOME\n" \ "foo\n$HOME\n" \
"" "" "" ""

2
testsuite/pwd/pwd-prints-working-directory
View File

@ -1,4 +1,4 @@
# shell's $PWD may leave symlinks unresolved. # shell's $PWD may leave symlinks unresolved.
# "pwd" may be a built-in and have the same problem. # "pwd" may be a built-in and have the same problem.
# External pwd _can't_ have that problem (current dir on Unix is physical). # External pwd _can't_ have that problem (current dir on Unix is physical).
test $(`which pwd`) = $(busybox pwd) test "$(`which pwd`)" = "$(busybox pwd)"

6
testsuite/sum.tests
View File

@ -13,12 +13,12 @@
# test can create a file "actual" instead of writing to stdout # test can create a file "actual" instead of writing to stdout
testing "sum -r file doesn't print file's name" \ testing "sum -r file doesn't print file's name" \
"sum -r $0 | grep -c $0 && echo wrongly_printed_filename || echo yes" \ "sum -r '$0' | grep -c '$0' && echo wrongly_printed_filename || echo yes" \
"0\nyes\n" "" "" "0\nyes\n" "" ""
testing "sum -r file file does print both names" \ testing "sum -r file file does print both names" \
"sum -r $0 $0 | grep -c $0 && echo yes || echo wrongly_omitted_filename" \ "sum -r '$0' '$0' | grep -c '$0' && echo yes || echo wrongly_omitted_filename" \
"2\nyes\n" "" "" "2\nyes\n" "" ""
testing "sum -s file does print file's name" \ testing "sum -s file does print file's name" \
"sum -s $0 | grep -c $0 && echo yes || echo wrongly_omitted_filename" \ "sum -s '$0' | grep -c '$0' && echo yes || echo wrongly_omitted_filename" \
"1\nyes\n" "" "" "1\nyes\n" "" ""
exit $FAILCOUNT exit $FAILCOUNT

6
testsuite/xargs/xargs-works
View File

@ -1,4 +1,6 @@
# FEATURE: CONFIG_FEATURE_XARGS_SUPPORT_ZERO_TERM
[ -n "$d" ] || d=.. [ -n "$d" ] || d=..
find "$d" -name \*works -type f | xargs md5sum > logfile.gnu find "$d" -name \*works -type f -print0 | xargs -0 md5sum > logfile.gnu
find "$d" -name \*works -type f | busybox xargs md5sum > logfile.bb find "$d" -name \*works -type f -print0 | busybox xargs -0 md5sum > logfile.bb
diff -u logfile.gnu logfile.bb diff -u logfile.gnu logfile.bb