Test tenant
A logically bounded customer context of a multitenant application, configured for testing.
Set up a context for testing
A test tenant is a customer context configured for testing in a multitenant application. Suitable test accounts and data are assigned to it. It may still share technical infrastructure with other contexts; its name does not demonstrate a separate operating environment.
In a fictional example, a test order is prepared there. Mail and shipping integrations must be configured so no real shipment is commissioned. Check background jobs and access rights too. Distinguish isolation between tenants from separation from production resources. Document and verify which systems and data actually participate. Use suitable synthetic test data and explicitly designated test access.
Sources
Related terms
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- End-to-end testA check of an agreed workflow across the system parts essential to it.
- Transactional inboxA transactional inbox uses durable message records to protect local processing against duplicate deliveries.
- Message acknowledgementA message acknowledgement tells the broker that a delivery has been received or processed according to the agreed rule.
- Retry jitterRetry jitter varies waiting times randomly to spread retries and reduce simultaneous requests from many clients.
- Webhook replayWebhook replay means sending a webhook notification again. Deliberate recovery and replay attacks require different checks.
Articles on this topic
APIs & Integration with ASES
ERP, CRM and shop cleanly connected