test command

  1. Usage
    1. Environments
  2. Options



Run model or package tests.

By default, tests are run for a Guild file in the current directory. PATH_OR_PACKGE may be specified to run tests in a different directory or for an installed package.

Use one or more ‑‑test options to run specific tests in the order specified. If no tests are specified, runs all of the tests defined in the referenced Guild file or package.

Use one or more ‑‑model or ‑‑operation options to limit tests to the specified models and operations respectively.

In cases where multiple models may be tested in a for‑each‑model step, you may use ‑‑one‑model to limit tests to the first model. This is useful for reducing the test time at the expense of test coverage.

By default all tests are run even if one or more tests fail. To stop testing on the first failed test, use ‑‑stop‑on‑fail.


Tests are run in the current environment. If you want to isolate tests from other environments, you must create a test-specific environment activate it before running test.


-t, --test [TEST]...

Run a specific test. May be used multiple times.

-m, --model MODEL

Only test operations for MODEL. May be used multiple times. Use with ‑‑operation to further limit tests.

-o, --operation NAME

Only test operation NAME. May be used multiple times. Use with ‑‑model to limit operation to specific models.

-1, --one-model

Only test operations for the first model in a for-each-model step.

-s, --stop-on-fail

Stop testing after the first failed test.

--gpus DEVICES

Limit availabe GPUs to DEVICES, a comma separated list of device IDs. By default all GPUs are available. Cannot beused with --no-gpus.


Disable GPUs for tests. Cannot be used with --gpu.

-y, --yes

Do not prompt before running tests.

--help Show command help and exit.
Guild AI version 0.5.1