@piwitests/reporter 0.67.0 → 0.69.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/dist/cli/index.js +1903 -640
- package/dist/global-setup-module.js +458 -135
- package/dist/index.d.ts +39 -4
- package/dist/index.js +10174 -4441
- package/dist/internal/capture/attachments.d.ts +1 -0
- package/dist/internal/capture/attachments.js +2 -1
- package/dist/internal/capture/capture-fixtures.d.ts +176 -21
- package/dist/internal/capture/capture-fixtures.js +6932 -2926
- package/package.json +1 -1
- package/templates/skills/fix-a-reported-bug/SKILL.md +3 -1
- package/templates/skills/investigate-failure/SKILL.md +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@piwitests/reporter",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.69.0",
|
|
4
4
|
"description": "Playwright reporter that streams results, traces and HTML reports to a Piwi Dashboard instance",
|
|
5
5
|
"url": "https://github.com/PiwiTests/piwi",
|
|
6
6
|
"homepage": "https://piwitests.dev",
|
|
@@ -36,7 +36,9 @@ Without it, the CLI does the same: `npx @piwitests/reporter bug <id>`, with the
|
|
|
36
36
|
4. **Fix the bug** in the application code. Keep the change to what the evidence and the expected result point at.
|
|
37
37
|
|
|
38
38
|
5. **Prove the fix.** Remove the `test.fail()` line from the bug's spec and run it: it must pass. Run the tests that
|
|
39
|
-
visit the page too (`npx playwright test <their files>`), so the fix breaks nothing around it.
|
|
39
|
+
visit the page too (`npx playwright test <their files>`), so the fix breaks nothing around it. With Piwi's run tools
|
|
40
|
+
connected (`npx @piwitests/reporter mcp`), start each with `run_start` instead: a test that fails waits at its line
|
|
41
|
+
for you to read its page (`run_follow`, `page_snapshot`).
|
|
40
42
|
|
|
41
43
|
6. **Report.** The cause, the fix, the spec file, and the two runs. Once the spec passes without `test.fail()` in a
|
|
42
44
|
run on the project's default branch (not a `piwi bug` run), Piwi closes the report on its own; before that, such a
|
|
@@ -25,7 +25,7 @@ Prefer the **Piwi MCP server** if it is connected to this agent (tools named `li
|
|
|
25
25
|
|
|
26
26
|
6. **Propose the fix.** Make the smallest change that addresses the root cause, in the actual source or spec files. Prefer Piwi's own suggestions where they exist — for a broken selector, the ranked replacement from `get_locator_healing` (the `apply-locator-healing` skill does exactly this). Show the diff.
|
|
27
27
|
|
|
28
|
-
7. **Verify.** Re-run the affected spec(s): `npx playwright test <file>`. Confirm they pass and the new run is green in the dashboard (`get_run_insights` compares the run with its baseline, usually the last passing run: regressions cleared, nothing new broken).
|
|
28
|
+
7. **Verify.** Re-run the affected spec(s). With Piwi's run tools connected (`npx @piwitests/reporter mcp`: `run_start`, `run_follow`, `page_snapshot`, …), start it with `run_start` (`file`, and `line` for one test): it runs where the developer sees it, and a test that still fails waits at its line for you to read its page (`run_follow`, then `page_snapshot`). Otherwise run `npx playwright test <file>`. Confirm they pass and the new run is green in the dashboard (`get_run_insights` compares the run with its baseline, usually the last passing run: regressions cleared, nothing new broken).
|
|
29
29
|
|
|
30
30
|
8. **Report back.** Piwi learns from what you tell it, so end every investigation with these calls (each is logged with your API key; `record_diagnosis` and `report_fix_attempt` need the Maintainer role or above on the project, rating a diagnosis needs read access only):
|
|
31
31
|
- **Your diagnosis.** If the cluster had no diagnosis, or yours differs, record it with `record_diagnosis` (`clusterId`, or `executionId` for a failure in no cluster or with a cause of its own): the model you run on and the diagnosis in the schema the tool describes (summary, confidenceScore, severity, ranked hypotheses with their evidence, suggestedFix with the unified-diff `patch`). Piwi validates the patch against the source that failed and shows the diagnosis as written by an agent.
|