form-tester 0.10.0 → 0.10.1

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 (3) hide show
  1. package/.github/copilot-instructions.md +76 -67
  2. package/form-tester.js +1 -1
  3. package/package.json +1 -1
package/.github/copilot-instructions.md CHANGED
@@ -10,96 +10,105 @@ npm install -g form-tester
10
10
  form-tester install
11
11
  ```
12
12
 
13
- ## Running the CLI
13
+ ## Running a test
14
14
 
15
+ When the user gives you a form URL to test, execute ALL steps below in sequence WITHOUT stopping to ask. Do not ask "want me to continue?" — just do the entire flow.
16
+
17
+ ### Step 1 — Start the test
15
18
  ```bash
16
- # AI mode (default) — no prompts:
17
19
  form-tester test <url> --auto
20
+ ```
21
+ Or with options:
22
+ ```bash
18
23
  form-tester test <url> --auto --pnr 12345 --persona ung-mann --scenario "test validation"
19
-
20
- # Human mode — user chooses persona and scenario:
21
- form-tester test <url> --human # lists personas
22
- form-tester test <url> --human --persona ung-mann --scenario "test X" # run with choices
23
-
24
- # Full interactive CLI:
25
- form-tester
26
24
  ```
27
25
 
28
- Persona IDs: `ung-mann`, `gravid-kvinne`, `eldre-kvinne`, `kronisk-syk-mann`. Defaults to "noen" if omitted.
29
-
30
- When the user asks for `--human` mode:
31
- 1. Run `form-tester test <url> --human` to get persona list.
32
- 2. Ask the user to pick a persona and scenario.
33
- 3. Re-run: `form-tester test <url> --human --persona <id> --scenario "<text>"` (use `""` for standard test).
34
- Otherwise default to `--auto`.
35
-
36
- ## Commands
37
-
38
- | Command | Description |
39
- |---------|-------------|
40
- | `/setup` | Initial setup |
41
- | `/update` | Update Playwright CLI + skills |
42
- | `/version` | Show version |
43
- | `/people` | Rescan visible person list |
44
- | `/test {url}` | Test a form URL |
45
- | `/save {label}` | Save snapshot + screenshot |
46
- | `/clear` | Clear session |
47
- | `/quit` | Exit CLI |
48
-
49
- ## Playwright CLI (use via form-tester exec)
26
+ ### Step 2 — Dismiss cookies
27
+ ```bash
28
+ form-tester cookies
29
+ ```
50
30
 
51
- IMPORTANT: Always use `form-tester exec` instead of `playwright-cli` directly. This records all commands for replay.
31
+ ### Step 3 — Select person
32
+ ```bash
33
+ form-tester select-person
34
+ ```
35
+ To select a specific person: `form-tester select-person "Name"`
52
36
 
37
+ ### Step 4 — Study the form
38
+ Take a snapshot and identify ALL sections and required fields:
53
39
  ```bash
54
- form-tester exec open https://example.com
55
40
  form-tester exec snapshot
56
- form-tester exec fill e1 "value"
57
- form-tester exec click e3
58
- form-tester exec screenshot --filename=page.png --full-page
59
- form-tester exec close # finalizes recording
60
41
  ```
42
+ Look for collapsed/accordion sections (buttons with arrow icons). Expand ALL of them by clicking their header buttons before filling anything.
61
43
 
62
- Replay a previous run:
44
+ ### Step 5 — Fill the form
45
+ Use `form-tester exec` for ALL commands (this records them for replay):
63
46
  ```bash
64
- form-tester replay output/form-id/timestamp/recording.json
47
+ form-tester exec fill <ref> "value"
48
+ form-tester exec click <ref>
49
+ form-tester exec select <ref> "option text"
50
+ form-tester exec screenshot --filename "path.png" --full-page
65
51
  ```
66
52
 
67
- ## Test Flow
53
+ For autosuggest/search fields: fill the text, wait for dropdown, then click the suggestion:
54
+ ```bash
55
+ form-tester exec fill <ref> "search text"
56
+ form-tester exec snapshot # find the suggestion element
57
+ form-tester exec click <suggestion-ref>
58
+ ```
68
59
 
69
- When `/test` is triggered:
60
+ ### Step 6 — Submit
61
+ Take a screenshot, then click the submit button.
70
62
 
71
- 1. Prompt for PNR if not in URL. Wait for response.
72
- 2. Prompt for persona (numbered selection). Wait for response.
73
- 3. Prompt for test scenario in a separate message. Wait for response.
74
- 4. Only after all prompts answered: open browser, fill form, submit, verify.
63
+ ### Step 7 — Handle validation errors
64
+ IMPORTANT: If validation errors appear after submit, the form DID NOT SUBMIT. Run:
65
+ ```bash
66
+ form-tester validate
67
+ ```
68
+ This parses all validation errors, clicks each error link to scroll to the field, and shows what needs to be filled. Fix each field, then run `form-tester validate` again to confirm. Only then resubmit.
75
69
 
76
- ## Important Notes
70
+ RULES:
71
+ - Maximum 3 submit attempts. After 3, STOP and write results.
72
+ - Do NOT re-fill fields that are already filled.
73
+ - Do NOT use JavaScript `dispatchEvent` or `element.evaluate()` to set values.
74
+ - Always use Playwright's `fill`, `click`, `select` commands.
77
75
 
78
- - Provide a full /skjemautfyller URL. If `pnr` is missing, the CLI will prompt.
79
- - All screenshots MUST use `--full-page` to capture the entire page.
80
- - Take a full-page screenshot EVERY TIME the page changes: after clicking action buttons (Neste, Forrige, Send inn), after step/page transitions, after validation errors, after modals, and after submission.
81
- - Use `/save {label}` to capture additional snapshots into the output folder.
82
- - If an error modal appears on submit, open DevTools -> Network, retry once, and capture the Correlation ID header.
76
+ ### Step 8 — Post-submit verification
77
+ After successful submission, read the modal text:
78
+ - If it mentions Dokumenter storage ("lagret i Dokumenter") → run document verification
79
+ - If it does NOT mention Dokumenter → skip, note in test_results.txt
83
80
 
84
- ## Post-Submit Verification
81
+ ### Step 9 — Document verification
82
+ ```bash
83
+ form-tester documents
84
+ ```
85
+ This handles everything: navigate to Dokumenter, find latest doc, detect PDF vs HTML, download or screenshot.
85
86
 
86
- After submission, read the modal text:
87
- - If it mentions Dokumenter storage -> navigate to `/dokumenter?pnr={PNR}`, verify the document appears.
88
- - If it does NOT mention Dokumenter -> skip verification, note in test_results.txt.
87
+ ### Step 10 — Finalize
88
+ - Write test_results.txt with status, data used, and notes
89
+ - Close browser: `form-tester exec close`
89
90
 
90
- Document capture — detect format via `form-tester exec snapshot`:
91
+ ## Issue logging
91
92
 
92
- **PDF documents** (link with href containing `/pdf/`, or screenshot times out):
93
- Do NOT screenshot PDFs. Do NOT use `require('fs')` in run-code (it doesn't exist there).
94
- Download using Playwright's download event:
95
- ```
96
- form-tester exec run-code "async page => { const link = page.locator('a[href*=\"/pdf/\"]').first(); const [download] = await Promise.all([ page.waitForEvent('download'), link.click() ]); await download.saveAs('$OUTPUT_DIR/document.pdf'); }"
97
- ```
98
- Or if there's a "Last ned" button:
99
- ```
100
- form-tester exec run-code "async page => { const [download] = await Promise.all([ page.waitForEvent('download'), page.getByRole('link', { name: 'Last ned' }).click() ]); await download.saveAs('$OUTPUT_DIR/document.pdf'); }"
93
+ When something unexpected happens, log it:
94
+ ```bash
95
+ form-tester issue <category> "<description>"
101
96
  ```
97
+ Categories: `person-selection`, `navigation`, `form-fill`, `submission`, `documents`, `pdf-download`, `html-capture`, `screenshot`, `snapshot`, `validation`, `modal`, `timeout`, `other`
98
+
99
+ View recent issues: `form-tester issues`
100
+
101
+ ## Important rules
102
+
103
+ - ALWAYS use `form-tester exec` instead of `playwright-cli` directly
104
+ - ALL screenshots MUST use `--full-page`
105
+ - Take a screenshot EVERY TIME the page changes
106
+ - Do NOT stop to ask the user between steps — execute the full flow
107
+ - Persona IDs: `ung-mann`, `gravid-kvinne`, `eldre-kvinne`, `kronisk-syk-mann`, `noen`
102
108
 
103
- **HTML documents**: `form-tester exec screenshot --filename "..." --full-page`. Also save raw HTML.
109
+ ## Human mode
104
110
 
105
- **XML/other**: note the type in test_results.txt and skip capture.
111
+ When user asks for `--human` mode:
112
+ 1. Run `form-tester test <url> --human` to get persona list
113
+ 2. Ask user to pick persona and scenario
114
+ 3. Re-run: `form-tester test <url> --human --persona <id> --scenario "<text>"`
package/form-tester.js CHANGED
@@ -7,7 +7,7 @@ const { spawn, execSync } = require("child_process");
7
7
  const CONFIG_PATH = path.join(process.cwd(), "form-tester.config.json");
8
8
  const OUTPUT_BASE = path.resolve(process.cwd(), "output");
9
9
  const ISSUES_PATH = path.join(OUTPUT_BASE, "issues.jsonl");
10
- const LOCAL_VERSION = "0.10.0";
10
+ const LOCAL_VERSION = "0.10.1";
11
11
  const RECOMMENDED_PERSON = "Uromantisk Direktør";
12
12
 
13
13
  // Recording — persisted to disk so `form-tester exec` can append across processes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "form-tester",
3
- "version": "0.10.0",
3
+ "version": "0.10.1",
4
4
  "description": "AI-powered form testing skill for /skjemautfyller forms using Playwright CLI. Works with Claude Code and GitHub Copilot.",
5
5
  "main": "form-tester.js",
6
6
  "bin": {