---
title: rattler-build test
---
<!--- This file is autogenerated. Do not edit manually! -->
# [rattler-build](index.md) test

Run a test for a single package

## Usage
```
rattler-build test [OPTIONS] --package-file <PACKAGE_FILE>
```

## Options
- <a id="arg---channel" href="#arg---channel">`--channel (-c) <CHANNELS>`</a>
:  Channels to use when testing
<br>May be provided more than once.
- <a id="arg---package-file" href="#arg---package-file">`--package-file (-p) <PACKAGE_FILE>`</a>
:  The package file or extracted package directory to test
<br>**required**: `true`
- <a id="arg---compression-threads" href="#arg---compression-threads">`--compression-threads <COMPRESSION_THREADS>`</a>
:  The number of threads to use for compression
<br>**env**: `RATTLER_COMPRESSION_THREADS`
- <a id="arg---test-index" href="#arg---test-index">`--test-index <TEST_INDEX>`</a>
:  The index of the test to run. This is used to run a specific test from the package
- <a id="arg---experimental" href="#arg---experimental">`--experimental`</a>
:  Enable experimental features
<br>**env**: `RATTLER_BUILD_EXPERIMENTAL`
- <a id="arg---v3" href="#arg---v3">`--v3`</a>
:  Enable V3 recipe fields and MatchSpec syntax
- <a id="arg---allow-insecure-host" href="#arg---allow-insecure-host">`--allow-insecure-host <ALLOW_INSECURE_HOST>`</a>
:  List of hosts for which SSL certificate verification should be skipped
<br>May be provided more than once.
- <a id="arg---channel-priority" href="#arg---channel-priority">`--channel-priority <CHANNEL_PRIORITY>`</a>
:  Channel priority to use when solving

## Modifying result
- <a id="arg---output-dir" href="#arg---output-dir">`--output-dir <OUTPUT_DIR>`</a>
:  Output directory for build artifacts.
<br>**env**: `CONDA_BLD_PATH`

## Description
Run a test for a single package

This creates a temporary directory, copies the package file into it, and then runs the indexing. It then creates a test environment that installs the package and any extra dependencies specified in the package test dependencies file.

With the activated test environment, the packaged test files are run:

* `info/test/run_test.sh` or `info/test/run_test.bat` on Windows * `info/test/run_test.py`

These test files are written at "package creation time" and are part of the package.

