1 files changed, 81 insertions, 0 deletions
diff --git a/tests/misc/printenv.sh b/tests/misc/printenv.sh
new file mode 100755
index 000000000..bbce8ef0e
--- /dev/null
+++ b/tests/misc/printenv.sh
@@ -0,0 +1,81 @@
+#!/bin/sh
+# Verify behavior of printenv.
+
+# Copyright (C) 2009-2012 Free Software Foundation, Inc.
+
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+. "${srcdir=.}/init.sh"; path_prepend_ ../src
+print_ver_ printenv
+
+# Without arguments, printenv behaves like env.  Some shells provide
+# printenv as a builtin, so we must invoke it via "env".
+# But beware of $_, set by many shells to the last command run.
+# Also, filter out LD_PRELOAD, which is set when running under valgrind.
+env | grep -Ev '^(_|LD_PRELOAD=)' > exp || framework_failure_
+env -- printenv | grep -Ev '^(_|LD_PRELOAD=)' > out || fail=1
+compare exp out || fail=1
+
+# POSIX is clear that environ may, but need not be, sorted.
+# Environment variable values may contain newlines, which cannot be
+# observed by merely inspecting output from printenv.
+if env -- printenv | grep '^ENV_TEST' >/dev/null ; then
+  skip_ "environment has potential interference from ENV_TEST*"
+fi
+
+# Printing a single variable's value.
+env -- printenv ENV_TEST > out
+test $? = 1 || fail=1
+test -s out && fail=1
+echo a > exp || framework_failure_
+ENV_TEST=a env -- printenv ENV_TEST > out || fail=1
+compare exp out || fail=1
+
+# Printing multiple variables.  Order follows command line.
+ENV_TEST1=a ENV_TEST2=b env -- printenv ENV_TEST2 ENV_TEST1 ENV_TEST2 > out \
+  || fail=1
+ENV_TEST1=a ENV_TEST2=b env -- printenv ENV_TEST1 ENV_TEST2 >> out || fail=1
+cat <<EOF > exp || framework_failure_
+b
+a
+b
+a
+b
+EOF
+compare exp out || fail=1
+
+# Exit status reflects missing variable, but remaining arguments processed.
+ENV_TEST1=a env -- printenv ENV_TEST2 ENV_TEST1 > out
+test $? = 1 || fail=1
+ENV_TEST1=a env -- printenv ENV_TEST1 ENV_TEST2 >> out
+test $? = 1 || fail=1
+cat <<EOF > exp || framework_failure_
+a
+a
+EOF
+compare exp out || fail=1
+
+# Non-standard environment variable name.  Shells won't create it, but
+# env can, and printenv must be able to deal with it.
+echo b > exp || framework_failure_
+env -- -a=b printenv -- -a > out || fail=1
+compare exp out || fail=1
+
+# Silently reject invalid env-var names.
+# Bug present through coreutils 8.0.
+env a=b=c printenv a=b > out
+test $? = 1 || fail=1
+test -s out && fail=1
+
+Exit $fail