@testim/testim-cli 4.154.0 → 4.154.57
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 +10 -0
- package/cli.js +53 -53
- package/cli.js.map +4 -4
- package/npm-shrinkwrap.json +460 -439
- package/package.json +2 -2
- package/meta.json +0 -1
package/README.md
CHANGED
|
@@ -155,6 +155,16 @@ The following are Environment Variables that the runner listens to:
|
|
|
155
155
|
* `"WEBDRIVER_DEBUG": "1"`
|
|
156
156
|
* `"OVERRIDE_SCHEDULER": "true`
|
|
157
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>`
|
|
158
168
|
|
|
159
169
|
License
|
|
160
170
|
----
|