summaryrefslogtreecommitdiffstats
path: root/tools/regression/usr.bin
Commit message (Collapse)AuthorAgeFilesLines
* Add tests for -t option with short tty name - pkill(1) should accept bothpjd2005-11-072-6/+30
| | | | (eg. "ttyv0" and "v0").
* Add first tests for semicolon handling. The first test fails. This isharti2005-10-188-0/+47
| | | | probably a bug in the parser.
* Add more tests for escaped newline handling and fix a test that currentlyharti2005-10-1814-8/+48
| | | | should fail because of a bug in the parser (test 2).
* Add regression tests for '-L' option.pjd2005-08-252-0/+84
|
* '-F' option behaviour was reverted, so revert previous commit.pjd2005-08-252-3/+5
|
* '-F' option now needs locked pidfile. Modify regression tests respectively.pjd2005-08-242-6/+4
|
* Correct one regression test (which was expected an incorrect answer), andgad2005-07-151-1/+66
| | | | add a few more tests. This matches bug fixes recently committed to 'env'.
* Upgrade these regression tests to track recent changes to `env'.gad2005-06-211-3/+78
| | | | Approved by: re (blanket `env')
* Add a suite of regression tests for all the recent changes to `env',gad2005-06-203-0/+801
| | | | | | | | | | | | | | | using my own script to handle it. I wrote my own partially because of all the quoting-issues involved with testing what I wanted to test, and partially because this lets me commit one script and one data file, instead of one-file-per-regression-test. This suite was good enough for my initial testing (and it did help me find a few bugs that would have otherwise been missed). I'm not sure how well it will work in general use, but I figured I might as well commit it. It won't *hurt* to have it available. At the worst, people can just ignore it. Approved by: re (blanket `env')
* Add a test for escaped newline handling.harti2005-06-018-0/+45
|
* Add support for TODO tests. These are tests that are supposed to fail,harti2005-06-012-23/+43
| | | | because of a make bug that should be fixed.
* Change the test infrastructure so that tests are easier to maintain andharti2005-05-31192-623/+910
| | | | | | | | | | | | | | so that make(1) will run in an almost clean environment and enhance the description of the test infrastructure. Add the ability to have multiple tests carried out per test script. Give some tests more meaningful names. Fix the usage message from the test scripts. Make it possible to pass several commands to the test scripts like: 'sh test.t setup run compare clean'.
* Add a test to check whether in compat mode make detectes builtinsharti2005-05-206-0/+51
| | | | | on the command line and really executes the shell instead of directly executing the command.
* Add a test to ensure that in compat mode when a line contains noharti2005-05-206-0/+51
| | | | | | shell meta characters it is not passed to the shell, but the command is executed directly (given that the line is not a shell builtin) and that the line with a meta character is passed to the shell.
* Add a test that test whether we can replace the shell to use byharti2005-05-206-0/+54
| | | | | make with another shell and set all its parameters (meta and builtins not tested here).
* Some test cases for .SHELL target: builtin shell selection andharti2005-05-1917-0/+179
| | | | changing the path of a builtin shell.
* o -n option added.marcel2005-05-1510-2/+47
| | | | o -x option added.
* Add an initial regression test suite for make(1).harti2005-04-2865-0/+958
| | | | Submitted by: Max Okumoto <okumotu@ucsd.edu> (partly, initial version)
* Also test \0 in the format string.stefanf2005-04-142-1/+1
|
* Add a few regression tests for printf(1).stefanf2005-04-1312-1/+38
|
* Add regression tests for pkill/pgrep.pjd2005-03-2025-0/+803
| | | | MFC after: 3 days
* Repo-copy tools/regression/usr.bin/make to tools/build/make_checkharti2005-03-028-323/+1
| | | | | | | | and adjust the path in the Makefile for the upgrade_checks target. These checks are really feature upgrade checks that should be fast and just find out whether we need to build a new make before proceeding with other targets like buildworld. This makes the place free for a real regression test suite in the old place.
* Fix builds with a read-only directory and a make upgrade. This is doneharti2004-12-071-6/+4
| | | | | | | | by forcing the creation of an object directory for the make regression tests. Let make handle the tracking of the dependency and installation of test_shell script. Submitted by: ru
* Make this work under debugging, e.g., "make -dl".ru2004-12-061-1/+1
|
* Make the tests runnable on a read-only src. To do this you must make sureharti2004-12-022-49/+63
| | | | | | | | | | | | that you create one of the object directories make knows (see make(1)). This uses the -C flag, so add a test that checks that make actually accepts -C. Also fix the test that selects csh via the .SHELL target to work for tcsh users too. This commit renames shell_test to shell_test.sh. There is no history to preserve so go without a repo-copy. Reviewed by: ru
* Chmod the shell testscript to be executable if it isn't already. Accordingharti2004-11-301-0/+1
| | | | | to the CVS-Meisters x-mode just happens to work, but is not guaranteed to do so. Try to be on the safe side.
* Add some regression tests for the .SHELL target. I'm not sure that theharti2004-11-254-1/+65
| | | | | output of shell_2j is actually correct - it just tests what make currently does. Make should switch on echoing for the second line, shouldn't it?
* Switch over to a different, more flexible test output protocol that'snik2004-11-1119-37/+90
| | | | | | | | | | | | | | | | | | | | understood by Perl's Test::Harness module and prove(1) commands. Update README to describe the new protocol. The work's broken down into two main sets of changes. First, update the existing test programs (shell scripts and C programs) to produce output in the ok/not ok format, and to, where possible, also produce a header describing the number of tests that are expected to be run. Second, provide the .t files that actually run the tests. In some cases these are copies of, or very similar too, scripts that already existed. I've kept the old scripts around so that it's possible to verify that behaviour under this new system (in terms of whether or not a test fails) is identical to the behaviour under the old system. Add a TODO file.
* Add a regression test for the alternate shell specification.ru2004-10-231-0/+10
|
* Now that make more correctly handles variable assignmentsharti2004-08-121-3/+1
| | | | in .MAKEFLAGS targets enable the regression test for this.
* Per letter dated July 22, 1999 remove 3rd clause of Berkeley deriveddds2004-08-092-8/+0
| | | | | | software (original contributor). Reviewed by: imp
* Back out something I'm working on that crept in with the last commit.harti2004-08-051-1/+3
| | | | Spotted by: ru
* Remove extra spaces. Remove double quotes around error messages -harti2004-08-051-13/+11
| | | | | | they are not needed and will actually be printed. Submitted by: ru
* Add another test that checks for a working '+' command flag.harti2004-08-051-0/+19
|
* Add a regression test for the passing of command lineharti2004-08-041-0/+87
| | | | variable assignments via the MAKEFLAGS environment variable.
* A new version that does exponents and lots of other neat things. Updatesmkelly2004-05-011-59/+335
| | | | | | from the original author of math.sed. Submitted by: K S Braunsdorf <sed@ksb.npcguild.org>
* Add a test for what was broken in rev. 1.28 and fixed in rev. 1.29ru2004-01-301-0/+8
| | | | of make/str.c.
* Add a test for what was fixed in revs. 1.28 and 1.29 of make/str.c.ru2004-01-291-0/+11
|
* Fix a bug that prevented exists() from finding "foo/", "foo/."ru2003-10-021-0/+11
| | | | | | and "foo/.." when ".PATH: foo" was also given. PR: bin/34062
* Test 8.16 in sed.test tests the ability of a sed to handle an emptydds2003-07-222-22/+38
| | | | | | | | | | | | | | | | | regular expression as the first argument to a substitute command. If used to test a sed which (erroneously) evaluates this at translation time rather than at execution time, the bugged sed is put into an infinite loop. This mode of failure seems excessive. Such a failing sed is the Free Software Foundation's sed 3.02. The specific test was also not being executed for the BSD sed. Both problems are now fixed. PR: misc/25585 Submitted by: Walter Briscoe <w.briscoe@ponl.com> Approved by: schweikh (mentor) MFC after: 2 weeks
* Fixed broken arithmetic expression parser.ru2003-07-041-0/+12
| | | | | Reminded by: bde In memory of: alane
* Add tests for the behaviour of substitution when the regex can matchfanf2003-06-045-0/+8
| | | | a zero-length string. This shows bugs in the s///g and s///2+ cases.
* The regression-tests for 'make' *expect* to trigger make's warning:gad2003-02-101-1/+1
| | | | | | | | | | warning: duplicate script for target "double" ignored The regression-tests do try to hide that message, but the message does still appear when using -j (eg: 'make -j5 buildworld'). This changes the regression-test so the expected warning message will not be seen even when -j is specified. Reviewed by: jmallett ru
* Add a test for what was fixed in revisions 1.39 and 1.50 ofru2002-11-281-0/+9
| | | | | | make/parse.c (allow embedded `:' and `!' in target names). Approved by: re
* Moved make(1) regression tests from src/Makefile to where theyru2002-11-281-1/+25
| | | | | | | belong (src/tools/regression/usr.bin/make), and use the latter to test if make(1) is adequate for building the world. Approved by: re
* Hide the test in <target> under '.if make(<target>)' so as to not get anyjmallett2002-10-251-0/+4
| | | | errors/warnings related to crud in said test block.
* As of revision 1.38 of make/parse.c, our make(1) will warn too. Note thatjmallett2002-07-281-2/+3
| | | | | this isn't just for the sake of testing behaviour, and that things really do break if this regression occurs.
* Update another mention of <CR><CR> I missed the first time around (rev 1.2)tjr2002-07-041-1/+1
|
* Note that two carriage returns aren't required after entering thetjr2002-07-031-2/+3
| | | | | | initial setup anymore (since process.c rev. 1.25). Add $FreeBSD$. MFC after: 2 weeks
* The wrong y/// output got spammed into this file; from green@ indirectly.jmallett2002-06-271-1/+1
|
OpenPOWER on IntegriCloud