// Guide for running Nanvix tests with z. Use this when asked to run unit tests, integration tests, or the full test suite.
Guide for Nanvix CI and GitHub Actions workflow behavior, including local pipeline execution and matrix coverage. Use this when asked about CI checks, workflow failures, or release flow.
Guide for developing, building, and running Nanvix user-space applications across supported runtimes and languages. Use this when asked about guest app implementation or execution.
Guide for creating and modifying Nanvix libraries under src/libs, including guest no_std and host std crates. Use this when asked about library architecture or crate changes.
Guide for developing and debugging Nanvix daemons, including guest daemons and host linuxd behavior. Use this when asked about daemon architecture or daemon changes.
Guide for modifying and debugging the Nanvix kernel architecture and kernel-call paths. Use this when asked about kernel internals or kernel implementation changes.
Guide for writing, running, and debugging Nanvix unit, integration, and system tests in Rust and C/C++. Use this when asked about test implementation or failures.
| name | test |
| description | Guide for running Nanvix tests with z. Use this when asked to run unit tests, integration tests, or the full test suite. |
Use this skill when the user asks to run tests on Nanvix. This covers unit tests, system
integration tests, and the combined test suite exposed through the z utility.
doc/setup.md.build skill)../z build -- run-unit-tests
./z build -- run-nanvix-tests
Test configurations are auto-selected based on deployment mode:
test/test-standalone.toml (Linux), test/test-standalone-windows.toml (Windows)test/test-single_process.tomltest/test-l2.tomltest/test-multi_process.toml./z build -- test
On Windows, unit tests can be run natively through z.ps1:
.\z.ps1 build -- run-unit-tests
System integration tests are also available on Windows for standalone mode
(DEPLOYMENT_MODE=standalone) on microvm machines:
.\z.ps1 build -- run-nanvix-tests
Single-process, L2 and multi-process deployment modes remain Linux-only as they require
nanvixd with network namespace support.
build skill).LOG_LEVEL=trace or LOG_LEVEL=debug for more verbose output when diagnosing failures.troubleshooting skill for deeper diagnosis of runtime and test failures.