source: branches/2.2.9/mindi-busybox/testsuite/sed.tests @ 2725

Last change on this file since 2725 was 2725, checked in by bruno, 8 years ago
  • Update mindi-busybox to 1.18.3 to avoid problems with the tar command which is now failing on recent versions with busybox 1.7.3
  • Property svn:executable set to *
File size: 9.9 KB
Line 
1#!/bin/sh
2
3# SUSv3 compliant sed tests.
4# Copyright 2005 by Rob Landley <rob@landley.net>
5# Licensed under GPLv2, see file LICENSE in this source tree.
6
7. ./testing.sh
8
9# testing "description" "arguments" "result" "infile" "stdin"
10
11# Corner cases
12testing "sed no files (stdin)" 'sed ""' "hello\n" "" "hello\n"
13testing "sed explicit stdin" 'sed "" -' "hello\n" "" "hello\n"
14testing "sed handles empty lines" "sed -e 's/\$/@/'" "@\n" "" "\n"
15testing "sed stdin twice" 'sed "" - -' "hello" "" "hello"
16
17# Trailing EOF.
18#   Match $, at end of each file or all files?
19
20# -e corner cases
21#   without -e
22#   multiple -e
23#       interact with a
24#   -eee arg1 arg2 arg3
25# -f corner cases
26#   -e -f -e
27# -n corner cases
28#   no newline at EOF?
29# -r corner cases
30#   Just make sure it works.
31# -i corner cases:
32#   sed -i -
33#   permissions
34#   -i on a symlink
35#   on a directory
36#       With $ last-line test
37# Continue with \
38#       End of script with trailing \
39
40# command list
41testing "sed accepts blanks before command" "sed -e '1 d'" "" "" ""
42testing "sed accepts newlines in -e" "sed -e 'i\
431
44a\
453'" "1\n2\n3\n" "" "2\n"
46testing "sed accepts multiple -e" "sed -e 'i\' -e '1' -e 'a\' -e '3'" \
47    "1\n2\n3\n" "" "2\n"
48
49# substitutions
50testing "sed -n" "sed -n -e s/foo/bar/ -e s/bar/baz/" "" "" "foo\n"
51testing "sed s//p" "sed -e s/foo/bar/p -e s/bar/baz/p" "bar\nbaz\nbaz\n" \
52    "" "foo\n"
53testing "sed -n s//p" "sed -ne s/abc/def/p" "def\n" "" "abc\n"
54test x"$SKIP_KNOWN_BUGS" = x"" && {
55testing "sed s//g (exhaustive)" "sed -e 's/[[:space:]]*/,/g'" ",1,2,3,4,5,\n" \
56    "" "12345\n"
57}
58testing "sed s arbitrary delimiter" "sed -e 's woo boing '" "boing\n" "" "woo\n"
59testing "sed s chains" "sed -e s/foo/bar/ -e s/bar/baz/" "baz\n" "" "foo\n"
60testing "sed s chains2" "sed -e s/foo/bar/ -e s/baz/nee/" "bar\n" "" "foo\n"
61testing "sed s [delimiter]" "sed -e 's@[@]@@'" "onetwo" "" "one@two"
62testing "sed s with \\t (GNU ext)" "sed 's/\t/ /'" "one two" "" "one\ttwo"
63
64# branch
65testing "sed b (branch)" "sed -e 'b one;p;: one'" "foo\n" "" "foo\n"
66testing "sed b (branch with no label jumps to end)" "sed -e 'b;p'" \
67    "foo\n" "" "foo\n"
68
69# test and branch
70testing "sed t (test/branch)" "sed -e 's/a/1/;t one;p;: one;p'" \
71    "1\n1\nb\nb\nb\nc\nc\nc\n" "" "a\nb\nc\n"
72testing "sed t (test/branch clears test bit)" "sed -e 's/a/b/;:loop;t loop'" \
73    "b\nb\nc\n" "" "a\nb\nc\n"
74testing "sed T (!test/branch)" "sed -e 's/a/1/;T notone;p;: notone;p'" \
75    "1\n1\n1\nb\nb\nc\nc\n" "" "a\nb\nc\n"
76
77test x"$SKIP_KNOWN_BUGS" = x"" && {
78# Normal sed end-of-script doesn't print "c" because n flushed the pattern
79# space.  If n hits EOF, pattern space is empty when script ends.
80# Query: how does this interact with no newline at EOF?
81testing "sed n (flushes pattern space, terminates early)" "sed -e 'n;p'" \
82    "a\nb\nb\nc\n" "" "a\nb\nc\n"
83}
84# non-GNU sed: N does _not_ flush pattern space, therefore c is eaten @ script end
85# GNU sed: N flushes pattern space, therefore c is printed too @ script end
86testing "sed N (flushes pattern space (GNU behavior))" "sed -e 'N;p'" \
87    "a\nb\na\nb\nc\n" "" "a\nb\nc\n"
88
89testing "sed N test2" "sed ':a;N;s/\n/ /;ta'" \
90    "a b c\n" "" "a\nb\nc\n"
91
92testing "sed N test3" "sed 'N;s/\n/ /'" \
93    "a b\nc\n" "" "a\nb\nc\n"
94
95testing "sed address match newline" 'sed "/b/N;/b\\nc/i woo"' \
96    "a\nwoo\nb\nc\nd\n" "" "a\nb\nc\nd\n"
97
98# Multiple lines in pattern space
99testing "sed N (stops at end of input) and P (prints to first newline only)" \
100    "sed -n 'N;P;p'" "a\na\nb\n" "" "a\nb\nc\n"
101
102# Hold space
103testing "sed G (append hold space to pattern space)" 'sed G' "a\n\nb\n\nc\n\n" \
104    "" "a\nb\nc\n"
105#testing "sed g/G (swap/append hold and patter space)"
106#testing "sed g (swap hold/pattern space)"
107
108testing "sed d ends script iteration" \
109    "sed -e '/ook/d;s/ook/ping/p;i woot'" "" "" "ook\n"
110testing "sed d ends script iteration (2)" \
111    "sed -e '/ook/d;a\' -e 'bang'" "woot\nbang\n" "" "ook\nwoot\n"
112
113# Multiple files, with varying newlines and NUL bytes
114test x"$SKIP_KNOWN_BUGS" = x"" && {
115testing "sed embedded NUL" "sed -e 's/woo/bang/'" "\0bang\0woo\0" "" \
116    "\0woo\0woo\0"
117}
118testing "sed embedded NUL g" "sed -e 's/woo/bang/g'" "bang\0bang\0" "" \
119    "woo\0woo\0"
120test x"$SKIP_KNOWN_BUGS" = x"" && {
121$ECHO -e "/woo/a he\0llo" > sed.commands
122testing "sed NUL in command" "sed -f sed.commands" "woo\nhe\0llo\n" "" "woo"
123rm sed.commands
124}
125
126# sed has funky behavior with newlines at the end of file.  Test lots of
127# corner cases with the optional newline appending behavior.
128
129testing "sed normal newlines" "sed -e 's/woo/bang/' input -" "bang\nbang\n" \
130    "woo\n" "woo\n"
131testing "sed leave off trailing newline" "sed -e 's/woo/bang/' input -" \
132    "bang\nbang" "woo\n" "woo"
133testing "sed autoinsert newline" "sed -e 's/woo/bang/' input -" "bang\nbang" \
134    "woo" "woo"
135testing "sed empty file plus cat" "sed -e 's/nohit//' input -" "one\ntwo" \
136    "" "one\ntwo"
137testing "sed cat plus empty file" "sed -e 's/nohit//' input -" "one\ntwo" \
138    "one\ntwo" ""
139test x"$SKIP_KNOWN_BUGS" = x"" && {
140testing "sed append autoinserts newline" "sed -e '/woot/a woo' -" \
141    "woot\nwoo\n" "" "woot"
142}
143testing "sed insert doesn't autoinsert newline" "sed -e '/woot/i woo' -" \
144    "woo\nwoot" "" "woot"
145testing "sed print autoinsert newlines" "sed -e 'p' -" "one\none" "" "one"
146testing "sed print autoinsert newlines two files" "sed -e 'p' input -" \
147    "one\none\ntwo\ntwo" "one" "two"
148testing "sed noprint, no match, no newline" "sed -ne 's/woo/bang/' input" \
149    "" "no\n" ""
150testing "sed selective matches with one nl" "sed -ne 's/woo/bang/p' input -" \
151    "a bang\nc bang\n" "a woo\nb no" "c woo\nd no"
152testing "sed selective matches insert newline" \
153    "sed -ne 's/woo/bang/p' input -" "a bang\nb bang\nd bang" \
154    "a woo\nb woo" "c no\nd woo"
155testing "sed selective matches noinsert newline" \
156    "sed -ne 's/woo/bang/p' input -" "a bang\nb bang" "a woo\nb woo" \
157    "c no\nd no"
158test x"$SKIP_KNOWN_BUGS" = x"" && {
159testing "sed clusternewline" \
160    "sed -e '/one/a 111' -e '/two/i 222' -e p input -" \
161    "one\none\n111\n222\ntwo\ntwo" "one" "two"
162}
163testing "sed subst+write" \
164    "sed -e 's/i/z/' -e 'woutputw' input -; $ECHO -n X; cat outputw" \
165    "thzngy\nagaznXthzngy\nagazn" "thingy" "again"
166rm outputw
167testing "sed trailing NUL" \
168    "sed 's/i/z/' input -" \
169    "a\0b\0\nc" "a\0b\0" "c"
170testing "sed escaped newline in command" \
171    "sed 's/a/z\\
172z/' input" \
173    "z\nz" "a" ""
174
175# Test end-of-file matching behavior
176
177testing "sed match EOF" "sed -e '"'$p'"'" "hello\nthere\nthere" "" \
178    "hello\nthere"
179testing "sed match EOF two files" "sed -e '"'$p'"' input -" \
180    "one\ntwo\nthree\nfour\nfour" "one\ntwo" "three\nfour"
181# sed match EOF inline: gnu sed 4.1.5 outputs this:
182#00000000  6f 6e 65 0a 6f 6f 6b 0a  6f 6f 6b 0a 74 77 6f 0a  |one.ook.ook.two.|
183#00000010  0a 74 68 72 65 65 0a 6f  6f 6b 0a 6f 6f 6b 0a 66  |.three.ook.ook.f|
184#00000020  6f 75 72                                          |our|
185# which looks buggy to me.
186$ECHO -ne "three\nfour" > input2
187testing "sed match EOF inline" \
188    "sed -e '"'$i ook'"' -i input input2 && cat input input2" \
189    "one\nook\ntwothree\nook\nfour" "one\ntwo" ""
190rm input2
191
192# Test lie-to-autoconf
193
194testing "sed lie-to-autoconf" "sed --version | grep -o 'GNU sed version '" \
195    "GNU sed version \n" "" ""
196
197# Jump to nonexistent label
198test x"$SKIP_KNOWN_BUGS" = x"" && {
199# Incompatibility: illegal jump is not detected if input is ""
200# (that is, no lines at all). GNU sed 4.1.5 complains even in this case
201testing "sed nonexistent label" "sed -e 'b walrus' 2>/dev/null || echo yes" \
202    "yes\n" "" ""
203}
204
205testing "sed backref from empty s uses range regex" \
206    "sed -e '/woot/s//eep \0 eep/'" "eep woot eep" "" "woot"
207
208testing "sed backref from empty s uses range regex with newline" \
209    "sed -e '/woot/s//eep \0 eep/'" "eep woot eep\n" "" "woot\n"
210
211# -i with no filename
212
213touch ./-  # Detect gnu failure mode here.
214testing "sed -i with no arg [GNUFAIL]" "sed -e '' -i 2> /dev/null || echo yes" \
215    "yes\n" "" ""
216rm ./-     # Clean up
217
218testing "sed s/xxx/[/" "sed -e 's/xxx/[/'" "[\n" "" "xxx\n"
219
220# Ponder this a bit more, why "woo not found" from gnu version?
221#testing "sed doesn't substitute in deleted line" \
222#   "sed -e '/ook/d;s/ook//;t woo;a bang;'" "bang" "" "ook\n"
223
224# This makes both seds very unhappy.  Why?
225#testing "sed -g (exhaustive)" "sed -e 's/[[:space:]]*/,/g'" ",1,2,3,4,5," \
226#   "" "12345"
227
228# testing "description" "arguments" "result" "infile" "stdin"
229
230testing "sed n command must reset 'substituted' bit" \
231    "sed 's/1/x/;T;n;: next;s/3/y/;t quit;n;b next;: quit;q'" \
232    "0\nx\n2\ny\n" "" "0\n1\n2\n3\n"
233
234testing "sed d does not break n,m matching" \
235    "sed -n '1d;1,3p'" \
236    "second\nthird\n" "" "first\nsecond\nthird\nfourth\n"
237
238testing "sed d does not break n,regex matching" \
239    "sed -n '1d;1,/hir/p'" \
240    "second\nthird\n" "" "first\nsecond\nthird\nfourth\n"
241
242testing "sed d does not break n,regex matching #2" \
243    "sed -n '1,5d;1,/hir/p'" \
244    "second2\nthird2\n" "" \
245    "first\nsecond\nthird\nfourth\n""first2\nsecond2\nthird2\nfourth2\n"
246
247testing "sed 2d;2,1p (gnu compat)" \
248    "sed -n '2d;2,1p'" \
249    "third\n" "" \
250    "first\nsecond\nthird\nfourth\n"
251
252# Regex means: "match / at BOL or nothing, then one or more not-slashes".
253# The bug was that second slash in /usr/lib was treated as "at BOL" too.
254testing "sed beginning (^) matches only once" \
255    "sed 's,\(^/\|\)[^/][^/]*,>\0<,g'" \
256    ">/usr</>lib<\n" "" \
257    "/usr/lib\n"
258
259testing "sed c" \
260    "sed 'crepl'" \
261    "repl\nrepl\n" "" \
262    "first\nsecond\n"
263
264testing "sed nested {}s" \
265    "sed '/asd/ { p; /s/ { s/s/c/ }; p; q }'" \
266    "qwe\nasd\nacd\nacd\n" "" \
267    "qwe\nasd\nzxc\n"
268
269testing "sed a cmd ended by double backslash" \
270    "sed -e '/| one /a \\
271    | three \\\\' -e '/| one-/a \\
272    | three-* \\\\'" \
273'   | one \\
274    | three \\
275    | two \\
276' '' \
277'   | one \\
278    | two \\
279'
280
281# first three lines are deleted; 4th line is matched and printed by "2,3" and by "4" ranges
282testing "sed with N skipping lines past ranges on next cmds" \
283    "sed -n '1{N;N;d};1p;2,3p;3p;4p'" \
284    "4\n4\n" "" "1\n2\n3\n4\n"
285
286testing "sed -i with address modifies all files, not only first" \
287    "cp input input2; sed -i -e '1s/foo/bar/' input input2 && cat input input2; rm input2" \
288    "bar\nbar\n" "foo\n" ""
289
290
291# testing "description" "arguments" "result" "infile" "stdin"
292
293exit $FAILCOUNT
Note: See TracBrowser for help on using the repository browser.