Testing and handoff

Test the integration#

• Test connect, cancellation, session/customer/state mismatch, expired attempts, callback replay, and issuer/resource mismatch.
• Test encrypted persistence across restarts, proactive refresh, rotated token persistence, concurrent refresh, disconnect, and revocation failure.
• Test two customers with distinct credentials cannot access each other's connection, tools, jobs, or results.
• Test that reconnecting the same Dativue account through the same product invalidates its previous grant and surfaces reconnect required there.
• Test tool pagination, argument validation, MCP errors, insufficient credits, pending jobs, and retry/idempotency handling.
• Test the integrations UI on mobile and desktop, including keyboard access, failures, and reconnect/disconnect states.
• Complete a real browser OAuth flow and obtain an actual free quote through the implemented product connection.
• Keep mocked protocol tests, live authenticated access, and paid provider verification separate in the report.

Report the outcome#

Finish by listing the code and configuration changed, checks actually run, and any remaining human sign-in, consent, or deployment step. Use precise status: implemented locally, tested, authenticated access verified, deployed, or pending. Do not claim publication, deployment, paid research verification, or connection success without the corresponding evidence.