Prepare a Test Set
Select the website and complete catalogue loading, field setup, embedding, consultant settings and the knowledge base. Prepare real products with known SKUs, a product with variants, an unavailable variant and a question about a fact missing from your data. Have a current policy page and a safe test contact ready.
Agree on expected results before testing. For example, “outdoor tiles under <budget>” must use confirmed properties of the same offer, not simply find the word tiles. If frost resistance is unknown, the correct answer acknowledges the limitation. Any product suggestion is not automatically a successful recommendation.
Test in a normal browser on the store page, then on a mobile device. Record the date, interface language, exact query, selected product, outcome and responsible party. Do not include keys, tokens, other people's contact details or private conversations in the record.
Check Search and Cards
| Scenario | Example action | Acceptance condition |
|---|---|---|
| Exact product | Enter a real SKU | Correct product found; link opens |
| Category | Enter a shopper's name for a group | Results match the query's meaning |
| Imperfect query | Repeat a name with a common typo | Usefulness checked without unrelated substitution |
| Filter and sort | Limit price and choose an available sort | Cards satisfy the selected constraints |
| Source change | Update price or description and allow processing | New information appears in search |
| Variant | Select a size or colour | Price and stock belong to the selected offer |
Compare the card with the store, not just the account's product list. Importing, building searchable results and displaying the widget are separate stages. A product in the account with empty search results calls for an index check, not another script insertion.
Test Substantive Answers
- Ask about delivery in your own words without repeating the material's exact title.
- Ask about an exception: another area, a bulky product or a custom service.
- Request a product with two constraints, such as budget and size.
- Ask about an absent attribute and confirm the answer is not invented.
- After updating a material, start a new conversation and repeat the question.
Expect answers based on current active sources, with appropriate clarification when data is insufficient. In Services mode, check the route towards an estimate or meeting rather than a stock promise. In Support, an unconnected order-status function must produce an honest limitation, not a fabricated delivery date.
Test the Basket without Purchasing
Select an available variant, add it once and open the native basket in the same session. Compare variant, quantity, price and currency. Test an unavailable variant: a store rejection must not appear as successful adding. A price difference must have a clear message, or an indication that price verification was unavailable.
Test a lost-response retry as the same operation, not a fresh intentional addition. A second successful click may legitimately increase quantity. Limits are explained under basket integration. Do not proceed to payment to verify search: adding, checkout, payment and order confirmation are distinct events.
Check Contacts and Delivery
Submit the agreed test contact. Under Chats (/lk/dialogs), find the conversation using search, open it and check the message sequence. Use the available export for the selected period if needed. Under Requests (/lk/leads), check contact details, summary and state. Move the test lead into progress and close it after testing.
Check the chosen notifications, active CRM destination and every connected shopper channel separately. An account record does not prove email delivery, and an email to a manager does not prove a bot replied to a shopper. Confirm receipt at the destination.
Record the Launch Decision
| Outcome | Meaning | Next action |
|---|---|---|
| Passed | Expected result obtained on the site and relevant system | Record date and tested cases |
| Failed | Incorrect product, fact, action or delivery | Fix that stage and repeat the case |
| Not applicable | Feature disconnected or unnecessary | Explicitly exclude it from shopper promises |
Check mobile width, panel opening and closing, usable links and unobstructed important buttons. If using a screenshot, show a specific step, label demonstration content “Demo” and conceal secrets. An image does not replace executing the action.
Launch only after material data and action errors are resolved. Do not promise unconnected capabilities. Use troubleshooting and product scope to investigate failed cases.