[[ ]] extended test in Bash Scripting - Time & Space Complexity

Time Complexity: [[ ]] extended test

O(n)

Understanding Time Complexity

We want to understand how the time it takes to run a bash script using the [[ ]] extended test changes as the input grows.

Specifically, we ask: how does the number of checks scale when testing multiple conditions?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#!/bin/bash

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

This script loops over all items in the current folder and checks if each is a regular file and readable.

Identify Repeating Operations

• Primary operation: The for-loop iterates over each file in the directory.
• How many times: Once for each file found (n times).
• Inside the loop: The [[ ]] test checks two conditions per file.

How Execution Grows With Input

As the number of files increases, the script checks each file once with two conditions.

Input Size (n)	Approx. Operations
10	About 20 condition checks (2 per file)
100	About 200 condition checks
1000	About 2000 condition checks

Pattern observation: The total checks grow linearly with the number of files.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows directly in proportion to the number of files checked.

Common Mistake

[X] Wrong: "The [[ ]] test runs in constant time no matter how many files there are."

[OK] Correct: Each file requires its own check, so the total time grows with the number of files.

Interview Connect

Understanding how loops and condition checks scale helps you write efficient scripts and explain your reasoning clearly in interviews.

Self-Check

What if we added a nested loop inside the for-loop that also checks each file? How would the time complexity change?

Practice

1. What does the [[ ]] construct do in a bash script?

easy

A. It tests conditions like comparing strings or numbers.

B. It defines a function in bash.

C. It creates a new variable.

D. It runs a command in the background.

Solution

1. Step 1: Understand the purpose of [[ ]]

   The [[ ]] syntax is used in bash to test conditions such as string comparison, number comparison, and file checks.

2. Step 2: Compare with other options

   Options B, C, and D describe other bash features unrelated to [[ ]].

3. Final Answer:

   It tests conditions like comparing strings or numbers. -> Option A

4. Quick Check:

   [[ ]] = condition test [OK]

Hint: Remember: [[ ]] is for testing conditions in bash [OK]

Common Mistakes:

• Confusing [[ ]] with function definition syntax
• Thinking [[ ]] creates variables
• Assuming [[ ]] runs commands

2. Which of the following is the correct syntax to check if variable var equals "hello" using [[ ]]?

easy

A. [[ $var != "hello" ]]

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

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

D. [[ $var -eq "hello" ]]

Solution

1. Step 1: Identify correct string comparison operator in [[ ]]

   In bash, inside [[ ]], the operator for string equality is ==. -eq is for numeric equality. === is invalid.

2. Step 2: Check each option

   [[ $var != "hello" ]] checks inequality. [[ $var -eq "hello" ]] uses numeric -eq on string (error). [[ $var === "hello" ]] uses invalid ===. [[ $var == "hello" ]] uses == correctly.

3. Final Answer:

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

4. Quick Check:

   String equality in [[ ]] uses == [OK]

Hint: Use == for string equality inside [[ ]] [OK]

Common Mistakes:

• Using === which is invalid in bash
• Using -eq for string comparison
• Using != when checking for equality

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

var=5
if [[ $var -gt 3 && $var -lt 10 ]]; then
echo "In range"
else
echo "Out of range"
fi

medium

A. In range

B. Out of range

C. Syntax error

D. No output

Solution

1. Step 1: Evaluate numeric conditions inside [[ ]]

   The variable var is 5. The condition checks if 5 is greater than 3 and less than 10, which is true.

2. Step 2: Determine which branch runs

   Since the condition is true, the script echoes "In range".

3. Final Answer:

   In range -> Option A

4. Quick Check:

   5 > 3 and 5 < 10 = true [OK]

Hint: Check each numeric condition carefully with && [OK]

Common Mistakes:

• Confusing -gt and -lt operators
• Using single & instead of &&
• Forgetting to quote variables (not critical here)

4. Identify the error in this bash snippet:

filename="test.txt"
if [[ -f $filename && -r $filename ]]
then
echo "File exists and readable"
fi

medium

A. Variable $filename not quoted

B. Wrong operator for file check

C. Missing closing bracket "]" for [[ ]]

D. Missing then keyword

Solution

1. Step 1: Check syntax of [[ ]] condition

   The condition starts with [[ and has matching closing ]]. So brackets are correct.

2. Step 2: Verify other parts

   The then keyword is missing after the condition line, which causes a syntax error.

3. Final Answer:

   Missing then keyword -> Option D

4. Quick Check:

   Every if condition must be followed by then [OK]

Hint: Always include then after if condition [OK]

Common Mistakes:

• Forgetting the then keyword
• Using single [ with && without escaping
• Ignoring variable quoting warnings

5. You want to check if a variable input is either "yes" or "y" (case insensitive) using [[ ]]. Which snippet correctly does this?

hard

A. [[ $input =~ ^(yes|y)$ ]]

B. [[ $input == "yes" || $input == "y" ]]

C. [[ ${input,,} == "yes" || ${input,,} == "y" ]]

D. [[ $input == "yes" && $input == "y" ]]

Solution

1. Step 1: Understand case-insensitive check

   To ignore case, convert input to lowercase using ${input,,} before comparison.

2. Step 2: Check logical OR condition

   We want to accept either "yes" or "y", so use || between comparisons.

3. Step 3: Evaluate options

   [[ ${input,,} == "yes" || ${input,,} == "y" ]] correctly converts to lowercase and uses OR. [[ $input == "yes" || $input == "y" ]] lacks case conversion. [[ $input =~ ^(yes|y)$ ]] uses regex but is case-sensitive. [[ $input == "yes" && $input == "y" ]] uses AND which requires both to be true, impossible here.

4. Final Answer:

   [[ ${input,,} == "yes" || ${input,,} == "y" ]] -> Option C

5. Quick Check:

   Use ${var,,} for lowercase and || for OR [OK]

Hint: Use ${var,,} to lowercase and || for OR in [[ ]] [OK]

Common Mistakes:

• Not converting input to lowercase
• Using && instead of || for alternatives
• Incorrect regex syntax inside [[ ]]