test command and [ ] syntax in Bash Scripting - Time & Space Complexity

Time Complexity: test command and [ ] syntax

O(n)

Understanding Time Complexity

We want to understand how the time taken by bash test commands grows as we check more conditions.

How does the number of checks affect the total time?

Scenario Under Consideration

Analyze the time complexity of the following bash snippet using test or [ ] syntax.

for file in *; do
  if [ -f "$file" ]; then
    echo "$file is a regular file"
  fi
done
    

This code loops over all items in the current folder and tests if each is a regular file.

Identify Repeating Operations

Look for repeated actions in the code.

• Primary operation: The test command [ -f "$file" ] runs once per file.
• How many times: It runs once for each item in the folder, so as many times as there are files.

How Execution Grows With Input

As the number of files grows, the number of test commands grows the same way.

Input Size (n)	Approx. Operations
10	10 test commands
100	100 test commands
1000	1000 test commands

Pattern observation: The number of tests grows directly with the number of files.

Final Time Complexity

Time Complexity: O(n)

This means the time grows in a straight line as the number of files increases.

Common Mistake

[X] Wrong: "The test command runs only once regardless of files."

[OK] Correct: The test runs inside the loop, so it runs once per file, not just once total.

Interview Connect

Understanding how loops and tests scale helps you write efficient scripts and answer questions about script speed.

Self-Check

"What if we added a nested loop inside that also runs tests? How would the time complexity change?"

Practice

1. What does the [ -f filename ] test check in a bash script?

easy

A. If filename is a directory

B. If filename is empty

C. If filename is executable

D. If filename exists and is a regular file

Solution

1. Step 1: Understand the -f test

   The -f option in [ ] checks if the file exists and is a regular file (not a directory or special file).

2. Step 2: Compare with other options

   -d checks for directory, -x for executable, and -s for non-empty file, so they don't match.

3. Final Answer:

   If filename exists and is a regular file -> Option D

4. Quick Check:

   -f means regular file check [OK]

Hint: Remember: -f means regular file exists [OK]

Common Mistakes:

• Confusing -f with -d for directories
• Forgetting spaces inside [ ]
• Using filename without quotes causing errors

2. Which of the following is the correct syntax to test if variable var is equal to string hello in bash?

easy

A. [ $var = hello ]

B. [ $var == hello ]

C. [ "$var" = "hello" ]

D. [ "$var" == hello ]

Solution

1. Step 1: Check quoting rules

   Variables should be quoted to avoid errors if empty or contain spaces, so "$var" is correct.

2. Step 2: Check operator correctness

   Single equals = is POSIX compliant for string comparison inside [ ]. Double equals == works in [[ ]] but not always in [ ].

3. Final Answer:

   [ "$var" = "hello" ] -> Option C

4. Quick Check:

   Quote variables and use = inside [ ] [OK]

Hint: Always quote variables and use = inside [ ] [OK]

Common Mistakes:

• Not quoting variables causing syntax errors
• Using == inside [ ] which may fail
• Missing spaces around brackets

3. What will be the output of this script snippet?

var=""
if [ -z "$var" ]; then
  echo "Empty"
else
  echo "Not Empty"
fi

medium

A. Empty

B. Not Empty

C. Syntax Error

D. No output

Solution

1. Step 1: Understand the -z test

   -z returns true if the string length is zero (empty string).

2. Step 2: Check variable value

   Variable var is set to empty string "", so [ -z "$var" ] is true and the if branch runs.

3. Final Answer:

   Empty -> Option A

4. Quick Check:

   -z tests empty string [OK]

Hint: Use -z to check empty strings [OK]

Common Mistakes:

• Not quoting variable causing errors
• Confusing -z with -n
• Expecting else branch to run

4. Identify the error in this bash condition:

if [ $num -gt 10 ]; then
  echo "Greater"
fi

medium

A. Missing spaces inside [ ]

B. Variable $num should be quoted

C. Wrong operator for numeric comparison

D. Missing then keyword

Solution

1. Step 1: Check variable usage in test

   When using variables in [ ], they should be quoted to avoid errors if empty or unset.

2. Step 2: Analyze the given code

   The code uses $num unquoted. If num is empty, the test becomes invalid syntax.

3. Final Answer:

   Variable $num should be quoted -> Option B

4. Quick Check:

   Always quote variables in [ ] to avoid syntax errors [OK]

Hint: Quote variables inside [ ] to prevent errors [OK]

Common Mistakes:

• Not quoting variables causing syntax errors
• Confusing numeric and string operators
• Forgetting spaces around brackets

5. You want to check if a file data.txt exists and is not empty before processing it in a script. Which condition correctly does this?

hard

A. [ -f data.txt ] && [ -s data.txt ]

B. [ -f data.txt -o -s data.txt ]

C. [ -f data.txt && -s data.txt ]

D. [ -f data.txt ] || [ -s data.txt ]

Solution

1. Step 1: Understand the tests

   -f checks if file exists and is regular file; -s checks if file size is greater than zero (not empty).

2. Step 2: Choose correct logical operator

   To require both conditions, use logical AND. Inside a single [ ], use -a; or chain separate tests with &&. Using && directly inside [ ] causes syntax error.

3. Step 3: Analyze options

   The option with && inside single [ ] has syntax error. Chained tests with && are clear and reliable. Options using -o or || apply OR logic, incorrect.

4. Final Answer:

   [ -f data.txt ] && [ -s data.txt ] -> Option A

5. Quick Check:

   Use && to combine separate [ ] tests [OK]

Hint: Use separate [ ] with && for AND conditions [OK]

Common Mistakes:

• Using -o or || which means OR, not AND
• Using && inside a single [ ] (syntax error)
• Not checking file size with -s