@taqwright/lime-cli 0.32.1 → 0.33.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 +22 -1
- package/dist/index.js +247 -237
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -482,7 +482,7 @@ It works from **any framework**, because it reads the report your runner already
|
|
|
482
482
|
|
|
483
483
|
| | |
|
|
484
484
|
|---|---|
|
|
485
|
-
| `--junit <file>` | JUnit XML — pytest, JUnit 5, WebdriverIO, RSpec, NUnit, Maestro |
|
|
485
|
+
| `--junit <file or folder>` | JUnit XML — pytest, JUnit 5, WebdriverIO, RSpec, NUnit, Maestro; a folder reads every `*.xml` in it (Maven Surefire's `target/surefire-reports`) |
|
|
486
486
|
| `--results <file>` | A Playwright JSON report, which is what taqwright writes |
|
|
487
487
|
| `--screens <dir>` | One JSON per failure, carrying the screen it died on — see below |
|
|
488
488
|
|
|
@@ -491,6 +491,27 @@ annotation that ties a test to its card. JUnit XML carries neither, so LIME matc
|
|
|
491
491
|
by spec path instead — run a repo scan (console → Scenarios → Sync) once, and it knows
|
|
492
492
|
which file holds which journey.
|
|
493
493
|
|
|
494
|
+
#### Results onto the flows you planned
|
|
495
|
+
|
|
496
|
+
When your flows are a plan, `docs/e2e-flows.csv` with an `id` column (imported in the console
|
|
497
|
+
under Scenarios → Import), name each test after its flow's id and its result lands on that
|
|
498
|
+
flow's card, from any runner:
|
|
499
|
+
|
|
500
|
+
| Runner | Test name |
|
|
501
|
+
|---|---|
|
|
502
|
+
| JUnit 5 | `void E2E_07_checkoutWithPromoCode()` |
|
|
503
|
+
| Cucumber | `Scenario: E2E-07 Checkout with a promo code` |
|
|
504
|
+
| taqwright / Playwright | `test('E2E-07 checkout with a promo code', …)` |
|
|
505
|
+
|
|
506
|
+
`_` counts as `-`, so a Java method can carry the id. Only ids the plan lists count: any other
|
|
507
|
+
id-like name reports under its own name, and `report` says which. An explicit
|
|
508
|
+
`taqwright-scenario` annotation still wins. A plan elsewhere, or ids written differently, go in
|
|
509
|
+
`lime.json` (`testCaseId` is a regex; its first group is the id when it has one):
|
|
510
|
+
|
|
511
|
+
```json
|
|
512
|
+
{ "testCasePlan": "qa/flows.csv", "testCaseId": "\\[(TC-\\d+)\\]" }
|
|
513
|
+
```
|
|
514
|
+
|
|
494
515
|
#### Which build was under test
|
|
495
516
|
|
|
496
517
|
`--app-version` is what lets LIME tell an intended UI change from a bug: a locator that
|