captain quarantine

Execute a test-suite and modify its exit code based on quarantined tests.

This is a specialized version of captain run without support for targeted retries and uploading test results to Captain Cloud.


captain quarantine [suite-id] [flags]


captain quarantine example-suite-id


--command <COMMAND>

Required. The command you use to run your tests. You can also specify this with the shorthand -c <COMMAND>.

--config-file <PATH_TO_CONFIG>

Defaulted. Overrides the location of the Captain CLI config file.

--framework <STRING>

Configurable. The framework of the test suite. This is required if --language is set.

--language <STRING>

Configurable. The programming language of the test suite. This is required if --framework is set.


Required. The identifier of the test suite. This value should be unique to your Captain organization.

When neither --suite-id nor the environment variable CAPTAIN_SUITE_ID are specified, then the first positional argument will be treated as the suite ID. For example, if you run captain quarantine example-suite-id then example-suite-id will be used for the suite ID.

Configurable. Prints a summary of all tests to the console


Configurable. Disables most default output.

--reporter <TYPE=OUTPUT_PATH>

Configurable. One or more TYPE=OUTPUT_PATH (e.g rwx-v1-json=path/to/ouput.json) pairs to enable different reporting options.

Available reporters are rwx-v1-json, junit-xml, markdown-summary, and github-step-summary.

--test-results <STRING>

Required. A filepath to the native test runner's test results output. This option supports globs for multiple result files.


If set, Captain CLI will update its internal storage files under .captain with the latest test results, such as flaky tests and test timings.