@seldonqa/cli 0.12.0 → 0.13.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.
Files changed (2) hide show
  1. package/README.md +5 -5
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -118,9 +118,7 @@ If your account has too many tunnels open at once you'll get `Tunnel limit reach
118
118
 
119
119
  **One local target, one run at a time.** Runs against the same local URL in the same workspace share a single tunnel. That includes two terminals, a terminal and a CI job, or two teammates. Whichever run finishes first closes the tunnel, and the other run loses access to your app. Until this is fixed, run them one after another.
120
120
 
121
- ## Usability studies (preview)
122
-
123
- > Preview: running a study needs a Seldon backend with usability runs enabled. Authoring and `validate` work offline today.
121
+ ## Usability studies
124
122
 
125
123
  Alongside QA, a project can keep **usability studies** as code: personas from your workspace attempt a goal on your app, and you get back a summary of where they struggled. Each study is one committed `<name>.usability.yml` file at the project root, next to `seldon.yml`. Every key is required except `version` and `credentials`:
126
124
 
@@ -153,6 +151,7 @@ seldon init --type usability trial-signup --dir studies # …or into another d
153
151
  seldon validate --file trial-signup.usability.yml
154
152
  seldon run --file trial-signup.usability.yml # waits, then prints a short report (--md / --full / --json)
155
153
  seldon report # re-show the last run's report
154
+ seldon personas # the persona names your workspace has (--limit / --offset to page)
156
155
  ```
157
156
 
158
157
  - **Which kind of file?** A file named `*.usability.yml` is always a usability study, so a study with a YAML error or a misspelled key gets usability errors rather than QA ones. Otherwise the CLI decides from the content: a top-level `experiment:` block is a usability study, `testCases:` is a QA suite. Pass `--type usability` (or `--type qa`) to `run` / `validate` to make that explicit; a contradicting `--type` is an error.
@@ -193,17 +192,18 @@ seldon report # re-show the last run's r
193
192
  | Command | What it does |
194
193
  | --- | --- |
195
194
  | `seldon init` | Scaffold a template `seldon.yml` |
196
- | `seldon init --type usability [name] [--dir <dir>]` | Scaffold a `<name>.usability.yml` study (preview) |
195
+ | `seldon init --type usability [name] [--dir <dir>]` | Scaffold a `<name>.usability.yml` study |
197
196
  | `seldon cases add` | Append a test case (`--name` `--step …` `--criteria`) |
198
197
  | `seldon cases` | List the cases in the current `seldon.yml` |
199
198
  | `seldon validate [--file <file>] [--type qa\|usability]` | Validate `seldon.yml` (or any QA suite / usability study) locally |
200
- | `seldon run --file <name>.usability.yml` | Run a usability study and print a short report with a link to the app (preview) |
199
+ | `seldon run --file <name>.usability.yml` | Run a usability study and print a short report with a link to the app |
201
200
  | `seldon run [--url <url>]` | Ingest `seldon.yml` and run it; a local `--url` is auto-exposed via a Cloudflare tunnel (`--auto-approve` to skip the prompt); `--no-wait` to detach, `--fail-on` to gate, `--label <tag>` to profile |
202
201
  | `seldon report [--md \| --json] [--full]` | Show the report for the last run (or `--id <run>`); for a usability run, a short report with a link to the app (`--md` / `--full` for the Markdown summary) |
203
202
  | `seldon logs --follow` | Stream the agent's live reasoning |
204
203
  | `seldon runs` | List QA runs with color-coded status |
205
204
  | `seldon cancel --id <run>` | Stop a run mid-flight |
206
205
  | `seldon list` | List baselines your key can see |
206
+ | `seldon personas [--limit <n>] [--offset <n>]` | List the personas your key can see (name and description, 10 at a time), for a study's `personas:` list |
207
207
  | `seldon config` · `login` | Manage credentials and settings |
208
208
  | `seldon api <operation>` | Call any Blok API operation directly |
209
209
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@seldonqa/cli",
3
- "version": "0.12.0",
3
+ "version": "0.13.0",
4
4
  "description": "Seldon QA - generate a QA test plan from any codebase and run AI agents against your live app, from your terminal or CI.",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -32,11 +32,11 @@
32
32
  "commander": "^12.1.0"
33
33
  },
34
34
  "optionalDependencies": {
35
- "@seldonqa/cli-darwin-x64": "0.12.0",
36
- "@seldonqa/cli-darwin-arm64": "0.12.0",
37
- "@seldonqa/cli-linux-arm64": "0.12.0",
38
- "@seldonqa/cli-win32-x64": "0.12.0",
39
- "@seldonqa/cli-linux-x64": "0.12.0"
35
+ "@seldonqa/cli-darwin-arm64": "0.13.0",
36
+ "@seldonqa/cli-darwin-x64": "0.13.0",
37
+ "@seldonqa/cli-win32-x64": "0.13.0",
38
+ "@seldonqa/cli-linux-x64": "0.13.0",
39
+ "@seldonqa/cli-linux-arm64": "0.13.0"
40
40
  },
41
41
  "devDependencies": {
42
42
  "@types/node": "^20.14.0",