# Testing

Three layers, each proving a different thing. Full details in [`tests/README.md`](https://github.com/OpenG2P/audit-manager/blob/develop/tests/README.md).

## 1. Unit tests — schema validation (no infra needed)

Sub-second, pure pydantic. Validates every sample event, enforces required fields, covers enum constraints and the Postgres column mapping.

```bash
python -m venv .venv && . .venv/bin/activate
pip install -e ".[test]"
pytest tests/unit/ -v                # 30 tests
```

## 2. Smoke test — end-to-end against `docker compose`

Posts every sample event shape, posts the batch, triggers an expected 4xx, waits for Kafka → Postgres settle, then queries Postgres to verify every expected id landed. Also verifies idempotency (repost = no duplicate row).

```bash
docker compose up --build -d
tests/smoke.sh
```

Overrides: `AUDIT_URL`, `SETTLE_SECONDS`, `COMPOSE_PG_SERVICE`.

## 3. Load test — concurrent POSTs, no-drop verification

Sends N unique events with C concurrent workers, then confirms all N are in Postgres.

```bash
N=1000 C=20 tests/load.sh
```

## Postman collection

Import [`tests/postman/OpenG2P-Audit-Manager.postman_collection.json`](https://github.com/OpenG2P/audit-manager/blob/develop/tests/postman/OpenG2P-Audit-Manager.postman_collection.json) into Postman, Bruno, or Insomnia. Folders:

* Service endpoints (`/v1/auditmanager/health`, `/v1/auditmanager/version`, `/v1/auditmanager/config`, `/v1/auditmanager/docs`)
* Single events — success paths (login, views, updates, payment approve/reverse)
* Single events — failure / denied outcomes
* Batch ingestion
* Negative tests with assertions

Each request ships with test-script assertions (`202 Accepted`, expected ids, 4xx on invalid). Use the **Runner** to fire the whole collection.

## Sample events

Nine JSON fixtures under [`tests/sample-events/`](https://github.com/OpenG2P/audit-manager/tree/develop/tests/sample-events) cover every realistic OpenG2P audit shape — reusable as `curl -d @file.json`:

```bash
curl -sX POST http://localhost:8000/v1/auditmanager/events \
  -H 'content-type: application/json' \
  --data-binary @tests/sample-events/04-beneficiary-updated.json
```


---

# Agent Instructions: 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:

```
GET https://docs.openg2p.org/platform/platform-services/audit-manager/testing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.