> ## Documentation Index
> Fetch the complete documentation index at: https://holder.docs.fiskil.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Test personas

> The minimum set of test customers to use when testing your CDR Data Holder solution in UAT.

A **test persona** is a test customer in your UAT data that represents a real type of CDR consumer. Testing with several personas confirms that each customer sees the right accounts in the consent flow and receives the right data.

***

## Recommended personas

As a minimum, set up these three personas:

| Persona | Description | What it tests |
| - | - | - |
| **Persona A** | The owner of a single account | The basic consent flow, with one account shown for selection |
| **Persona B** | The owner of two individual accounts | Account selection with multiple accounts, and sharing data from only the selected accounts |
| **Persona C** | The owner of a business account | Business customer details and accounts held by a non-individual customer |

> [!TIP]
>
> Run every test phase for each persona. Throughout the phases, the guides call out where each persona should return different results, so validate against those differences.

***

## Prepare persona data

For each persona, confirm the following before you start testing:

* **A reachable email address.** Personas sign in to the consent flow and the consent dashboard with a one-time password (OTP) sent by email, so each persona's email must be an inbox your testers can access.
* **Known accounts.** Record the accounts each persona holds so you can confirm the consent flow lists all of them.
* **Known data.** Record key values, such as balances or billing details, so you can check the API responses in [Phase 2](https://holder.docs.fiskil.dev/api-reference/cdr/testing/data-validation.md).

> [!NOTE]
>
> If you use the **Fiskil Data Store**, send Fiskil the customer ID for each persona and the email address to set on it. UAT data may not have email addresses configured for your authorised testers.

***

## What to expect for each persona

| Phase | Persona A | Persona B | Persona C |
| - | - | - | - |
| [Consent authorisation](https://holder.docs.fiskil.dev/api-reference/cdr/testing/consent-authorisation.md) | One account available to select | Both accounts available to select | Business account available to select |
| [Data validation](https://holder.docs.fiskil.dev/api-reference/cdr/testing/data-validation.md) | Data for the single account | Data for the selected accounts only | Business customer details and account data |
| [Error validation](https://holder.docs.fiskil.dev/api-reference/cdr/testing/error-validation.md) | Requests for accounts the persona doesn't hold return an error | Requests for an account not selected in the consent return an error | Requests for accounts the persona doesn't hold return an error |
| [Consent dashboard](https://holder.docs.fiskil.dev/api-reference/cdr/testing/consent-dashboard.md) | Consents and shared account listed | Consents and each shared account listed | Consents and shared business account listed |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.