The entity pool
Every business object Seedalina generates lands in the entity pool, grouped by template and environment. The pool is the shared shelf between "someone created good test data" and "a test actually used it" — browsable in the UI and queryable from the test client.
How entries get in
- Orders — Seedalina runs a template's steps and stores the result.
- Playwright scripts — orchestrated scripts report what they created; standalone scripts can push finished objects directly. See the Playwright integration.
- The browser extension — captured form results become pool entries. See the browser extension.
- By hand — add or edit entries directly in the pool view when the data already exists in the target system.
Lifecycle
Each entry carries a status, so parallel tests never trip over each other:
| Status | Meaning |
|--------|---------|
| NEW | Generated and available. |
| LOCKED | Claimed by a test or a person; released back to the pool afterwards. |
| CONSUMED | Permanently used up — a rotated password, a deleted account, a one-time flow. Never handed out again. |
Reservations
An entry can be reserved for a specific person — for example, data generated through a Playwright order is reserved for whoever placed the order. Nobody else can lock a reserved entry, and admins can reassign or clear reservations when data should change hands.
Export and import
The pool view exports entries as CSV for reporting or a quick look in Excel, and imports them back the same way — useful for seeding a fresh environment or reviewing what a test run left behind.