@testim/testim-cli 4.176.2 → 4.179.0
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 +3 -3
- package/cli.js +36 -36
- package/cli.js.map +3 -3
- package/npm-shrinkwrap.json +736 -316
- package/package.json +34 -1
package/README.md
CHANGED
|
@@ -157,14 +157,14 @@ The following are Environment Variables that the runner listens to:
|
|
|
157
157
|
|
|
158
158
|
### Running local runner
|
|
159
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 '
|
|
161
|
-
Example: `
|
|
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 'pnpm start'
|
|
161
|
+
Example: `pnpm start --token <token> --project <project> --grid <grid>`
|
|
162
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
163
|
Example: `node apps/runner/deploy/cli.js --token <token> --project <project> --grid <grid>`
|
|
164
164
|
|
|
165
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
166
|
named RUNNER_ENVIRONMENT to take the correct services configuration - the values are production (default), staging, development.
|
|
167
|
-
Example: `RUNNER_ENVIRONMENT=staging
|
|
167
|
+
Example: `RUNNER_ENVIRONMENT=staging pnpm start --token <token> --project <project> --grid <grid>`
|
|
168
168
|
|
|
169
169
|
License
|
|
170
170
|
----
|