@taqwright/lime-cli 0.34.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.
Files changed (3) hide show
  1. package/README.md +15 -2
  2. package/dist/index.js +318 -285
  3. 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
@@ -520,8 +532,9 @@ lime-cli scenarios import # dry run of docs/e2e-flows.csv
520
532
  lime-cli scenarios import --sync --yes # apply; retire flows the file no longer lists
521
533
  ```
522
534
 
523
- `import` reads the plan by its column names (`id, flow, covers, feature, persona, steps,
524
- expected, platforms`), always shows LIME's dry run first, and changes the board only with
535
+ `import` reads the plan by its column names (`id, flow, covers, feature, persona, runs_after,
536
+ steps, expected, platforms`; `runs_after` lists the ids of the flows a flow starts after, which
537
+ the board draws as arrows), always shows LIME's dry run first, and changes the board only with
525
538
  `--yes`. A flow keeps its card across imports by its id. `--sync` retires flows the file no
526
539
  longer lists (hidden, history kept, back if the id returns) and refuses to retire more than a
527
540
  third of the plan unless `--force`. To keep the board in step with the repo, run it on every