> For the complete documentation index, see [llms.txt](https://docs.tesseract.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tesseract.fi/earn-direct-and-earn-api/earn-api/acceptance-testing.md).

# Acceptance Testing

The Earn API integration acceptance testing ensures that both the user interface and backend financial transactions are functioning correctly. It evaluates essential functionalities including account creation, product access, deposits, withdrawals, and balance and transaction visibility. It also tests the integrity of settlement processes and wallet configurations to ensure accurate and efficient financial interactions between the partner and Tesseract.

These tests are performed directly in Production.

### TC\_1: User Journey Test

**Objective.** Verify that the user can access and interact with all selected Lending products through Earn API — ensuring that account creation, deposit, withdrawal, and balance views all function as expected within the integration.

**Key steps:**

1. **Creation of a new user and access to products.** Ensure new users can see and access all available Tesseract products.
2. **Deposit.** Test the deposit function for Lending products.
3. **View balances.** Check that the user's balance updates correctly after deposits.
4. **View transactions.** Ensure the user can view their transaction history for both deposits and any accrued interest.
5. **Withdraw funds.** Confirm that withdrawals are processed correctly and balances update accordingly.

### TC\_2: Settlement Test

**Objective.** Assess the accuracy and efficiency of settlement transfers between the partner and Tesseract — verifying that all financial transactions related to settlements are handled correctly and that wallet configurations are set up properly.

**Key steps:**

1. **Deposit across all products.** Test the deposit functionality by ensuring the partner owes Tesseract for all currencies, simulating a real-world load on the system.
2. **Observe Day 1 Earn API reports.** Check the reports for any discrepancies in the recorded transactions and ensure that all expected outbound transfers to Tesseract are successful.
3. **Withdraw funds and observe Day 2 reports.** After ensuring all funds are deposited, test the withdrawal to simulate Tesseract owing the partner. Verify the next day's reports to ensure all inbound transfers to the partner's wallets are successful.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tesseract.fi/earn-direct-and-earn-api/earn-api/acceptance-testing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
