aboutsummaryrefslogtreecommitdiff
path: root/testsuite/sed.tests
AgeCommit message (Collapse)Author
2009-06-30sed: fix handling of 1d;1,3p and 1d;1,REGEXpDenys Vlasenko
function old new delta process_files 2084 2173 +89 Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
2008-07-11testsuite: uniformly use $ECHO with -n -eDenis Vlasenko
2008-02-28sed: n cmd must reset "we had successful subst" flag. closes bug 1214.Denis Vlasenko
2007-11-13sed: support GNU-like '\t' escape in substitutionsDenis Vlasenko
2007-03-16sed: fix very obscure case of escaped newline in sed commandDenis Vlasenko
(needed for uclibc build, btw). Add testcase for it.
2007-01-29add to testsuite and fix yet another sed corner caseDenis Vlasenko
2007-01-29sed: fix 2 bugs (one testsuite entry + one newly found)Denis Vlasenko
but more importantly make code more understandable
2007-01-28fix all known regressions with sed and also make it simplerDenis Vlasenko
2006-09-17whitespace cleanupDenis Vlasenko
2006-07-26Rich Filker spotted that sed -e 's/xxx/[/' didn't work right. Did a smallerRob Landley
fix than his, and shrank the code a bit on top of that so the net size is smaller, and added a test to the test suite for this case. Plus I cleaned up the #includes and removed unnecessary "const"s while I was there.
2006-03-16Redo test suite to be able to test more than one command at a time. EliminateRob Landley
$COMMAND environment variable, instead put full command line (including command to run) in second argument. Modify $PATH to have test versions of commands at start of path. (Also more infrastructure for testing as root, work in progress...)
2006-03-01Yet more sed tests. Passing these is a to-do item for 1.1.2 or 1.2, not aRob Landley
1.1.1 issue.
2006-02-23Lots of tests the fix to sed needs to pass...Rob Landley
2005-11-10Ok, I've converted the contents of the "testing/sed" directory into a Rob Landley
sed.tests file. My brain hurts now. (Lots of boggling at sed minutiae and corner cases and going "why is gnu giving that output". The behavior of N and n with regard to EOF are only understandable if you read the Open Group spec, not if you read the sed info page, by the way...) Some of the existing sed tests are just nuts. For example, sed-next-line is testing for our behavior (which is wrong), and would fail if run against gnu sed (which was getting it right. Again, this was a spec-boggling moment, with much head scratching. I've got to add a debug mode where the stuff output by the p command is a different color from the stuff output by normal end of script printing (when not suppressed by -n).) As for sed-handles-unsatisifed-backrefs: what is this test trying to _do_? I ran it against gnu sed and got an error message, and this behavior sounds perfectly reasonable. (It _is_ an unsatisfied backref.) The fact we currently ignore this case (and treat \1 as an empty string) isn't really behavior we should have a test depend on for success. The remaining one is sed-aic-commands, which is long and complicated. I'm trying to figure out if I should chop this into a number of smaller tests, or if having one big "does-many-things" test is a good idea. In any case, the _next_ step is to go through the Open Group standard and make tests for every case not yet covered. (And there are plenty. There are few comments in the file already.) Plus I have notes about corner cases from development that I need to collate and put into here. This file is maybe the first 1/3 of a truly comprehensive sed test. Rob