Linux test Command Summary with Examples Tutorial

Examples of the Linux test Command

Intermediate

Learn to evaluate an expression in a shell script at the Linux command line.

Video Tutorial

Videos can also be accessed from the YouTube Linux Essentials Playlist on YouTube.

Linux test Command Summary with Examples (3:58)

Video Script

The Command and Why You Need It

Our ninety-third word, or command to memorize is test from our category Workflow.

test allows you to evaluate an expression.

Common Linux test Options

-options	description
`--help`	Print help screen
`--version`	Show version information

Recall from videos (tutorials) #87 to #92, we've been building a script to demonstrate workflow, here we'll use test at the command line, and return to programming a script in our next few videos (tutorials).

Before we start, it helps to think of commands as mini programs and most follow this structure: command -option(s) argument(s).

The test command has 2 options and the argument is an expression, which is something to evaluate, like is 10 greater than 9. Also note, square brackets [ ] around the expression really does the same thing.

Like most commands, help is available with double-dash --help, that is, if you're using the test program that is not built-in to your shell (otherwise see man bash). Okay, test evaluates strings, integers and files and gives an exit status of 0 for true and other integers if it's false, giving us program logic.

So why is test an important command? Well, you need a way to interpret these conditions. And now you know how to do that.

Demonstration

Okay, the best way to embed this in your memory is by typing in your own terminal window.

Find this on your Mac using a program called Terminal. On Linux use Terminal or Konsole, and currently Microsoft is adding this functionality to Windows.

Here we go. As with other built-ins, type -a tells us whether we have multiple versions, which can impact how you find help, for example.

$ type -a test test is a shell builtin test is /usr/bin/test

As mine did.

And then, a test of integers. Let's start with that in a test 10 = 10

$ test 10 = 10 $ _

And it looks like nothing happened. Well actually, it did, but we need to go get the exit status, like this with echo $?.

$ echo $? 0

And zero is for success (true), as I mentioned.

Or, we could do this in brackets (a synomyn). Is [ joe = joe ].

$ [ joe = joe ]; echo $? 0

And exit status here says true. But test joe blo = joe blo.

$ test joe blo = joe blo; echo $? -bash: test: too many arguments 2

And bash will yell at you if you don't surround it in quotes. We know about that one (because it then becomes four items to test instead of two).

And then on files, using options that say test -e, for does it exist? Then the file name, let's say we go look for our .bashrc file, and the exit status here is true.

$ test -e .bashrc; echo $? 0

And last, just for curiousity, let's see how test interprets nothing.

$ test; echo $? 1

False, hmm, interesting.

A Final Tip

Okay now you know how to use test. And you know the syntax for commands, options and arguments.

One last tip about the test command. So it's likely you'll see test used more often with brackets [ ], but really it is up to you.

Okay, thanks for visiting today. I hope this was a helpful introduction to the test command.

Learn More About The Series

For an overview of the 100 videos, the 8 quizzes, a cheat sheet, the categories and a Q&A section, visit:

Linux test Command Summary with Examples