Skip to content

[QA] Manual Testing — New Integrations in Agentic-AQUA #41

@coelhogonzalo

Description

@coelhogonzalo

Overview

Manual QA pass for the five new swap and payment provider integrations added to Agentic-AQUA. During testing we should walk through each flow conversationally via the agent and verify correct tool invocation, responses, and state transitions. Findings can be added on the list at the end of the ticket


Scope

Wallet Setup (Introduction)

Use a dedicated test wallet for each session. Create via lw_generate_mnemonic + lw_import_mnemonic and fund with small test amounts. Check balances before and after flows using unified_balance or lw_balance. Delete the wallet with delete_wallet when done.


1. Sideswap

Tools: sideswap_server_status, sideswap_list_assets, sideswap_recommend, sideswap_peg_quote, sideswap_peg_in, sideswap_peg_out, sideswap_peg_status, sideswap_quote, sideswap_execute_swap, sideswap_swap_status

  • Ask the agent to check server status — confirm it returns healthy
  • Ask the agent to list available assets — confirm expected assets appear
  • Ask the agent for a peg-in recommendation, request a quote, execute the peg-in, and follow up on status until a terminal state is reached
  • Repeat the above for peg-out
  • Ask the agent for a swap quote, execute the swap, and verify the status flow through to completion

2. Sideshift

Tools: sideshift_list_coins, sideshift_pair_info, sideshift_recommend, sideshift_quote, sideshift_send, sideshift_receive, sideshift_status

  • Ask the agent to list supported coins — confirm expected coins are present
  • Ask for pair info on a known pair (e.g. BTC → L-BTC) — confirm rate and limits are returned
  • Request a quote, execute a send-side shift, and follow status to terminal state
  • Request a quote, execute a receive-side shift, and follow status to terminal state
  • Ask the agent for a recommendation and verify a sensible suggestion is returned

3. Eulen DePix Swaps

(This might be difficult to fully test without a Brazilian bank account but we can check that the flow makes sense)

Tools: pix_receive, pix_status, lightning_receive, lightning_send, lightning_transaction_status

  • Ask the agent to generate a PIX receive address — confirm a valid QR/key is returned
  • Ask for the status of a known PIX transaction — confirm correct state is shown
  • Ask the agent to create a Lightning invoice — confirm invoice is valid
  • Ask the agent to pay a Lightning invoice and confirm the transaction status reflects success
  • Walk through a full PIX → Lightning swap and a Lightning → PIX swap end-to-end

4. Changelly

Tools: changelly_list_currencies, changelly_quote, changelly_send, changelly_receive, changelly_status

  • Ask the agent to list available currencies — confirm expected pairs are present
  • Request a quote for a known pair — confirm rate, minimum, and maximum fields are present
  • Execute a send-side exchange and follow status to terminal state
  • Execute a receive-side exchange and follow status to terminal state
  • Ask for a quote on an unsupported pair — confirm the agent handles it gracefully

5. Send to Lightning Address

Tools: lightning_send, lightning_transaction_status

  • Ask the agent to send to a valid Lightning Address (e.g. user@domain.com) — confirm payment completes and status reflects success
  • Ask the agent to send to an invalid or unreachable Lightning Address — confirm a clear, helpful error is returned

6. Extras

  • Ask the agent to compare rates between Changelly and Sideshift
  • Ask the agent to do a USDt swap and use the cheapest option between them

Acceptance Criteria

  • All happy-path flows complete successfully
  • The agent invokes the correct tools for each user request with no hallucinated steps
  • Status follow-ups return accurate, up-to-date state
  • Error cases (bad pairs, invalid addresses) produce clear, user-friendly responses rather than raw errors

List of issues found during Testing:

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions