abq report list-tests
Outputs all tests for a specific worker & runner of a distributed ABQ report suite run.
abq report list-tests may be only be invoked after all workers for a given test suite run have
completed. If there are outstanding workers for a given test suite run, abq report list-tests will
error out without reporting test ids.
abq report list-tests only returns tests run before retries. Any retries will be missing from the listed test report.
Usage
abq report list-tests --run-id --worker [OPTIONS]
Examples
list tests for my-test-1 from worker 0 (from the default runner, 1)
abq report list-tests --run-id my-test-1 --worker 0 [OPTIONS]
list tests for my-test-1 from worker 1, runner 2
abq report list-tests --run-id my-test-1 --worker 1 --num 2 [OPTIONS]
Required Parameters
--run-id <RUN_ID>
The distributed run ID to fetch tests from.
In CI environments, abq report list-tests will attempt to infer the run ID from CI environment variables. See the CI platforms documentation.
You can also specify the run ID by setting the ABQ_RUN_ID environment variable.
Example: abq report list-tests --run-id my-test-1 --worker 0
--worker <WORKER>
The identity of the test worker to fetch tests from. This is the same value as passed to abq test --worker <WORKER>
Example: abq report list-tests -run-id my-test-1 --worker 0
Options
--num <RUNNER_NUM>
Each worker has one or more test runners. This is the number of the test runner whose tests abq will fetch.
If abq test's --num 1 (the default), this will always be 1 (which is the default value).
You can also specify this option with the shorthand -n
Examples:
abq report list-tests --run-id my-test-1 --worker 0 --num 2abq report list-tests --run-id my-test-1 --worker 0 --n 2
--access-token <ACCESS_TOKEN>
The RWX access token to use when fetching queue configuration information from a managed RWX queue.
You can also specify the access token by setting the RWX_ACCESS_TOKEN environment variable.
Example: abq report list-tests --run-id my-test-1 --worker 0 --access-token rwx_org_eyJhbGci
--queue-addr <QUEUE_ADDR>
The address of the queue to connect to.
When using a managed RWX queue, use
--access-token instead, which will
automatically fetch the queue address from a managed RWX queue. A queue
address is only needed if you are self-hosting a queue.
Example: abq report list-tests --run-id my-test-1 --worker 0 --queue-addr 10.0.0.1:9000
--tls-cert <TLS_CERT>
The path to the TLS certificate to use when exchanging messages with the queue.
When using a managed RWX queue, use
--access-token instead, which will
automatically fetch the TLS certificate from a managed RWX queue. A TLS
certificate is only needed if you are self-hosting a
queue.
Example: abq report list-tests --run-id my-test-1 --worker 0 --queue-addr 10.0.0.1:9000 --tls-cert ./cert.pem
--timeout-seconds <TIMEOUT_SECONDS>
The number of seconds to wait for tests to be available. If tests are not available after the specified number of seconds, abq report list-tests will exit with an error.
If there are active workers, abq report list-tests will exit immediately with an error. However, if all workers are complete, tests may still be pending before delivery to abq report list-tests.
The default value is 300.
Example: abq report list-tests --run-id mytest-1 --worker 0 --timeout-seconds 180
--token <TOKEN>
The token to use for authorizing messages sent to the queue. This is typically the user token that is used when running abq start.
When using a managed RWX queue, use
--access-token instead, which will
automatically fetch the token from a managed RWX queue. A token is only needed
if you are self-hosting a queue.
Example: abq report list-tests --run-id my-test-1 --worker 0 --queue-addr 10.0.0.1:9000 --token abqs_OSRMcU9W6YJkLyVDkzhJ4HCkrWHzEq
--help
Print detailed help information about the abq report list-tests command.
Example: abq report list-tests --help
-h
Print summarized help information about the abq report list-tests command.
Example: abq report list-tests -h