@testim/testim-cli 4.149.0 → 4.150.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -10,7 +10,6 @@ For the live and up to date documentation of this tool please check out [this gu
10
10
 
11
11
  ### Installation
12
12
 
13
-
14
13
  Install the testim CLI globally:
15
14
 
16
15
  ```sh
@@ -156,8 +155,18 @@ The following are Environment Variables that the runner listens to:
156
155
  * `"WEBDRIVER_DEBUG": "1"`
157
156
  * `"OVERRIDE_SCHEDULER": "true`
158
157
 
158
+ ### Running local runner
159
+ To test `runner` code changes by locally running executions via the CLI, you can do any of the following:
160
+ 1. Go to the Runner folder, (i.e cd apps/runner) and copy-paste a CLI command - remove the 'testim' command and instead do 'yarn start'
161
+ Example: `yarn start --token <token> --project <project> --grid <grid>`
162
+ 2. You can follow the instructions on runner's [DOC.md](./DOC.md) file, to create a beta version - than, you can do: node {{full path to runner folder}}/deploy/cli.js
163
+ Example: `node apps/runner/deploy/cli.js --token <token> --project <project> --grid <grid>`
164
+
165
+ Important note - due to multi region support, when you want to run local runner against non-production environments, you will need to add an env var
166
+ named RUNNER_ENVIRONMENT to take the correct services configuration - the values are production (default), staging, development.
167
+ Example: `RUNNER_ENVIRONMENT=staging yarn start --token <token> --project <project> --grid <grid>`
159
168
 
160
169
  License
161
170
  ----
162
171
 
163
- © 2014-2019 Testim. All Rights Reserved.
172
+ © 2014-2025 Testim. All Rights Reserved.