You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
defaults.add(Pair.from(AgentCLIPromptText, "As a test agent verify that you can log in with the credentials john/demo. Then the Welcome John Smith message is shown."));
Copy file name to clipboardExpand all lines: docs/webstudio/WEBSTUDIO_FUNCTIONAL_SPEC.md
+22-4Lines changed: 22 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,9 +81,9 @@ The `Edit test.settings file` view is treated as one logical editing area for un
81
81
-`Edit Settings` renders the content of the `test.settings` file into a visual grouped form of settings.
82
82
The `Edit Settings` view is treated as one logical editing area for unsaved-change behavior.
83
83
84
-
### State Observation Mode
84
+
### CLI State Projection Mode
85
85
86
-
`StateObservationMode` controls how a captured TESTAR state is projected for consumers. Currently, it is applied to CLI/agent state output.
86
+
`CliStateProjectionMode` controls how a captured TESTAR state is projected for CLI/agent consumers.
87
87
88
88
The setting must not redefine the canonical captured state used by TESTAR internals.
89
89
@@ -103,9 +103,9 @@ The distinction between interactive and actionable is intentional:
103
103
- interactive means the widget has an interaction capability
104
104
- actionable means the widget is interactive and also passes enabled, non-blocked, visible, widget-filter, and top-level policies
105
105
106
-
The default value is `FULL_STATE`.
106
+
The default value is `INTERACTIVE_SEMANTIC_WIDGETS`.
107
107
108
-
The `Edit Settings` view must render `StateObservationMode` as a dropdown using the available enum values.
108
+
The `Edit Settings` view must render `CliStateProjectionMode` as a dropdown using the available enum values.
109
109
110
110
## Navigation Rules
111
111
@@ -335,12 +335,30 @@ CLI Mode supports:
335
335
- agent CLI execution start
336
336
- CLI command execution
337
337
- CLI session stop
338
+
- focused editing of Agent CLI settings stored in the selected workspace `test.settings`
338
339
339
340
Workspace selection:
340
341
341
342
- WebStudio uses the shared workspace list for CLI mode with other testar modes
342
343
- WebStudio sends the selected workspace to CLI startup
343
344
- CLI validates connector values server-side and reports startup errors to the user
345
+
- Manual and Agent CLI execution use the selected workspace settings, including `CliStateProjectionMode` and `AgentCLI...` values
346
+
347
+
### Agent CLI Settings
348
+
349
+
Agent CLI settings are stored in the selected workspace `test.settings` file with `AgentCLI...` names.
350
+
351
+
The `Edit Settings` view must expose these settings in an `Agent CLI` group.
352
+
353
+
The CLI mode view may also expose a focused `Agent CLI Settings` panel for the same settings.
354
+
355
+
If users edit Agent CLI settings in CLI mode and then leave CLI mode, change workspace, or start Manual/Agent CLI execution, WebStudio must show an unsaved settings dialog.
356
+
357
+
Dialog actions:
358
+
359
+
-`Save`: persist Agent CLI settings to the selected workspace `test.settings`, then continue the pending action
360
+
-`Discard`: restore the last persisted Agent CLI settings in the CLI panel, then continue the pending action
361
+
-`Cancel`: keep the user in CLI mode and abort the pending action
0 commit comments