Queue tests remotely
Queue tests to run on Momentic’s cloud infrastructure.
This command requires an API key to authenticate against Momentic’s servers.
Overview
Queue one or more tests that exist on Momentic Cloud to run on Momentic’s fully managed CI infrastructure. Results will be available in the Test results tab on the Momentic Cloud app.
Arguments
| Argument | Description | Required |
|---|---|---|
testPaths | One or more test paths. | Yes |
This command accepts one or more test paths as arguments. The test path is a lowercased version of the test name where spaces are replaced with dashes. For example, hello-world is the path for Hello World.
For convenience, you can copy a test’s path from the main directory view on Momentic Cloud:
Options
| Option | Description | Required |
|---|---|---|
-w, --wait | Wait for tests to finish running before exiting. The CLI will exit with code 1 if any tests fail or if the wait timeout elapses. | No |
--wait-timeout <waitTimeout> | The maximum number of seconds to wait for tests to complete. Only applicable when the wait flag is also specified. | No (default: 1800) |
--env <env> | Name of the environment to use when running tests. | No |
--url-override <urlOverride> | Fully qualified URL (e.g., https://www.google.com) to start all tests from. Overrides any default starting URL set from the test or environment. | No |
--custom-headers HEADER-1=value HEADER-2=value | Add or override HTTP headers to be sent on every network request that occurs during the test. If this option is provided, you must use -- to separate the options from the test names provided (e.g. momentic queue tests --custom-headers TEST=true -- my-test). | No |
--input-csv <inputCsv> | Run parametrized tests, loading inputs from the specified file on disk. If multiple tests are provided as arguments, a unique job will be created for every test/parameter combination. | No |
Limitations
Due to downstream infrastructure provider limitations, tests that run for over 10 minutes may be disrupted during scaling or upgrade events. If this occurs, the current test attempt will be marked as “cancelled” and the test will be automatically retried on another node. For long-running tests, we recommend configuring the number of retries to be at least 3.
Was this page helpful?