> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/g2p-bridge/development/testing.md).

# Testing

The G2P Bridge is tested at several complementary layers:

| Layer                                                                                          | Scope                                                                                                                                                               | Where                   |
| ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- |
| Unit Testing                                                                                   | White-box, mocked services/DB — fast, run in CI on every commit                                                                                                     | `core/**/tests/`        |
| [Regression Sanity Suite](/products/g2p-bridge/development/testing/regression-sanity-suite.md) | Black-box, point-at-a-deployed-system — every API + full end-to-end cash flow verified stage by stage, plus business-rule negatives and MT940 reconciliation errors | `test/sanity/`          |
| [API Walkthrough (Postman)](/products/g2p-bridge/development/testing/api-walkthrough.md)       | Manual, learn-by-doing run through the disbursement APIs with editable CSV seed data — same flow as the sanity suite, but you drive it; doubles as training         | `test/api-walkthrough/` |
| Performance Testing                                                                            | Load / throughput                                                                                                                                                   | `test/`                 |

Use the **unit tests** to catch code-logic regressions, the **regression sanity suite** to confirm an installed environment works end to end (it now also covers the API-level negative scenarios and MT940 reconciliation-error checks that were previously standalone Postman/script artefacts), the **API Walkthrough** for a hands-on/training run against an installed system, and **performance** testing for scale.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openg2p.org/products/g2p-bridge/development/testing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.