Testing with OS provided arguments

[nour]

Hello,
I’m writing a(nother) CLI arg parser.
I want to test it by passing args through the OS.
I can write a shell script that would sequentially call my binary with arguments
but I thought I would ask if there is a more builtin way…

[rpkak]

you can do something like this in build.zig:

const std = @import("std");

pub fn build(b: *std.Build) void {
    // const mod = ...

    const test_exe = b.addExecutable(.{
        .name = "test_exe",
        .root_module = mod,
    });

    const run = b.addRunArtifact(test_exe);
    run.addArgs(&.{ "arg", "moreargs" });

    run.expectExitCode(0);
    run.expectStdOutEqual("output");

    const test_step = b.step("test", "run tests");

    test_step.dependOn(&run.step);
}

[Southporter]

In addition, you can also allow for tests to be run on the full args passed to the build command:

    // This allows the user to pass arguments to the application in the build
    // command itself, like this: `zig build test -- arg1 arg2 etc`
    if (b.args) |args| {
        run_cmd.addArgs(args);
    }

The rest would be like @rpkak laid out.

[squeek502]

More options for how to do this in this thread:

How to write integration tests for CLI utilities?

Let’s say I am writing a CLI utility, which, say, prints hello world: // ./main.zig const std = @import("std"); pub fn main() !void { try std.io.getStdOut().writeAll("hello world"); } Now, I want to write an integration test to run the utility and check its output, something like this: // ./tests.zig const std = @import("std"); test "it prints hello world" { const exe_path: []const u8 = get_exe_path(); const exec_result = try std.ChildProcess.exec(.{ .allocator = std.tes…

[nour]

Thank you all for your help!