Use Case testing matrix
Runs + Chat preview — the main verification method; a real channel and Operator Panel are optional.
Tools:
- How to test a scenario — Runs, Chat preview, log/trace
- Node Inspector → “Test action” — isolated Action test
- Fast Line Pro → Testing — agent without the scenario
- Channel on the instance (Telegram / widget) — when preview is not enough
- Operator Line — optional E2E after connect
- Custom Data UI — view the record (where applicable)
Basic level
| Use Case | Runs (required) | Channel (optional) | CD UI | What to check |
|---|---|---|---|---|
| Use Case 1 FAQ + AI | ✓ | TG/widget | — | {{ai_answer}}, fallback |
| Use Case 2 Menu | ✓ | — | — | Each button → its own branch; default |
| Use Case 3 Connect | ✓ | E2E | — | Edges success/limit/error; text after limit; chat_closed_alias; skill group |
| Use Case 4 Mock CRM | ✓ | — | — | crm_data; not_ok with a broken URL |
| Use Case 5 Action Jail | ✓ | 1 channel | — | +380 / 380 / 0…; error edge |
| Use Case 6 Registered Users | ✓ | across sessions | — | New Run → __get success |
| Use Case 7 Custom Data | ✓ | — | ✓ | ID in constants |
| Use Case 7b CSAT/NPS | ✓ | — | ✓ | Free-text ≠ INTEGER success; alias audit |
| Use Case 8 Macro section | ✓ | — | — | Section trace; OP button — optional |
| Use Case 9 Audit / RE | ✓ | optional | — | RE lab; tooling tour (Runs + trace + test action) |
Advanced + capstone
| Use Case | Runs (required) | Channel (optional) | CD UI | What to check |
|---|---|---|---|---|
| Use Case 10 Ticket | ✓ | — | — | ticket_id; categorizer; error edge |
| Use Case 11 Broadcast | ✓ alias | TG E2E | — | Delivery; subscribe vs one-off |
| Use Case 13 Capstone | ✓ | recommended | ✓ | 3 branches; self-check |
Optional
| Use Case | Runs | Channel | What to check |
|---|---|---|---|
| Priority segment (optional) | ✓ | — | Different subject_alias by segment |
| AI catalog (optional) | ✓ | — | 5 control queries |
| SLA alias (optional) | ✓ | — | Alias entry exists |
| Use Case 12 Copilot | ✓ | — | Copilot overview |
When preview is enough, and when you need a channel
| Situation | Preview | Channel |
|---|---|---|
| Node logic, edges, variables | Yes | No |
| Registered Users across visits | New Run | TG is more reliable |
| Connect to an operator | Up to connect in Runs | E2E — optional |
| Broadcast with a button | Alias + keyboard | TG for delivery |
| Macro | Section trace | OP — optional |
Note: checking in Operator Line is a recommendation, not a required pass condition. See when it is not the scenario.
Record in the result template
For each Use Case note: Runs · channel (if used) · CD UI (if applicable).