Company Memory UI Heavy Chrome Test
Overall
Pass
Chat Source
Pass
Panel Flow
Pass
Mobile Width
Pass
What Was Tested
A fresh Testers Tomatoes memory artifact was created for a realistic chat-to-knowledge path:
- Space:
#general - Source message:
d58bb68a-5322-431e-b057-9319bce3753c - Wiki title:
UI Heavy Buyer FAQ 1780918125732 - Slug:
ui-heavy-buyer-faq-1780918125732 - Resource URL:
https://example.com/testers-tomatoes/ui-heavy-buyer-faq
UI Test Results
| Flow | Observed UI Behavior | Result |
|---|---|---|
| Authenticated app shell | Local app opened at /chat; sidebar, Chat, Tasks, composer, and Knowledge button were visible. |
Pass |
| Chat source deep link | /chat?space=...&message=... landed in #general and displayed the exact source decision text. |
Pass |
| Knowledge panel open | Knowledge button opened the in-chat panel; filter tabs and the new resource entry were visible. | Pass |
| Panel card expansion | Expanded resource showed content, resource URL, From conversation, Edit, Delete, and View in Wiki. |
Pass |
| Panel filters | Resources kept the resource visible; Decisions hid it; All restored it. |
Pass |
| Edit mode | Edit opened title, URL, content, Cancel, and Save controls. Cancel returned to read mode with source/resource links intact. | Pass |
| Add form | Add Entry opened all type buttons. Resource type displayed URL + description fields; Add remained disabled with empty title. | Pass |
| View in Wiki | Panel link navigated to /knowledge?slug=ui-heavy-buyer-faq-1780918125732. Detail showed title, content, resource URL, Sources, source excerpt, and chat-source href. |
Pass |
| Wiki source citation | Clicking Chat message navigated back to the original chat deep link and displayed the source decision. |
Pass |
| Mobile-width layout | At browser width 711px, wiki detail had no horizontal overflow; title, resource URL, and source citation remained visible. | Pass |
Testing Limitations
The in-app browser connector could not type into input fields because its virtual clipboard bridge was unavailable. Because of that, login and new text entry were seeded through Deft's normal API, while the actual product flow was validated through the Chrome UI.
This does not look like an app regression: the visible login fields, composer, add form, edit form, and buttons rendered correctly; only automated typing was blocked by the browser tool.