@piwitests/reporter 0.20.0 → 0.22.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 CHANGED
@@ -10,6 +10,18 @@ A custom Playwright reporter that sends test results to a [Piwi Dashboard](https
10
10
  npm install --save-dev @piwitests/reporter
11
11
  ```
12
12
 
13
+ ## Set up in one command
14
+
15
+ From your Playwright project, `npx @piwitests/reporter init` installs the reporter, wraps your `playwright.config`, creates the capture-fixtures file, and records the connection in `.env.example`:
16
+
17
+ ```bash
18
+ npx @piwitests/reporter init --server-url http://localhost:3000 --project my-project
19
+ ```
20
+
21
+ Every step is idempotent (safe to re-run); a config shape it will not rewrite is reported as `manual` with the exact change to make, never mangled. Add `--dry-run` to preview or `--json` for a machine-readable plan an agent can act on. It also installs the [Piwi agent skills](https://piwitests.github.io/mcp#agent-skills) so your coding agent can investigate failures, heal locators, and stabilize flaky tests. Run `npx @piwitests/reporter init --help` for all options, or wire it up by hand with the steps below.
22
+
23
+ > The package is `@piwitests/reporter`; its command is `piwi`. Invoke it through the package name (`npx @piwitests/reporter <command>`) so npx resolves this package — `npx piwi` would fetch an unrelated `piwi` from npm. Once the reporter is a project dependency, `npx piwi <command>` resolves the local binary and works too.
24
+
13
25
  ## Quick start
14
26
 
15
27
  `wrapConfig` is the recommended setup. It injects the reporter **and** a global