@beryl-so/cli 0.51.0 → 0.52.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/beryl-test-skill.js +11 -0
- package/dist/schema.generated.js +15 -0
- package/package.json +1 -1
package/dist/beryl-test-skill.js
CHANGED
|
@@ -365,6 +365,17 @@ ${JSON.stringify(BERYL_TEST_SKILL_EXAMPLE_PLAN, null, 2)
|
|
|
365
365
|
shows any, offer them once (\`tests_set_groups\`); no answer = leave it ungrouped and
|
|
366
366
|
move on. Never create a group yourself, that is the user's call.
|
|
367
367
|
|
|
368
|
+
### Testing a mobile or tablet viewport
|
|
369
|
+
A test runs at a desktop viewport unless you say otherwise. To cover a responsive layout,
|
|
370
|
+
set \`device\` on the plan: \`"mobile"\` or \`"tablet"\` (default \`"desktop"\`). This is
|
|
371
|
+
full Chromium device emulation, not a resize: the viewport, a mobile Chrome user-agent,
|
|
372
|
+
touch and the device pixel ratio all change together, so a hamburger or a nav that only
|
|
373
|
+
exists on small screens actually renders and is testable. \`mobile\` emulates a Pixel-class
|
|
374
|
+
phone, \`tablet\` a Galaxy-class tablet; both keep a Chrome user-agent so the emulated UA
|
|
375
|
+
matches the engine. Author the flow at that size over the Playwright MCP (resize the MCP
|
|
376
|
+
browser to match) so the refs you act on are the ones the small-screen layout renders. The
|
|
377
|
+
account, session and teardown rules are unchanged; \`device\` only sets the frame it runs in.
|
|
378
|
+
|
|
368
379
|
### The outcome assertion is the whole game
|
|
369
380
|
|
|
370
381
|
A flow is only worth banking if you can point at the **success signal** — the one
|
package/dist/schema.generated.js
CHANGED
|
@@ -36,6 +36,16 @@ export const ACTION_PLAN_SCHEMA = {
|
|
|
36
36
|
"title": "AuthMode",
|
|
37
37
|
"type": "string"
|
|
38
38
|
},
|
|
39
|
+
"DeviceClass": {
|
|
40
|
+
"description": "The viewport and device a test runs at. The AUTHOR sets it when a flow is specific\nto a form factor (a mobile-only nav, a hamburger, a stacked layout); omit it and the\ntest runs at the default desktop viewport.\n\n``mobile`` / ``tablet`` are full Chromium device emulation, not a bare resize: the\nviewport, a mobile Chrome user-agent, touch, and the device pixel ratio all change\ntogether, so a control gated behind a touch or mobile-UA media query actually appears.",
|
|
41
|
+
"enum": [
|
|
42
|
+
"desktop",
|
|
43
|
+
"tablet",
|
|
44
|
+
"mobile"
|
|
45
|
+
],
|
|
46
|
+
"title": "DeviceClass",
|
|
47
|
+
"type": "string"
|
|
48
|
+
},
|
|
39
49
|
"DialogChoice": {
|
|
40
50
|
"enum": [
|
|
41
51
|
"accept",
|
|
@@ -1344,6 +1354,11 @@ export const ACTION_PLAN_SCHEMA = {
|
|
|
1344
1354
|
"title": "Before",
|
|
1345
1355
|
"type": "array"
|
|
1346
1356
|
},
|
|
1357
|
+
"device": {
|
|
1358
|
+
"$ref": "#/$defs/DeviceClass",
|
|
1359
|
+
"default": "desktop",
|
|
1360
|
+
"description": "Viewport and device to run at. 'mobile' and 'tablet' apply full Chromium device emulation (viewport, mobile user-agent, touch, pixel ratio); 'desktop' (default) runs at the standard desktop viewport."
|
|
1361
|
+
},
|
|
1347
1362
|
"requires_auth": {
|
|
1348
1363
|
"default": false,
|
|
1349
1364
|
"title": "Requires Auth",
|
package/package.json
CHANGED