CTRL K

Chapter 1. Getting Started
- Starting a new project
Chapter 2. Strings
Chapter 3. Numbers
Chapter 4. Data Structures
- Using associative arrays
Chapter 5. Good Coding Practices
Chapter 6. Files and I/O
Chapter 7. Dates and Times
Chapter 8. Data and Text Processing
- Manipulating files with CLI one-liners
- Editing files in-place with CLI one-liners
Chapter 9. Testing and Debugging
Chapter 10. Data Formats and Serialization
Chapter 11. HTML and the Web

Chapter 1. Getting Started
- Starting a new project
Chapter 2. Strings
Chapter 3. Numbers
Chapter 4. Data Structures
- Using associative arrays
Chapter 5. Good Coding Practices
Chapter 6. Files and I/O
Chapter 7. Dates and Times
Chapter 8. Data and Text Processing
- Manipulating files with CLI one-liners
- Editing files in-place with CLI one-liners
Chapter 9. Testing and Debugging
Chapter 10. Data Formats and Serialization
Chapter 11. HTML and the Web

Chapter 9. Testing and Debugging

Bash Chapter 9.
Testing and Debugging

Printing debug output

Originally, debugging meant removing physical bugs that disrupted early computers.

In Bash, your terminal is essentially a REPL.

Bash doesn’t come with a built-in debugger like some other languages, but you can use built-in commands like set -x to trace what’s happening.

Bash doesn’t have a built-in testing framework, but you can write simple test functions.