Script testing strategies in Bash Scripting - Step-by-Step Execution

Concept Flow - Script testing strategies

Write script

↓

Add test cases

↓

Run script with test inputs

↓

Check outputs

↓

Compare with expected results

↓

Use script

↓

Repeat tests

This flow shows writing a script, adding tests, running them, checking outputs, and fixing errors until tests pass.

Execution Sample

Bash Scripting

#!/bin/bash
# Simple test for greeting function
say_hello() {
  echo "Hello, $1!"
}
result=$(say_hello Alice)
echo "$result"

This script defines a function that greets a name and tests it by calling with 'Alice' and printing the result.

Execution Table

Step	Action	Input	Output	Result
1	Define function say_hello	-	-	Function ready
2	Call say_hello with 'Alice'	Alice	Hello, Alice!	Output captured
3	Print result	-	Hello, Alice!	Output matches expected
4	Compare output to expected	Hello, Alice!	Hello, Alice!	Test Pass

💡 Test passes because output matches expected greeting

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
result	empty	Hello, Alice!	Hello, Alice!	Hello, Alice!

Key Moments - 3 Insights

Why do we compare the script output to expected results?

Comparing output to expected results (see execution_table step 4) confirms the script works correctly for given inputs.

What if the output does not match expected?

If output differs (fail branch in concept_flow), we fix the script and rerun tests until outputs match.

Why add test cases before running the script?

Adding test cases early (concept_flow step 2) helps catch errors quickly and ensures script behaves as intended.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'result' after step 2?

A Hello, Alice!

B empty

C Hello, World!

D Error

💡 Hint

Check variable_tracker row for 'result' after Step 2

At which step does the script output get compared to the expected result?

A Step 1

B Step 3

C Step 4

D Step 2

💡 Hint

See execution_table 'Compare output to expected' action

If the output was 'Hello, Bob!' instead of 'Hello, Alice!', what would happen next?

A Test passes

B Script is fixed and tests rerun

C Script is used as is

D Test is skipped

💡 Hint

Refer to concept_flow where Fail leads to fixing script and repeating tests

Concept Snapshot

Script Testing Strategies:
1. Write your script.
2. Add test cases with expected outputs.
3. Run script with test inputs.
4. Check actual output.
5. Compare output to expected.
6. Fix script if tests fail and repeat.

Full Transcript

Script testing strategies involve writing a script and then creating test cases to check if it works correctly. You run the script with test inputs and capture the output. Then you compare this output to what you expect. If they match, the test passes and you can use the script. If not, you fix the script and test again. This cycle continues until all tests pass, ensuring your script works as intended.

Practice

1. Why is it important to test a bash script before using it in real tasks?

easy

A. To reduce the script's file size

B. To make the script run faster automatically

C. To change the script's language to another programming language

D. To find and fix errors early, avoiding bigger problems later

Solution

1. Step 1: Understand the purpose of testing scripts

   Testing helps catch mistakes before the script runs on important data or systems.

2. Step 2: Identify the benefit of early error detection

   Finding errors early prevents failures and saves time and effort in fixing issues later.

3. Final Answer:

   To find and fix errors early, avoiding bigger problems later -> Option D

4. Quick Check:

   Testing = Catch errors early [OK]

Hint: Testing finds errors before damage happens [OK]

Common Mistakes:

• Thinking testing makes scripts faster automatically
• Confusing testing with rewriting code
• Believing testing reduces file size

2. Which command is used to run a bash script with debugging output showing each command executed?

easy

A. bash -e script.sh

B. bash -v script.sh

C. bash -x script.sh

D. bash -c script.sh

Solution

1. Step 1: Recall bash debugging options

   The -x option runs the script showing each command before execution.

2. Step 2: Differentiate from other options

   -v prints shell input lines, -e exits on error, -c runs commands from string.

3. Final Answer:

   bash -x script.sh -> Option C

4. Quick Check:

   Debug with -x = bash -x [OK]

Hint: Use bash -x to see commands run step-by-step [OK]

Common Mistakes:

• Confusing -v with -x for debugging
• Using -e expecting debug output
• Trying -c without command string

3. What will be the output of this script when run with bash -x test.sh?

#!/bin/bash
x=5
if [ $x -gt 3 ]; then
  echo "Greater"
else
  echo "Smaller"
fi

medium

A. + x=5
+ '[' 5 -gt 3 ']'
+ echo 'Greater'
Greater

B. Greater

C. + x=5
+ echo 'Greater'
Greater

D. Smaller

Solution

1. Step 1: Understand bash -x output

   Running with -x prints each command with a plus sign before executing it.

2. Step 2: Trace the script commands

   Commands x=5, the test [ $x -gt 3 ], and echo "Greater" are printed before output.

3. Final Answer:

   + x=5 + '[' 5 -gt 3 ']' + echo 'Greater' Greater -> Option A

4. Quick Check:

   bash -x shows commands with + [OK]

Hint: bash -x shows commands with + before output [OK]

Common Mistakes:

• Ignoring the debug lines starting with +
• Choosing output without debug info
• Confusing else branch output

4. This script is intended to check if a file exists and print a message, but it fails. What is the error?

#!/bin/bash
filename="myfile.txt"
if [ -f $filename ]
then
  echo "File exists"
else
  echo "File missing"
fi

medium

A. The if statement syntax is incorrect; should use double brackets [[ ]]

B. Missing quotes around $filename can cause errors if filename has spaces

C. The script needs to use -e instead of -f to check file existence

D. The echo commands must be inside curly braces { }

Solution

1. Step 1: Identify variable usage in test condition

   The variable $filename is unquoted, which can cause errors if it contains spaces.

2. Step 2: Understand quoting importance in bash tests

   Quoting variables prevents word splitting and errors in test expressions.

3. Final Answer:

   Missing quotes around $filename can cause errors if filename has spaces -> Option B

4. Quick Check:

   Quote variables in tests = Missing quotes around $filename can cause errors if filename has spaces [OK]

Hint: Always quote variables in test conditions [OK]

Common Mistakes:

• Thinking [[ ]] is required instead of [ ]
• Confusing -f and -e options
• Believing echo needs braces

5. You want to test a script that processes user input and exits with code 0 on success or 1 on failure. Which strategy best helps automate testing this behavior?

hard

A. Write test cases that run the script with different inputs and check the exit code using $?

B. Only run the script manually and watch the output on screen

C. Use echo statements inside the script without checking exit codes

D. Rename the script file to .test and run it without arguments

Solution

1. Step 1: Understand exit codes in bash scripts

   Scripts use exit codes to signal success (0) or failure (non-zero).

2. Step 2: Automate testing by running script with inputs and checking $?

   Running script with inputs and verifying $? confirms correct behavior automatically.

3. Final Answer:

   Write test cases that run the script with different inputs and check the exit code using $? -> Option A

4. Quick Check:

   Test exit codes with $? = Write test cases that run the script with different inputs and check the exit code using $? [OK]

Hint: Check $? after running script to verify success/failure [OK]

Common Mistakes:

• Relying only on manual output checks
• Ignoring exit codes in tests
• Assuming renaming files triggers tests