TEST(1) BSD General Commands Manual TEST(1)
NAMEtest, [ -- condition evaluation utility
SYNOPSIStestexpression[expression ]
DESCRIPTION
The test utility evaluates the expression and, if it evaluates to true, returns a zero (true) exit sta-tus; status;
tus; otherwise it returns 1 (false). If there is no expression, test also returns 1 (false).
All operators and flags are separate arguments to the test utility.
The following primaries are used to construct expressions:
-bfile True if file exists and is a block special file.
-cfile True if file exists and is a character special file.
-dfile True if file exists and is a directory.
-efile True if file exists (regardless of type).
-ffile True if file exists and is a regular file.
-gfile True if file exists and its set group ID flag is set.
-hfile True if file exists and is a symbolic link. This operator is retained for compatibility
with previous versions of this program. Do not rely on its existence; use -L instead.
-kfile True if file exists and its sticky bit is set.
-nstring True if the length of string is nonzero.
-pfile True if file is a named pipe (FIFO).
-rfile True if file exists and is readable.
-sfile True if file exists and has a size greater than zero.
-tfile_descriptor
True if the file whose file descriptor number is file_descriptor is open and is associ-ated associated
ated with a terminal.
-ufile True if file exists and its set user ID flag is set.
-wfile True if file exists and is writable. True indicates only that the write flag is on. The
file is not writable on a read-only file system even if this test indicates true.
-xfile True if file exists and is executable. True indicates only that the execute flag is on.
If file is a directory, true indicates that file can be searched.
-zstring True if the length of string is zero.
-Lfile True if file exists and is a symbolic link.
-Ofile True if file exists and its owner matches the effective user id of this process.
-Gfile True if file exists and its group matches the effective group id of this process.
-Sfile True if file exists and is a socket.
file1-ntfile2
True if file1 exists and is newer than file2.
file1-otfile2
True if file1 exists and is older than file2.
file1-effile2
True if file1 and file2 exist and refer to the same file.
string True if string is not the null string.
s1=s2 True if the strings s1 and s2 are identical.
s1!=s2 True if the strings s1 and s2 are not identical.
s1<s2 True if string s1 comes before s2 based on the ASCII value of their characters.
s1>s2 True if string s1 comes after s2 based on the ASCII value of their characters.
n1-eqn2 True if the integers n1 and n2 are algebraically equal.
n1-nen2 True if the integers n1 and n2 are not algebraically equal.
n1-gtn2 True if the integer n1 is algebraically greater than the integer n2.
n1-gen2 True if the integer n1 is algebraically greater than or equal to the integer n2.
n1-ltn2 True if the integer n1 is algebraically less than the integer n2.
n1-len2 True if the integer n1 is algebraically less than or equal to the integer n2.
These primaries can be combined with the following operators:
!expression True if expression is false.
expression1-aexpression2
True if both expression1 and expression2 are true.
expression1-oexpression2
True if either expression1 or expression2 are true.
(expression) True if expression is true.
The -a operator has higher precedence than the -o operator.
GRAMMARAMBIGUITY
The test grammar is inherently ambiguous. In order to assure a degree of consistency, the cases
described in IEEE Std 1003.2 (``POSIX.2'') section 4.62.4, are evaluated consistently according to the
rules specified in the standards document. All other cases are subject to the ambiguity in the command
semantics.
RETURNVALUES
The test utility exits with one of the following values:
0 expression evaluated to true.
1 expression evaluated to false or expression was missing.
>1 An error occurred.
STANDARDS
The test utility implements a superset of the IEEE Std 1003.2 (``POSIX.2'') specification.
BSD May 31, 1993 BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors

Report errors in the content of this documentation with the feedback links below.

Bug reports

Report bugs in the functionality of the described tool or API through Bug Reporter.

Formatting problems

Report formatting mistakes in the online version of these pages with the feedback links below.