Zig Academy · 课时

编写 test 代码块

让测试紧邻您的代码。

编写 test 代码块 是 CoddyKit 上的免费 Zig Academy 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Zig Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Zig Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Tests Live in Your Code

In Zig you do not need a separate test file. A test block sits right beside the code it checks, in the very same source file.

The test Keyword

You start a test with the test keyword, a name in quotes, and a block. The compiler collects every one of these for you.

test "adds two numbers" {
    // checks go here
}

Name Your Tests Clearly

The string after test is its name. A clear name like "parses empty input" shows up in the report and tells you what failed.

test "parses empty input" {}

Import std to Assert

Most tests need helpers, so you bring in the standard library at the top with an @import call and use std.testing inside.

const std = @import("std");

A First Real Test

Inside the block you compute something and check it. Here expect passes only when the boolean condition is true.

test "two plus two" {
    try std.testing.expect(2 + 2 == 4);
}

Tests Can Fail

Assertion helpers return an error when the check is false. That is why you write try before them, letting the failure end the test.

try std.testing.expect(1 == 2);

Test a Function You Wrote

A test usually calls one of your own functions and checks its result. The function and the test can share the same file.

fn add(a: i32, b: i32) i32 {
    return a + b;
}

Checking the Result

Now exercise that function from a test and confirm the output is what you expect with a single expect call.

test "add works" {
    try std.testing.expect(add(2, 3) == 5);
}

Many Tests, One File

You can stack as many test blocks as you like. Each runs in isolation, so a failure in one does not block the others.

Tests Are Compiled Code

A test block is normal Zig, fully type-checked. If it does not compile, the test run stops before anything even executes.

Why Inline Tests Help

Keeping checks next to the code means tests evolve with it. When you change a function, its test is right there to update.

Quick Check

You want to declare a unit test in a Zig source file. What is the right shape?

Recap

You met the test block: named, inline, fully compiled Zig that you assert with try. Tests live right next to the code they protect. ✅

常见问题解答

「编写 test 代码块」课时是免费的吗？

是的 — 「编写 test 代码块」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Zig Academy 课程的其余内容，请升级到 CoddyKit PRO。 Zig Academy 课程共包含 4 节课。

「编写 test 代码块」这节课中我会学到什么？

让测试紧邻您的代码。你通过在浏览器中直接运行的动手代码来练习 Zig Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Zig Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Zig Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「编写 test 代码块」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Zig Academy 课中编写并运行代码吗？

能。每节 Zig Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Zig Academy