Penegasan dengan std.testing

Zig's assertion helpers live in std.testing. Pull it into a short name so each check reads cleanly inside your test blocks.

The simplest helper is expect. It takes one boolean and fails the test when that condition is false.

Every testing helper returns an error on failure, so you always prefix it with try. That is what makes the test stop and report.

To compare two values, reach for expectEqual. It checks equality and, on failure, prints both the expected and the actual value.

With expectEqual the first argument is the expected value and the second is what your code produced. Order shapes the failure message.

Two slices are equal when their elements match, not their pointers. Use expectEqualSlices and tell it the element type.

For text, expectEqualStrings compares two byte slices and prints a readable diff when they differ, which is perfect for output checks.

Sometimes a call should fail. Wrap it in expectError to assert it returns a specific error and not a value.

Floats rarely match exactly. Use expectApproxEqAbs with a small tolerance so tiny rounding differences do not fail your test.

When an assertion fails, Zig prints the expected and actual values right in the report. That diff usually points straight at the bug.

Match the helper to the data: expectEqual for scalars, slice and string helpers for sequences, expectError for the failure path.

You need to assert that two text values are exactly equal in a test. Which helper fits best?

You learned the std.testing toolkit: expect, expectEqual, slice and string checks, plus expectError. Each one needs try in front. ✅