@immense/vue-pom-generator 1.0.90 → 1.0.92

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 (62) hide show
  1. package/README.md +88 -10
  2. package/RELEASE_NOTES.md +95 -62
  3. package/class-generation/base-page.ts +141 -59
  4. package/class-generation/diagnostics.ts +559 -0
  5. package/class-generation/index.ts +247 -128
  6. package/class-generation/playwright-types.ts +7 -11
  7. package/class-generation/pointer.ts +65 -18
  8. package/dist/class-generation/base-page.d.ts +19 -4
  9. package/dist/class-generation/base-page.d.ts.map +1 -1
  10. package/dist/class-generation/diagnostics.d.ts +110 -0
  11. package/dist/class-generation/diagnostics.d.ts.map +1 -0
  12. package/dist/class-generation/index.d.ts +4 -0
  13. package/dist/class-generation/index.d.ts.map +1 -1
  14. package/dist/class-generation/playwright-types.d.ts +3 -39
  15. package/dist/class-generation/playwright-types.d.ts.map +1 -1
  16. package/dist/class-generation/pointer.d.ts +10 -1
  17. package/dist/class-generation/pointer.d.ts.map +1 -1
  18. package/dist/eslint/index.cjs +52 -9
  19. package/dist/eslint/index.cjs.map +1 -1
  20. package/dist/eslint/index.d.ts +16 -7
  21. package/dist/eslint/index.d.ts.map +1 -1
  22. package/dist/eslint/index.mjs +52 -9
  23. package/dist/eslint/index.mjs.map +1 -1
  24. package/dist/index.cjs +728 -324
  25. package/dist/index.cjs.map +1 -1
  26. package/dist/index.mjs +728 -324
  27. package/dist/index.mjs.map +1 -1
  28. package/dist/manifest-generator.d.ts +10 -5
  29. package/dist/manifest-generator.d.ts.map +1 -1
  30. package/dist/method-generation.d.ts.map +1 -1
  31. package/dist/playwright/reporter.cjs +174 -0
  32. package/dist/playwright/reporter.cjs.map +1 -0
  33. package/dist/playwright/reporter.d.ts +13 -0
  34. package/dist/playwright/reporter.d.ts.map +1 -0
  35. package/dist/playwright/reporter.mjs +174 -0
  36. package/dist/playwright/reporter.mjs.map +1 -0
  37. package/dist/plugin/internal/build-plugin.d.ts +2 -0
  38. package/dist/plugin/internal/build-plugin.d.ts.map +1 -1
  39. package/dist/plugin/internal/dev-plugin.d.ts +2 -0
  40. package/dist/plugin/internal/dev-plugin.d.ts.map +1 -1
  41. package/dist/plugin/internal-plugins.d.ts.map +1 -1
  42. package/dist/route-navigation-codegen.d.ts +40 -0
  43. package/dist/route-navigation-codegen.d.ts.map +1 -0
  44. package/dist/router-bridge.d.ts +15 -0
  45. package/dist/router-bridge.d.ts.map +1 -1
  46. package/dist/router.cjs +41 -1
  47. package/dist/router.cjs.map +1 -1
  48. package/dist/router.mjs +41 -1
  49. package/dist/router.mjs.map +1 -1
  50. package/dist/tests/broad/helpers/fake-runtime.d.ts +27 -3
  51. package/dist/tests/broad/helpers/fake-runtime.d.ts.map +1 -1
  52. package/dist/tests/fixtures/generated-tsc/base-page.full.d.ts +16 -3
  53. package/dist/tests/fixtures/generated-tsc/base-page.full.d.ts.map +1 -1
  54. package/dist/tests/method-generation.test.d.ts +2 -0
  55. package/dist/tests/method-generation.test.d.ts.map +1 -0
  56. package/dist/tests/playwright-diagnostics.test.d.ts +2 -0
  57. package/dist/tests/playwright-diagnostics.test.d.ts.map +1 -0
  58. package/dist/tests/playwright-reporter.test.d.ts +2 -0
  59. package/dist/tests/playwright-reporter.test.d.ts.map +1 -0
  60. package/dist/transform.d.ts.map +1 -1
  61. package/dist/vite.config.d.ts.map +1 -1
  62. package/package.json +8 -1
package/README.md CHANGED
@@ -14,6 +14,7 @@ If you already use Playwright with `getByTestId`, the point is simple: this pack
14
14
  - **Generates TypeScript POM output as either one aggregate or split per class, always with a stable `index.ts` barrel.**
15
15
  - **Describes generated Playwright locators** with deterministic human-readable labels via `Locator.describe()`.
16
16
  - **Can generate Playwright fixtures** so tests can request `userListPage` instead of constructing `new UserListPage(page)` manually.
17
+ - **Captures generator-aware failure diagnostics before fixture teardown** and prints the relevant DOM, accessibility tree, browser errors, generated methods, and isolated rerun command to stdout.
17
18
  - **Can fail fast on unnameable wrapper-button actions** so complex inline handlers do not silently degrade into low-signal generated APIs.
18
19
  - **Can emit a single C# POM file** for Playwright .NET consumers.
19
20
  - **Exposes `virtual:testids` and `virtual:pom-manifest`** so your app can inspect collected ids and generated POM metadata at runtime.
@@ -23,7 +24,7 @@ If you already use Playwright with `getByTestId`, the point is simple: this pack
23
24
 
24
25
  - **It is not a runtime DOM crawler.** It only knows what it can learn from Vue SFC templates and router introspection.
25
26
  - **It does not fully understand arbitrary wrapper components automatically.** There is some wrapper inference for simple local SFCs and some naming conventions, but serious design-system components still need `injection.nativeWrappers`.
26
- - **It does not fully fill route params for you.** Generated `goTo()` / `goToSelf()` methods use the discovered route template literally. A route like `/users/:id` still needs a real `/users/123` when you actually navigate.
27
+ - **It cannot infer query-value types from arbitrary route-props code.** Generated `goTo()` accepts discovered query keys as optional `string | number` values; callers still choose and supply the values appropriate for their application.
27
28
  - **It does not auto-attach every file in `pom/custom`.** Custom helpers are imported, but they only affect generated classes when you explicitly configure attachments, or when they match the built-in `Toggle` / `Checkbox` widget conventions.
28
29
  - **It does not make override classes globally replace generated classes.** `pom/overrides` only changes generated fixture instantiation. Direct imports from the generated barrel still give you the generated class unless you import your override yourself.
29
30
  - **The C# emitter is not feature-parity with the TypeScript emitter.** It emits locator/action classes, but not Playwright fixtures, not helper attachments, and not the same route helper surface.
@@ -215,6 +216,7 @@ Exports:
215
216
  - `defineVuePomGeneratorConfig()`
216
217
  - `defineNuxtPomGeneratorConfig()`
217
218
  - `@immense/vue-pom-generator/eslint`
219
+ - `@immense/vue-pom-generator/playwright/reporter`
218
220
  - `@immense/vue-pom-generator/router` (browser-safe runtime bridge)
219
221
 
220
222
  ## Basic Vue/Vite setup
@@ -366,6 +368,7 @@ TypeScript output:
366
368
  Optional Playwright fixture output:
367
369
 
368
370
  - `fixtures.g.ts` next to the POMs by default
371
+ - `pom-manifest.g.ts` — a Node-importable map from Vue source/test ids to generated methods
369
372
  - or a custom directory / file path when configured
370
373
 
371
374
  Optional C# output:
@@ -374,6 +377,60 @@ Optional C# output:
374
377
 
375
378
  If you emit outside a `__generated__` path, the generator also manages `.gitattributes` entries for generated files.
376
379
 
380
+ ## Fast, loud Playwright failures
381
+
382
+ Generated fixtures install a failure capture around the browser page. On every unexpected failed attempt, before Playwright destroys the browser context, it captures within one five-second total budget:
383
+
384
+ - the URL and page title
385
+ - rendered generated test ids with visible/hidden and enabled/disabled state
386
+ - the best matching generated POM and its method catalog
387
+ - the most recent generated action and all test-id candidates it expected
388
+ - an accessibility snapshot
389
+ - buffered browser console errors, uncaught page errors, failed requests, and HTTP error responses
390
+ - a screenshot and structured JSON attachment
391
+
392
+ Add the reporter to print this as one bounded, LLM-friendly stdout block. In GitHub Actions, compose Playwright's built-in `github` reporter for canonical line annotations:
393
+
394
+ ```ts
395
+ import { defineConfig } from "@playwright/test";
396
+
397
+ export default defineConfig({
398
+ expect: { timeout: 5_000 },
399
+ reporter: process.env.CI
400
+ ? [
401
+ ["github"],
402
+ ["@immense/vue-pom-generator/playwright/reporter"],
403
+ ]
404
+ : [
405
+ ["list"],
406
+ ["@immense/vue-pom-generator/playwright/reporter"],
407
+ ],
408
+ use: {
409
+ actionTimeout: 5_000,
410
+ navigationTimeout: 5_000,
411
+ trace: "retain-on-first-failure",
412
+ },
413
+ });
414
+ ```
415
+
416
+ The report ends with a file-and-line-targeted command that includes `--max-failures=1`. Method availability is descriptive only: `absent`, `hidden`, or `disabled` can be a valid state for the current page.
417
+
418
+ Animations and presentation delays are disabled by default. Recording/demo projects can opt in through the generated `animation` fixture option; ordinary tests use Playwright's actionability checks without forced clicks. Before clicking, generated actions also await finite CSS animations on the target's ancestor chain (bounded by five seconds). This covers overlays that are visible to Playwright while their component library still suppresses input during an opening transition; infinite decorative animations are ignored.
419
+
420
+ ## Recommended Playwright lint rules
421
+
422
+ The ESLint export composes its generator-specific conventions with `eslint-plugin-playwright`. The flat recommended config treats manual sleeps, `networkidle`, selector waits, forced actions, and non-web-first assertions as errors:
423
+
424
+ ```ts
425
+ import { recommendedPlaywrightConfig } from "@immense/vue-pom-generator/eslint";
426
+
427
+ export default [
428
+ ...recommendedPlaywrightConfig,
429
+ ];
430
+ ```
431
+
432
+ It enables `playwright/no-wait-for-timeout`, `playwright/no-networkidle`, `playwright/no-wait-for-selector`, `playwright/no-force-option`, and `playwright/prefer-web-first-assertions` alongside the generated-POM rules. Presentation waits inside the generator's explicitly enabled animation runtime are not test-authored waits and remain isolated there.
433
+
377
434
  ## Actual Vite dev/build behavior
378
435
 
379
436
  This is important if you are deciding whether the tool will fit into a real codebase.
@@ -407,26 +464,47 @@ What is not fully supported:
407
464
 
408
465
  - arbitrary computed `:to` expressions
409
466
  - parameter-aware `goToSelf()` URL filling
410
- - exposing rich route-param metadata on the generated POM surface
467
+ - inferring query-value types from arbitrary route-props transformations
411
468
 
412
469
  ### 2) View-level `route`, `goTo()`, and `goToSelf()`
413
470
 
414
471
  When `generation.router` is enabled, each view POM gets:
415
472
 
416
473
  - `static readonly route: { template: string } | null`
417
- - `async goTo()`
474
+ - a typed `async goTo(...)` whose flat input includes discovered path params and optional query keys
418
475
  - `async goToSelf()`
419
476
 
477
+ For a route such as:
478
+
479
+ ```ts
480
+ {
481
+ path: "/users/:userId",
482
+ name: "user-details",
483
+ component: UserDetailsPage,
484
+ props: route => ({
485
+ userId: route.params.userId,
486
+ tab: route.query.tab,
487
+ }),
488
+ }
489
+ ```
490
+
491
+ the generated method is shaped like this:
492
+
493
+ ```ts
494
+ goTo(params: { userId: string | number; tab?: string | number }): Promise<void>
495
+ ```
496
+
497
+ `goTo({ userId: 42, tab: "activity" })` partitions the flat input into Vue Router's
498
+ `params` and `query` records. On a cold page it boots the application, waits for Vue
499
+ Router's initial navigation to settle, and then uses `router.push`; warm pages use the
500
+ same awaited push without booting again.
501
+
420
502
  Important caveats:
421
503
 
422
504
  - `goToSelf()` calls `page.goto(...)`, resolving the route template against `PLAYWRIGHT_RUNTIME_BASE_URL`, `PLAYWRIGHT_TEST_BASE_URL`, or `VITE_PLAYWRIGHT_BASE_URL` when those runtime env vars are present
423
- - a dynamic route template like `/users/:id` stays `/users/:id`
505
+ - unlike `goTo()`, a dynamic `goToSelf()` template like `/users/:id` stays `/users/:id`
424
506
  - if a component is matched by multiple routes, the generator currently picks one route template (the shortest one)
425
-
426
- So the safe rule is:
427
-
428
- - use generated `goTo()` for simple/static routes
429
- - for dynamic routes, navigate with a real URL yourself or wrap that behavior in your override/custom code
507
+ - when a component has both a paramless route and a route whose path params are all optional, pass at least one path-param key (it may be `undefined`) to select the parametrized route; a query-only object selects the paramless route
430
508
 
431
509
  ### Why `moduleShims` exists
432
510
 
@@ -1266,7 +1344,7 @@ If you are evaluating this package critically, the most accurate short version i
1266
1344
  - it is strongest when your team already wants `getByTestId`-style Playwright tests
1267
1345
  - it is strongest in TypeScript-first Playwright projects
1268
1346
  - it is strongest when your Vue component library is either native-heavy or can be described with `nativeWrappers`
1269
- - it is useful with router-aware pages, but you should treat dynamic-route `goTo()` support as partial and explicit
1347
+ - it is useful with router-aware pages, including typed path params and discovered query keys
1270
1348
  - it becomes much more maintainable when you pair it with the ESLint cleanup rule and a small `pom/custom` folder for the genuinely hard widgets
1271
1349
 
1272
1350
  If that matches your codebase, the package removes a surprising amount of repetitive test maintenance. If it does not, the caveats above are the important ones to believe.
package/RELEASE_NOTES.md CHANGED
@@ -1,86 +1,119 @@
1
- I'll investigate the repository to determine which PRs fall within the release window and gather
2
- details for accurate release notes.
1
+ I'll verify the actual merged PRs in the release window by querying the repository directly, and
2
+ check the git log between the tags.
3
3
 
4
- Let me examine the actual content of the key changes to understand what was introduced.
4
+ Let me check the v1.0.91 tag to understand the boundary, and verify the PR merge details.
5
5
 
6
- Now I have a complete picture. Let me verify the key breaking change — the router global key rename.
6
+ Let me retry those queries.
7
7
 
8
- I now have a complete understanding of all changes. Here are the release notes for v1.0.90:
8
+ Now I understand the picture. The v1.0.91 tag is at commit #53, so v1.0.92 contains only PR #54. Let
9
+ me examine the key changed files to write accurate release notes.
10
+
11
+ Let me check the diagnostics module and README changes to round out the picture.
12
+
13
+ I now have a complete picture. v1.0.91 was tagged at PR #53's commit, so v1.0.92 contains only PR
14
+ #54. Let me write the release notes.
9
15
 
10
16
  Highlights
11
17
 
12
- - New browser-safe router bridge — exposeRouterForPomNavigation() lets consumers expose the live
13
- Vue Router to generated POM goTo() methods via a dedicated @immense/vue-pom-generator/router entry
14
- point.
15
- - Per-component existingIdBehavior overrides — the option now accepts { default, components } to
16
- apply different test-ID collision policies on a per-SFC basis.
17
- - New no-data-testid-in-specs ESLint rule — bans raw data-testid selectors and getByTestId() calls
18
- in spec files, steering authors toward generated POM accessors.
19
- - Router global key namespaced — the internal globalThis key used by generated goTo() is renamed
20
- from __appRouter to __vuePomGeneratorRouter, backed by a shared constant in the new bridge module.
18
+ - Fast, actionable Playwright failure diagnostics — generated fixtures now capture the full failure
19
+ state (URL, rendered test IDs, accessibility snapshot, console errors, failed requests, HTTP
20
+ response bodies, active action, and POM method catalog) before the browser context is destroyed,
21
+ within a five-second budget.
22
+ - Bundled Playwright reporter — a new @immense/vue-pom-generator/playwright/reporter subpath prints
23
+ diagnostics as one bounded, LLM-friendly stdout block and emits a structured JSON attachment.
24
+ - Generated POM manifest — a new pom-manifest.g.ts artifact maps Vue source/test IDs to their
25
+ generated methods, consumable at runtime by the diagnostics layer.
26
+ - Composable recommended ESLint config — recommendedPlaywrightConfig composes generator-specific
27
+ rules with eslint-plugin-playwright, banning manual waits, networkidle, selector waits, forced
28
+ actions, and non-web-first assertions.
29
+ - Five-second action failure budget — generated actions now fail fast instead of waiting out
30
+ Playwright's default timeout, and redundant runtime waits have been removed.
31
+ - Finite-animation awareness — generated clicks await finite CSS animations on the target's
32
+ ancestor chain (bounded to five seconds); infinite decorative animations are ignored.
21
33
 
22
34
  Changes
23
35
 
24
- Router Bridge
25
-
26
- - Added router-bridge.ts with exposeRouterForPomNavigation(), POM_ROUTER_GLOBAL_NAME, and
27
- PomNavigationRouter / PomNavigationTarget interfaces.
28
- - Registered @immense/vue-pom-generator/router as a new package export in package.json and
29
- vite.config.ts.
30
- - Updated class-generation/index.ts to import and use the shared POM_ROUTER_GLOBAL_NAME constant
31
- instead of a local magic string.
32
- - Broadened the bridge's push/resolve callable constraints to accept Vue Router's overloads.
33
- - Documented the router bridge usage in README.md.
34
-
35
- Existing ID Behavior
36
-
37
- - Added ExistingIdBehaviorByComponent interface and ExistingIdBehaviorConfig type
38
- (ExistingIdBehavior | ExistingIdBehaviorByComponent).
39
- - Exported ExistingIdBehaviorByComponent and ExistingIdBehaviorConfig from the main entry point.
40
- - Added resolveExistingIdBehavior(config, componentName) to plugin/vue-plugin.ts and wired it into
41
- both build and dev plugin processors.
42
- - Widened existingIdBehavior option type to ExistingIdBehaviorConfig across
43
- resolved-generation-options.ts, resolved-injection-options.ts, and vue-plugin.ts.
44
- - Corrected the JSDoc default annotation from "preserve" to "error" (the code default was already
45
- "error").
36
+ Diagnostics & Reporting
37
+
38
+ - Added class-generation/diagnostics.ts — installs a failure-capture wrapper around the browser
39
+ page that gathers URL/title, rendered test IDs with visible/enabled state, the best-matching POM and
40
+ its method catalog, the most recent generated action and expected test-id candidates, an
41
+ accessibility snapshot, buffered console/page errors, failed requests, bounded HTTP failure bodies,
42
+ a screenshot, and a JSON attachment.
43
+ - Added playwright/reporter.ts — a Playwright reporter that reads the diagnostics attachment and
44
+ prints a single bounded stdout block; ends with a file-and-line-targeted rerun command including
45
+ --max-failures=1.
46
+ - Exported a new package subpath @immense/vue-pom-generator/playwright/reporter.
47
+ - Method availability is reported descriptively (absent, hidden, disabled) rather than as errors,
48
+ so conditional UI states remain obvious without false failures.
49
+
50
+ POM Manifest
51
+
52
+ - Added pom-manifest.g.ts — a Node-importable map from Vue source/test IDs to generated methods,
53
+ consumed by the diagnostics layer to report method availability.
54
+ - Introduced manifest types (PomManifest, PomManifestComponent, PomManifestMethod,
55
+ PomManifestEntry) in the diagnostics module.
56
+ - Updated manifest-generator.ts to emit the new manifest artifact alongside existing POM output.
46
57
 
47
58
  ESLint
48
59
 
49
- - Added no-data-testid-in-specs rule that flags data-testid in string literals, template literals,
50
- and getByTestId() calls (including computed member access).
51
- - Exported the rule from @immense/vue-pom-generator/eslint.
60
+ - Added recommendedPlaywrightConfig — a composable flat config that merges
61
+ eslint-plugin-playwright's recommended rules with the generator's own rules.
62
+ - Enabled playwright/no-wait-for-timeout, playwright/no-networkidle,
63
+ playwright/no-wait-for-selector, playwright/no-force-option, and
64
+ playwright/prefer-web-first-assertions as errors.
65
+ - Banned low-level POM action helpers (clickByTestId, clickLocator) via the no-raw-locator-action
66
+ rule.
67
+ - Added scrollIntoViewIfNeeded to the recognized locator-action set.
68
+ - Restructured the plugin export to include a configs record alongside rules.
69
+ - Added eslint-plugin-playwright (^2.11.0) as a runtime dependency.
70
+
71
+ Action & Animation Behavior
52
72
 
53
- Tests
73
+ - Generated actions now fail within a five-second total budget; redundant runtime waits removed.
74
+ - Generated clicks await finite CSS animations on the target's ancestor chain before proceeding,
75
+ bounded to five seconds; infinite decorative animations are ignored.
76
+ - Animations and presentation delays are disabled by default; recording/demo projects opt in via
77
+ the generated animation fixture option.
54
78
 
55
- - Added tests/router-bridge.test.ts covering exposeRouterForPomNavigation().
56
- - Added tests/existing-id-behavior.test.ts covering resolveExistingIdBehavior with scalar and
57
- per-component configs.
58
- - Extended tests/existing-id-error.test.ts with a per-component override scenario.
59
- - Extended tests/eslint.test.ts with no-data-testid-in-specs valid/invalid cases.
60
- - Updated tests/class-generation-coverage.test.ts to reference the renamed __vuePomGeneratorRouter
61
- key.
79
+ Codegen & Navigation
80
+
81
+ - Centralized router navigation emission in route-navigation-codegen.ts; cold pages now boot the
82
+ application, wait for Vue Router's initial navigation to settle, then use router.push, while warm
83
+ pages use the same awaited push without re-booting.
84
+ - Tightened fragment, wrapper, radio, checkbox, pointer, and transitive-POM codegen behavior
85
+ uncovered by consumer testing.
86
+ - Updated class-generation/base-page.ts, class-generation/index.ts, class-generation/pointer.ts,
87
+ class-generation/playwright-types.ts, method-generation.ts, transform.ts, and router-bridge.ts to
88
+ support the above.
89
+
90
+ Plugin & Build
91
+
92
+ - Updated plugin/internal-plugins.ts, plugin/internal/build-plugin.ts, and
93
+ plugin/internal/dev-plugin.ts for manifest and reporter integration.
94
+ - Updated vite.config.ts and scripts/packed-smoke-check.mjs accordingly.
95
+
96
+ Documentation
97
+
98
+ - Expanded README.md with sections on fast Playwright failures, the bundled reporter, the POM
99
+ manifest, recommended lint rules, and animation handling.
62
100
 
63
101
  Breaking Changes
64
102
 
65
- - Router global key renamed: generated goTo() methods now read the live router from
66
- globalThis.__vuePomGeneratorRouter instead of globalThis.__appRouter. Consumers who manually set
67
- globalThis.__appRouter = router should switch to exposeRouterForPomNavigation(router) from
68
- @immense/vue-pom-generator/router.
69
- - existingIdBehavior type widened: the option type is now ExistingIdBehaviorConfig
70
- (ExistingIdBehavior | ExistingIdBehaviorByComponent). Existing string values remain valid; code that
71
- narrowed the option to ExistingIdBehavior may need a type update.
103
+ - New peer dependency — @playwright/test (>=1.61.0 <2) is now a required peer dependency.
104
+ - Five-second action budget — generated actions fail within five seconds instead of relying on
105
+ Playwright's default timeout; tests depending on longer timeouts will fail sooner.
106
+ - Animations disabled by default — presentation delays are off unless explicitly opted in via the
107
+ generated animation fixture option.
72
108
 
73
109
  Pull Requests Included
74
110
 
75
- No pull requests were merged in this release window. All changes were committed directly:
76
-
77
- - a2f3c67 feat: add POM consumer integration APIs
78
- - be7b0be fix: isolate browser router bridge
79
- - c3ca37a fix: accept Vue Router in bridge
111
+ - ]8;id=md-1fivfqz;https://github.com/immense/vue-pom-generator/pull/54#54 — Add fast, actionable Playwright diagnostics]8;;]8;; (@dkattan)]8;;
80
112
 
81
113
  Testing
82
114
 
83
- New unit tests cover the router bridge, resolveExistingIdBehavior (scalar and per-component), and
84
- the no-data-testid-in-specs ESLint rule. Existing class-generation coverage tests were updated for
85
- the router key rename.
115
+ Validated per the PR: npm test (401 passed), npm run typecheck, npm run lint, npm run smoke:pack,
116
+ and a full Immy Aspire-backed Playwright suite with --max-failures=1 (passed in 4m37s). New test
117
+ suites added for diagnostics (tests/playwright-diagnostics.test.ts) and the reporter
118
+ (tests/playwright-reporter.test.ts), plus tests/method-generation.test.ts.
86
119