Feature QA Smoke Map
Use this page as a release-smoke map for a deployed test environment. It is intentionally high level: canonical requirements and edge-case acceptance criteria still live in docs/features/**.
Before Testing
Section titled “Before Testing”- Confirm the release candidate, environment URL, tenant/deployment, and test account.
- Confirm which external connector providers are configured for that environment.
- Record missing provider setup as blocked coverage instead of failing unrelated product behavior.
- Use seeded or disposable test content. Do not use private customer data for exploratory QA.
- Capture the browser, viewport, account, feature path, and exact visible error copy for failures.
Core Smoke Paths
Section titled “Core Smoke Paths”| Area | Smoke path | Start here |
|---|---|---|
| Auth | Sign in, sign out, session restore, blocked unauthenticated route, and expected provider visibility for the deployment. | Auth Overview |
| Connectors | Connect a configured provider, observe status/readiness, run manual sync where available, verify reconnect/reauthorize/error messaging. | Connectors Overview |
| Library and uploads | Browse libraries, create or open a library, add eligible provider-backed content, use library focus in chat, and confirm unsupported uploads fail safely. | Library |
| Private chat | Send unfocused and focused private-chat prompts, verify focus boundaries, source visibility, recovery actions, and no private-source leakage. | Chat Runtime |
| Public chat | Start a public chat, select an allowed public model, save a default model, verify private focus/source controls are absent, and confirm public-safe skills/templates only. | Chat Runtime |
| Chat lifecycle | Rename, star, archive/unarchive, delete, edit a prior message, regenerate the latest assistant response, queue a turn, copy formatted and Markdown content, and reload the thread. | Chat Message Lifecycle |
| Sources | Open source details for answers with citations, verify unavailable/private sources fail closed, and confirm general-knowledge answers are not over-sourced. | Assistant Response Sources |
| HITL | Trigger an information request in chat, leave/return and refresh while pending, submit, use best judgment where offered, cancel, verify no-nuisance prompts do not open HITL, and confirm the Ask clarifying questions setting can disable optional prompts. |
Human In The Loop |
| Automations | Create an Automation, run now, verify generated-chat lineage, review dashboard preview, and confirm needs-attention recovery if access is missing. | Automations |
| Notifications | Verify notification menu/page behavior for available producers such as connector outcomes, shared chats, and Automation needs-attention. | Realtime |
| Skills/templates | Create or edit a skill/template, publish where applicable, select it in chat, and verify public-use restrictions in public chat. | Skills |
| Assistant feedback | Rate an assistant response, add optional feedback, remove feedback, and verify the selected message state is preserved across reload. | Assistant Feedback |
| Workspace shell | Check desktop and mobile navigation, All Chats filters, Spaces grouping, sidebar surfaces, empty states, and error-page behavior. | Web Workspace Shell |
Cross-Cutting Checks
Section titled “Cross-Cutting Checks”- Repeat core chat and connector paths on desktop and a mobile viewport.
- For list pages, verify search/filter/sort/pagination state survives reload and URL sharing where the feature exposes route-backed filters.
- For realtime surfaces, open the same account in two tabs and verify compact live surfaces update while browse pages use the documented “Load latest” pattern.
- For destructive actions, verify confirmation copy, cancel behavior, final state, and reload persistence.
- For privacy-sensitive surfaces, verify shared/public views omit owner-only focus, source, Automation, reasoning, and private connector metadata.
When A Feature Is Blocked
Section titled “When A Feature Is Blocked”- Missing provider credentials, tenant policy, seed data, or external service access should be recorded as blocked coverage with the missing prerequisite.
- Do not substitute local developer prompt packs, terminal commands, or mocked fixtures for QA release evidence.
- If a feature works only with a local developer setup, move that verification to Verification + Evals or the owning feature page’s developer checks.
Canonical Sources
Section titled “Canonical Sources”docs/features/*/spec.mddocs/features/*/stories/*.stories.mddocs/features/*/tests/*.featureapps/support-dev/src/content/docs/features/apps/support-dev/src/content/docs/platform/