Part 16. Testing and Debugging

Zig has a built-in test system. You do not need a separate testing library to start writing tests.

10 items

Section	Title
1	Zig Test Framework
2	Writing Unit Tests
3	Table-Driven Tests
4	Fuzz Testing
5	Debug Builds
6	Stack Traces
7	Assertions
8	Using GDB and LLDB
9	Memory Debugging
10	Benchmarking Code

Writes › Book › Zig › Part 16. Testing and Debugging ›

Zig Test Framework

Zig has a built-in test system. You do not need a separate testing library to start writing tests.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Writing Unit Tests

A unit test checks one small piece of code in isolation.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Table-Driven Tests

A table-driven test checks many input cases with one test loop.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Fuzz Testing

Fuzz testing means testing a program with many generated inputs.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Debug Builds

A debug build is a build made for finding mistakes.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Stack Traces

A stack trace shows how your program reached a failure.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Assertions

An assertion is a check that must be true while the program runs.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Using GDB and LLDB

GDB and LLDB are debuggers.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Memory Debugging

Memory debugging means finding mistakes in how a program uses memory.

Writes › Book › Zig › Part 16. Testing and Debugging ›

Benchmarking Code

Benchmarking measures how fast code runs.