freebsd-dev/tools/regression/usr.bin/sed/regress.sh

# $FreeBSD$

REGRESSION_START($1)

REGRESSION_TEST(`G', `sed G < regress.in')
REGRESSION_TEST(`P', `sed P < regress.in')
REGRESSION_TEST(`psl', `sed \$!g\;P\;D < regress.in')
REGRESSION_TEST(`bcb', `sed s/X/$(jot -n -bx -s "" 2043)\\\\zz/ < regress.in')
REGRESSION_TEST(`y', `echo -n foo | sed y/o/O/')
REGRESSION_TEST(`sg', `echo foo | sed s/,*/,/g')
REGRESSION_TEST(`s3', `echo foo | sed s/,*/,/3')
REGRESSION_TEST(`s4', `echo foo | sed s/,*/,/4')
REGRESSION_TEST(`s5', `echo foo | sed s/,*/,/5')

REGRESSION_END()
Add sed(1) tests for proper behaviour of the G option as fixed in PR 26152, and for proper behaviour of some sed functions given a nil pattern space, as fixed in PR 34813. The test for G was based on the test in the PR. The nil pattern space test is slightly different as we need to get some output, as the core dump will also produce no output (old behaviour) and turn up falsely that the utility is working fine. 2002-04-21 01:04:03 +00:00			`# $FreeBSD$`

Convert straightforward regression tests to use regress.m4. Goodbye, duplicated code, you will certainly not be missed. 2002-06-24 13:52:28 +00:00			`REGRESSION_START($1)`
Add sed(1) tests for proper behaviour of the G option as fixed in PR 26152, and for proper behaviour of some sed functions given a nil pattern space, as fixed in PR 34813. The test for G was based on the test in the PR. The nil pattern space test is slightly different as we need to get some output, as the core dump will also produce no output (old behaviour) and turn up falsely that the utility is working fine. 2002-04-21 01:04:03 +00:00
Convert straightforward regression tests to use regress.m4. Goodbye, duplicated code, you will certainly not be missed. 2002-06-24 13:52:28 +00:00			REGRESSION_TEST(`G', `sed G < regress.in')
			REGRESSION_TEST(`P', `sed P < regress.in')
			REGRESSION_TEST(`psl', `sed \$!g\;P\;D < regress.in')
Correct the psl regression test for sed(1)'s now-fixed newline behavior. Add the bcb regression test which checks for failures due to a backslash ('\') coinciding with the very last character of the command buffer. The regression test is cf. this PR (which I did not know about) and has a different fix for the bug. PR: bin/22351 Submitted by: Stefan Duerholt <stefan.duerholt@t-online.de> 2002-06-27 15:58:59 +00:00			REGRESSION_TEST(`bcb', `sed s/X/$(jot -n -bx -s "" 2043)\\\\zz/ < regress.in')
Erk, I forgot that regress.in has an ending newline, so change the test for transliterate to use echo -n to supress newline and a simple string. 2002-06-26 16:57:36 +00:00			REGRESSION_TEST(`y', `echo -n foo \| sed y/o/O/')
Add tests for the behaviour of substitution when the regex can match a zero-length string. This shows bugs in the s///g and s///2+ cases. 2003-06-04 15:26:23 +00:00			REGRESSION_TEST(`sg', `echo foo \| sed s/,*/,/g')
			REGRESSION_TEST(`s3', `echo foo \| sed s/,*/,/3')
			REGRESSION_TEST(`s4', `echo foo \| sed s/,*/,/4')
			REGRESSION_TEST(`s5', `echo foo \| sed s/,*/,/5')
Add sed(1) tests for proper behaviour of the G option as fixed in PR 26152, and for proper behaviour of some sed functions given a nil pattern space, as fixed in PR 34813. The test for G was based on the test in the PR. The nil pattern space test is slightly different as we need to get some output, as the core dump will also produce no output (old behaviour) and turn up falsely that the utility is working fine. 2002-04-21 01:04:03 +00:00
Convert straightforward regression tests to use regress.m4. Goodbye, duplicated code, you will certainly not be missed. 2002-06-24 13:52:28 +00:00			`REGRESSION_END()`