Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/SGizek/Raiku/llms.txt

Use this file to discover all available pages before exploring further.

raiku test provides a uniform interface for running tests across all eight languages supported by Raiku. Instead of remembering whether a package uses pytest, cargo test, go test, or zig build test, you simply pass the package name and raiku test figures out the right runner automatically. It resolves the package’s cache directory, selects the first available test runner for the package’s language (in priority order), and streams the test output directly to your terminal. The exit code mirrors the test runner’s, making raiku test suitable for use in CI pipelines.

Usage

raiku test PACKAGE [--version VER] [--runner CMD]

Arguments

ArgumentDescription
PACKAGEName of the installed package to test

Flags

FlagDefaultDescription
--versionlatest installedTest a specific installed version of the package
--runnerauto-detectedOverride the test runner command (space-separated, e.g. pytest -x)

Auto-Detection by Language

raiku test tries each runner in the priority order shown below, using shutil.which to check whether the binary is available on the host system:
LanguagePriorityRunnerCommand
Python1pytestpytest -v
Python2unittestpython -m unittest discover -v
Rust1cargo testcargo test
C1make testmake test
C++1ctestcmake --build build --target test
C++2cmakectest --test-dir build -V
Zig1zig build testzig build test
Java1mvnmvn test -q
Java2gradlegradle test
C#1dotnet testdotnet test
Go1go testgo test ./...
If no runner is found for the package’s language, raiku test prints a helpful message and suggests installing the appropriate toolchain or using --runner to specify a custom command.
Run raiku doctor to verify that all test tools for your languages are installed and accessible. raiku doctor --language Python shows the specific status of Python tooling.

Behavior

  • Tests run inside the package’s cache directory (~/.raiku/cache/<Language>/<name>/<version>/).
  • The runner and full command are printed before execution so you know exactly what is being run.
  • raiku test exits with the test runner’s exit code, so $? reliably indicates pass or fail.
  • If multiple versions of a package are installed, the latest is used unless --version is specified.

Examples

raiku test fast-math

Sample Output

Testing fast-math v1.2.0 [Python] in ~/.raiku/cache/Python/fast-math/1.2.0

  Runner:  pytest
  Command: pytest -v

========================= test session starts ==========================
platform linux -- Python 3.12.2, pytest-8.1.1
collected 24 items

src/test_fast_math.py::test_add          PASSED  [  4%]
src/test_fast_math.py::test_multiply     PASSED  [  8%]
...
========================= 24 passed in 0.42s ===========================

✓ Tests passed for 'fast-math'.
After raiku install, run raiku test PACKAGE immediately to verify the package works correctly in your local environment before using it in your project.

Build docs developers (and LLMs) love