Shell scripting · Lesson 3 of 31 · 8 minutes

Test guards

Use test commands as script-style guards.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Check deploy file
Run test -f scripts/deploy.sh.
Hint & worked example
Evaluate a file or string condition through its exit status rather than printed output.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
test -f scripts/deploy.sh
```
Remember: A successful test usually prints nothing; inspect $? or chain a command.
2
Check scripts directory
Run test -d scripts.
Hint & worked example
Evaluate a file or string condition through its exit status rather than printed output.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
test -d scripts
```
Remember: A successful test usually prints nothing; inspect $? or chain a command.
3
Write guard note
Run echo guard-reviewed > lab/guard.txt.
Hint & worked example
Write simple text to standard output. Prefer printf when exact formatting matters.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
echo guard-reviewed > lab/guard.txt
```
Remember: Redirection can overwrite an existing file before the command runs.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

test: Evaluate a file or string condition through its exit status rather than printed output.
A successful test usually prints nothing; inspect $? or chain a command.
echo: Write simple text to standard output. Prefer printf when exact formatting matters.
Redirection can overwrite an existing file before the command runs.

Worked example and expected result

$ test -f scripts/deploy.sh

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ test -d scripts

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ echo guard-reviewed > lab/guard.txt

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Test guards”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.A successful test usually prints nothing; inspect $? or chain a command.

Apply it elsewhere

Before adapting the test workflow from “Test guards” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Basename in scripts Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual