summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorRob Landley <rob@landley.net>2014-11-09 14:16:33 -0600
committerRob Landley <rob@landley.net>2014-11-09 14:16:33 -0600
commiteece7ed546d0e989b1e369c8f9f34b906d473e8a (patch)
tree2dea2b62427b17ff1ed7aa1903c1907dafeaf7a8 /tests
parent4e5b247d3f0e4d1a115fac51a1c6fa92db7eb146 (diff)
downloadtoybox-eece7ed546d0e989b1e369c8f9f34b906d473e8a.tar.gz
toybox-eece7ed546d0e989b1e369c8f9f34b906d473e8a.tar.bz2
toybox-eece7ed546d0e989b1e369c8f9f34b906d473e8a.zip
Yet more sed tests.
Diffstat (limited to 'tests')
-rw-r--r--tests/sed.test30
1 files changed, 22 insertions, 8 deletions
diff --git a/tests/sed.test b/tests/sed.test
index c9a460f..020759b 100644
--- a/tests/sed.test
+++ b/tests/sed.test
@@ -2,32 +2,45 @@
#testing "name" "command" "result" "infile" "stdin"
+testing 'sed as cat' 'sed ""' "one\ntwo\nthree" "" "one\ntwo\nthree"
+
# Exploring the wonders of sed addressing modes
testing '' 'sed -n 1p' "one\n" "" "one\ntwo\nthree"
testing '' 'sed 2p' "one\ntwo\ntwo\nthree" "" "one\ntwo\nthree"
testing '' 'sed -n 2p' "two\n" "" "one\ntwo\nthree"
-# Fun with newlines!
-testing '' 'sed -n 3p' "three" "" "one\ntwo\nthree"
-testing 'sed as cat' 'sed ""' "one\ntwo\nthree" "" "one\ntwo\nthree"
testing 'sed -n $p' 'sed -n \$p' "three" "" "one\ntwo\nthree"
testing 'sed as cat #2' "sed -n '1,\$p'" "one\ntwo\nthree" "" "one\ntwo\nthree"
+testing 'no input means no last line' "sed '\$a boing'" "" "" ""
+testing 'sed -n $,$p' 'sed -n \$,\$p' 'three' '' 'one\ntwo\nthree'
testing '' 'sed -n 1,2p' "one\ntwo\n" "" "one\ntwo\nthree"
testing '' 'sed -n 2,3p' "two\nthree" "" "one\ntwo\nthree"
testing '' 'sed -n 2,1p' "two\n" "" "one\ntwo\nthree"
-testing 'sed -n $p (2 input)' 'sed -n \$p - input' "four\n" "four\n" \
+testing 'sed $ with 2 inputs' 'sed -n \$p - input' "four\n" "four\n" \
"one\ntwo\nthree"
-# More fun with newlines! The missing \n is now _back_
+testing '' 'sed -n /two/p' "two\n" "" "one\ntwo\nthree"
+testing '' 'sed -n 1,/two/p' 'one\ntwo\n' '' 'one\ntwo\nthree'
+testing '' 'sed -n /one/,2p' 'one\ntwo\n' '' 'one\ntwo\nthree'
+testing '' 'sed -n 1,/one/p' 'one\ntwo\nthree' '' 'one\ntwo\nthree'
+testing '' 'sed -n /one/,1p' 'one\n' '' 'one\ntwo\nthree'
+testing 'sed -n /two/,$p' 'sed -n /two/,\$p' 'two\nthree' '' 'one\ntwo\nthree'
+
+
+# Fun with newlines!
+testing '' 'sed -n 3p' "three" "" "one\ntwo\nthree"
testing 'prodigal newline' "sed -n '1,\$p' - input" "one\ntwo\nthree\nfour\n" \
"four\n" "one\ntwo\nthree"
-testing 'no input means no last line' "sed '\$a boing'" "" "" ""
-
-testing 'sed 3p - input' "sed -n 3p" "three" "four\n" "one\ntwo\nthree"
+testing 'Newline only added if further output' "sed -n 3p - input" "three" \
+ "four\n" "one\ntwo\nthree"
+# Fun with match delimiters and escapes
testing 'sed match \t tab' "sed -n '/\t/p'" "\tx\n" "" "\tx\n"
testing 'sed match t delim disables \t tab' "sed -n '\t\txtp'" "" "" "\tx\n"
testing 'sed match t delim makes \t literal t' \
"sed -n '\t\txtp'" "tx\n" "" "tx\n"
testing 'sed match n delim' "sed -n '\n\txnp'" "\tx\n" "" "\tx\n"
+testing 'sed match n delim disables \n newline' "sed -n '\n\nxnp'" "" "" "\nx\n"
+testing 'sed match n delim makes \n literal n' \
+ "sed -n '\n\nxnp'" "nx\n" "" "nx\n"
testing 'end match does not check starting match line' \
"sed -n '/two/,/two/p'" "two\nthree" "" "one\ntwo\nthree"
testing 'end match/start match mixing number/letter' \
@@ -49,3 +62,4 @@ testing 'sed newline staying away' 'sed s/o/x/' 'xne\ntwx' '' 'one\ntwo'
# Why on _earth_ is this not an error? There's a \ with no continuation!
testing 'sed what, _really_?' 'sed -e a\\ && echo yes really' \
'one\nyes really\n' '' 'one\n'
+