zig/test/standalone/issue_794/main.zig

const c = @cImport(@cInclude("foo.h"));
const std = @import("std");
const testing = std.testing;

test "c import" {
    comptime try testing.expect(c.NUMBER == 1234);
}
add test for addIncludeDir for test step 2018-03-17 22:19:23 +00:00			`const c = @cImport(@cInclude("foo.h"));`
			`const std = @import("std");`
std.debug.assert: remove special case for test builds Previously, std.debug.assert would `@panic` in test builds, if the assertion failed. Now, it's always `unreachable`. This makes release mode test builds more accurately test the actual code that will be run. However this requires tests to call `std.testing.expect` rather than `std.debug.assert` to make sure output is correct. Here is the explanation of when to use either one, copied from the assert doc comments: Inside a test block, it is best to use the `std.testing` module rather than assert, because assert may not detect a test failure in ReleaseFast and ReleaseSafe mode. Outside of a test block, assert is the correct function to use. closes #1304 2019-02-08 23:18:47 +00:00			`const testing = std.testing;`
add test for addIncludeDir for test step 2018-03-17 22:19:23 +00:00
			`test "c import" {`
update usage of std.testing in behavior and standalone tests 2021-05-04 19:23:22 +01:00			`comptime try testing.expect(c.NUMBER == 1234);`
add test for addIncludeDir for test step 2018-03-17 22:19:23 +00:00			`}`