@taqwright/lime-cli 0.30.0 → 0.31.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 +20 -2
- package/dist/index.js +311 -270
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -312,6 +312,19 @@ test fails it; `--diff <file>` takes a unified diff for CI.
|
|
|
312
312
|
flagging direct device use. It is the repo owner's declaration, committed and reviewed; the
|
|
313
313
|
recording rule and the assertion rule still apply.
|
|
314
314
|
|
|
315
|
+
**Your own locator helpers** are read too. A one-line wrapper over an Appium call
|
|
316
|
+
(`By hint(String v) { return AppiumBy.xpath("//*[@hint='" + v + "']"); }`) is picked up from the
|
|
317
|
+
repo's Java/Kotlin, so `hint("Username")` is checked as the xpath it builds, and the brief tells
|
|
318
|
+
the agent to write locators the same way. A helper lime-cli cannot read is declared in `lime.json`:
|
|
319
|
+
|
|
320
|
+
```json
|
|
321
|
+
{ "locatorHelpers": { "byLabel": "accessibility id",
|
|
322
|
+
"byHint": { "using": "xpath", "template": "//*[@hint='{0}']" } } }
|
|
323
|
+
```
|
|
324
|
+
|
|
325
|
+
A new locator written through a helper that is neither inferred nor declared **fails** `check`:
|
|
326
|
+
a locator that could not be read was not checked, and `check` never says it was.
|
|
327
|
+
|
|
315
328
|
`--lime-dir` writes `.lime/` next to your project: the recorded steps the agent converts
|
|
316
329
|
from, a `run.json` of what was recorded (goal, platform, cloud device), and the briefs.
|
|
317
330
|
**No credential is ever written there** — cloud credentials are re-read from
|
|
@@ -328,8 +341,8 @@ make that a failure instead, or `--agent none` to skip adaptation deliberately.
|
|
|
328
341
|
|
|
329
342
|
### Your suite is not taqwright
|
|
330
343
|
|
|
331
|
-
`lime-cli export` handles any of the frameworks LIME supports — pytest, JUnit 5,
|
|
332
|
-
WebdriverIO, C# NUnit, taqwright — and works the rest out from the repo itself:
|
|
344
|
+
`lime-cli export` handles any of the frameworks LIME supports — pytest, JUnit 5, Java +
|
|
345
|
+
Cucumber, RSpec, WebdriverIO, C# NUnit, taqwright — and works the rest out from the repo itself:
|
|
333
346
|
|
|
334
347
|
```sh
|
|
335
348
|
cd your-test-repo
|
|
@@ -348,6 +361,11 @@ claude -p "Read .lime/ADAPT.md and follow it exactly." \
|
|
|
348
361
|
--output-format stream-json --verbose --permission-mode acceptEdits
|
|
349
362
|
```
|
|
350
363
|
|
|
364
|
+
On a **Cucumber** suite the test is a scenario in a `.feature` file: the brief lists every step
|
|
365
|
+
the project already defines so the agent reuses them, puts new steps beside the existing step
|
|
366
|
+
classes and keeps locators in page objects. `lime-cli check` treats the scenario and its step
|
|
367
|
+
definitions as the test, and `lime-cli verify` runs only the new scenario, by name.
|
|
368
|
+
|
|
351
369
|
Override anything it guessed with `--framework` and `--dest`. If you would rather lime-cli drive
|
|
352
370
|
the agent for you, that is `lime-cli adapt`.
|
|
353
371
|
|