Tests ausführen und filtern

To run the tests in a file you call the compiler in test mode. The zig test command compiles and executes every test block it finds.

You give zig test the root source file. It pulls in tests from that file and from any file reached through @import.

After a run, Zig prints how many tests passed. A line like "All 7 tests passed" means every test block returned without an error.

On failure Zig prints the test's name, the assertion that broke, and a stack trace. The name you chose is what makes this easy to read.

Run just the tests you care about with --test-filter. Only tests whose name contains the given text are executed.

While fixing one feature you rerun only its tests, so feedback is fast. The --test-filter flag matches a substring of the test name.

Return the special error.SkipZigTest from a test to mark it skipped instead of failed, which is handy for not-yet-ready cases.

The summary tallies skipped tests apart from passed and failed, so a skip never hides a real problem in your suite.

In a real project you usually run tests through the build system instead. A configured zig build test step compiles and runs them.

A file with only test blocks and no main function still works with zig test. The test runner supplies the entry point for you.

Because running tests is a single command, you can do it after every change. Fast feedback is what keeps a Zig codebase trustworthy.

You only want to run tests whose names mention the word parse. Which command does that?

You ran tests with zig test, read the summary, filtered by name, skipped with error.SkipZigTest, and learned about zig build test. ✅