Appwrite Testing

Core Rule

Keep the test suite pyramid-shaped: many fast unit tests, fewer service/API e2e tests, and very few broad workflow tests. Push each assertion to the lowest level that still proves the behavior.

Prefer fast feedback over formal labels. A narrow integration-style unit test with deterministic fakes is better than a slow e2e test when it proves the same behavior.

Choose The Test Level

Use tests/unit/... for:

• Pure validators, helpers, mappers, parsers, filters, retry classifiers, event builders, URL/security checks, and branching logic.
• Worker building blocks that can be called with fake adapters, in-memory collaborators, or scripted test doubles.
• Regression cases where inputs and observable outputs can be asserted without HTTP, Docker services, queues, Swoole coroutines, or real network calls.
• Boundary serialization/deserialization when the external side can be represented with a deterministic fake response or document.

Use tests/e2e/Services/{Service} for: