@taqwright/lime-cli 0.35.0 → 0.36.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 +12 -0
- package/dist/index.js +316 -284
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -512,6 +512,18 @@ id-like name reports under its own name, and `report` says which. An explicit
|
|
|
512
512
|
{ "testCasePlan": "qa/flows.csv", "testCaseId": "\\[(TC-\\d+)\\]" }
|
|
513
513
|
```
|
|
514
514
|
|
|
515
|
+
#### Keys in `.env`, filled by you
|
|
516
|
+
|
|
517
|
+
```bash
|
|
518
|
+
lime-cli env --devices browserstack --open # or local, lambdatest, or several: local,browserstack
|
|
519
|
+
lime-cli env --devices browserstack --check # which keys are still empty (never prints a value)
|
|
520
|
+
```
|
|
521
|
+
|
|
522
|
+
`env` adds the keys the chosen way of recording needs to `.env`, empty, each with where to get
|
|
523
|
+
its value, and makes sure `.env` is gitignored. Fill the values in an editor, never in a chat. A
|
|
524
|
+
cloud run then takes its app id from `.env` (`BROWSERSTACK_APP_URL`, `LT_APP_URL`, and the
|
|
525
|
+
`_IOS_` ones), so it needs no `--app-url`. LambdaTest keys work under `LT_*` or `LAMBDATEST_*`.
|
|
526
|
+
|
|
515
527
|
#### Your flow plan on the board, from the command line
|
|
516
528
|
|
|
517
529
|
```bash
|