Testing apps against Exponential
This folder is for app developers who need an Exponential installation to develop and test against. The choice of installation matters: a public demo is quick to look at, but only an installation you control lets you make keys, classes and test content freely.
Contents
Where to test
| Installation | Good for | Not good for |
|---|---|---|
| A public demo | seeing the administration and content; probing which APIs answer | keys, writes, your own classes; it is rebuilt on a schedule |
| A local installation of your own | everything during development; automated tests | production data and load |
| A staging copy of the production site | final checks with the real classes, roles and content | destructive tests |
Tests an app needs
- Contract tests against a local or staging installation: one read per route and service the app uses, checking the keys and types it parses (Fields and field values).
- Permission tests: the app's user can read what it shows and nothing it must not, and its writes are refused outside its folder (Permissions for app users).
- Error tests:
401,403,404,429and timeouts are handled (Errors and status codes). - Offline tests, if the app syncs (Syncing and offline reading).
Pages in this folder
| Page | Answers |
|---|---|
| Testing against a demo | Probing an installation, and what a public demo allows |
| A local test installation | Installing one in minutes and preparing it for an app |
Related pages
- Testing applications
- Launch checklist
- Demo mode FAQ
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.