Skip to content

Test plan: 'Continue in Novaworks' Deep Link

Expands on the Testing Needed section in spec.md. All scenarios assume the ADR (gateway owns untranslatable-response detection — see ../software-design/adr-gateway-owns-untranslatable-response-detection.md) is implemented.

Scenarios

  1. A2UI-disabled host receives a form → deep link offered.
  2. Given a host with A2UI support disabled
  3. When a conversation reaches a point where the agent needs to render a form

  4. Then the gateway detects the untranslatable response element, offers a "Continue in Novaworks" deep link (no raw form, no silent failure), and opening the link resumes the same conversation directly inside the correct state in the portal (e.g., the private chat containing that turn) — not a generic landing page.

  5. Turn-count threshold trigger.

  6. Given the turn-count environment variable set to a small test value (e.g., 3)
  7. When a conversation is driven past that count with no other trigger condition present
  8. Then the deep link is offered once the threshold is exceeded, and is not offered on turns at or below the threshold.

  9. And changing the env var (no code change) shifts the trigger point accordingly, confirming Open Question 2's resolution.

  10. Host that natively supports the required interaction → no deep link.

  11. Given a host with A2UI enabled
  12. When the same form-rendering scenario as (1) occurs

  13. Then the gateway does not offer the deep link and the conversation continues natively on the host — confirming the negative path from Functional Behavior step 3, and that the generic detection doesn't over-fire.

  14. Deep link delivered over a TBD transport (A2A/MCP).

  15. Given an A2A or MCP-connected host
  16. When any in-scope trigger condition fires (e.g., turn-count threshold)
  17. Then at minimum a URI/text deep link is delivered even without rich rendering support — closing the Risks-table gap that A2A/MCP fallback isn't proven end-to-end.

Out of scope for this pass

  • The sensitive-topic trigger condition (deferred per Open Question 5) — no test coverage until Superagent's sensitive-topic classification ships.
  • Section 5 re-sync behavior after the user resumes in the portal — covered separately once that Feature is elaborated.