ziglang/zig

Fork 274

Code Issues 154 Pull requests 83 Activity Actions 7

ability to read environment variables from unit tests #30833

New issue

Open

opened 2026年01月14日 19:37:30 +01:00 by andrewrk · 1 comment

andrewrk commented

2026年01月14日 19:37:30 +01:00

Owner

Copy link

Use case regressed in #30644.

Something simple like std.testing.environ would suffice. It should be a compile error when not testing to access this API.

Use case regressed in #30644. Something simple like `std.testing.environ` would suffice. It should be a compile error when not testing to access this API.

andrewrk added this to the 0.16.0 milestone

2026年01月14日 19:37:30 +01:00

andrewrk added the

labels

2026年01月14日 19:37:30 +01:00

andrewrk referenced this issue

2026年01月14日 19:37:46 +01:00

std: delete os.environ, os.argv, add new parameter to main, move process API to std.Io #30644

andrewrk referenced this issue

2026年01月14日 19:38:02 +01:00

std: delete os.environ, os.argv, add new parameter to main, move process API to std.Io #30644

matklad commented

2026年01月15日 13:01:26 +01:00

Copy link

FWIW, I think most of my uses of env from tests are actually cases where I need run-time parameters to tests, and env is more of a work-around:

passing update? flag to a snapshot-testing library
passing path to executables for integration tests
overriding parameters for "benchmark" tests

For all above use-cases, I think I'd actually prefer zig test test.zig -- --update-snapshots over UPDATE_SNAPSHOS=1 zig test test.zig, as I am parametrizing tests "cooperatively", and I don't need implicit propagation behavior of env vars.

At the same time, there's at least one case where I need specifically access to env: sometimes I use CI variable to sanity-check that dev behaviors (like skipping tests, or updating snapshots) cannot happen on CI. Here, I rely on vars being propagated automatically and implicitly, such that sanity check works even if I mess up something in build.zig or ci.yml.

FWIW, I think most of my uses of env from tests are actually cases where I need run-time parameters to tests, and env is more of a work-around: - passing `update?` flag to a snapshot-testing library - passing path to executables for integration tests - overriding parameters for "benchmark" tests For all above use-cases, I think I'd actually prefer `zig test test.zig -- --update-snapshots` over `UPDATE_SNAPSHOS=1 zig test test.zig`, as I am parametrizing tests "cooperatively", and I don't need implicit propagation behavior of env vars. At the same time, there's at least one case where I need specifically access to env: sometimes I use `CI` variable to sanity-check that dev behaviors (like skipping tests, or updating snapshots) cannot happen on `CI`. Here, I rely on vars being propagated automatically and implicitly, such that sanity check works even if I mess up something in build.zig or ci.yml.

murtaza referenced this issue

2026年01月15日 23:39:30 +01:00

testing: ability to read environment variables from unit tests #30851

No Branch/Tag specified

Branches Tags

master

poll

io-uring-update

llvm22

poll-ring

debug-file-leaks-differently

debug-file-leaks

hate-letter-to-std.os

i-am-a-foolish-fool

ProcessPrng

elfv2-dyn

jobserver

threadtheft

io-threaded-no-queue

0.15.x

Io.net

comptime-allocator

restricted-function-pointers

cli

wasm-linker-writer

wrangle-writer-buffering

sha1-stream

async-await-demo

fixes

0.14.x

ast-node-methods

spork8

macos-debug-info

make-vs-configure

fuzz-macos

main

sans-aro

ArrayList-reserve

incr-bug

llvm-ir-nosanitize-metadata

ci-tarballs

ci-scripts

threadpool

0.12.x

new-pkg-hash

json-diagnostics

more-doctests

rework-comptime-mutation

0.11.x

ci-perf-comment

stage2-async

0.10.x

autofix

0.9.x

aro

hcs

0.8.x

0.7.x

Labels

Clear labels

This proposal is planned.

The web application for interactive documentation and generation of its assets.

backend/c

The C backend outputs C source code.

backend/llvm

The LLVM backend outputs an LLVM bitcode module.

backend/self-hosted

The self-hosted backends produce machine code directly.

binutils

Zig's included binary utilities: zig ar, zig dlltool, zig lib, zig ranlib, zig objcopy, and zig rc.

breaking

Implementing this issue could cause existing code to no longer compile or have different behavior.

build system

The Zig build system - zig build, std.Build, the build runner, and package management.

debug info

docs

An issue with documentation, e.g. the language reference or standard library doc comments.

error message

This issue points out an error message that is unhelpful and should be improved.

frontend

Tokenization, parsing, AstGen, ZonGen, Sema, Legalize, and Liveness.

fuzzing

incremental

Reuse of internal compiler state for faster compilation.

lib/c

This issue relates to Zig's libc implementation and/or vendored libcs.

lib/compiler-rt

This issue relates to Zig's compiler-rt library.

lib/cxx

This issue relates to Zig's vendored libc++ and/or libc++abi.

lib/std

This issue relates to Zig's standard library.

lib/tsan

This issue relates to Zig's vendored libtsan.

lib/ubsan-rt

This issue relates to Zig's ubsan-rt library.

lib/unwind

This issue relates to Zig's vendored libunwind.

linking

Zig's integrated object file and incremental linker.

miscompilation

The compiler reports success but produces semantically incorrect code.

This issue suggests modifications. If it also has the "accepted" label then it is planned.

release notes

This issue or pull request should be mentioned in the release notes.

testing

This issue is related to testing the compiler, standard library, or other parts of Zig.

tier system

This issue tracks the support tier for a target.

zig cc

Zig as a drop-in C-family compiler.

zig fmt

The Zig source code formatter.

bounty

https://ziglang.org/news/announcing-donor-bounties

bug

Observed behavior contradicts documented or intended behavior.

contributor-friendly

This issue is limited in scope and/or knowledge of project internals.

downstream

An issue with a third-party project that uses this project.

enhancement

Solving this issue will likely involve adding new logic or components to the codebase.

infra

optimization

A task to improve performance and/or resource usage.

question

No questions on the issue tracker; use a community space instead.

regression

A bug that did not occur in a previous version.

upstream

An issue with a third-party project that this project uses.

No labels

Milestone

Clear milestone

No items

No milestone

0.16.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ziglang/zig#30833

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?