nonexistent programs on $PATH and nonexistent programs with an absolute
pathname, so we ought to test both.
If anyone creates a program called nonexistent-program-on-path and
thereby breaks this test for themselves, they deserve it. ;-)
Also prune a no-longer-used shell variable.
being restricted to the #!/bin/sh used to run atf; (2) you can tell what
happened when it fails, since it does currently fail; (3) it runs all the
cases even when some of them don't work, and fails only at the end.
reason the parser does not accept its contents... You know, one should
always test even trivial changes!
Will review this in more depth tomorrow to find the real root cause of the
problem and rule out a fix for ATF.
support shared libraries). Reported by he@.
This was an attempt to test the exact same id binary in the system but
using fake library calls to provide fictitious but stable user/group
entries. Instead, build a helper id binary linked against our fake
functions. This is what we already do in, e.g. the tests for util/df.
check for the command's syntax, but while doing so, I'm adding tests for
all (or almost) possible executions of these commands.
I'm not too happy with the "libfake" directory because there must be some
simpler way to do this, but it will do the trick for now hopefully.
This change converts all the existing regression tests in regress/bin to
the new framework provided by atf. As a side effect, this also moves all
the tests programs in regress/bin to tests/util, as they all belong to
utilities installed by the base-util-root package.