Configure a system
A system tells Seedalina how an entity becomes real in one of your test environments. You can connect REST APIs, database scripts, or Playwright flows, depending on the workflow you are automating.
Everything lives in Settings
Systems, script repos, users, and your license are managed together on the Settings page:
- License — your plan, seats, and license key.
- Systems — the target applications and their environments.
- Repos — the Git repositories that hold your Playwright scripts.
- Users — who can order, edit, and administer.
Add a connection
Create a system under Settings → Systems, then configure the credentials and endpoint appropriate to its test environment. Keep development, integration, and UAT separate: the same template can then produce data in the right place without relying on a tester's memory.
Build an entity template
An entity template describes the data to generate and the operation that creates it. The template editor is organized into four tabs:
- Metadata — name, key, parameters, and pool behavior.
- Properties — the fields of the entity. Use synthetic generators for values such as names, addresses, and identifiers, then map those values into the target request or script. Drag rows to set the order fields appear everywhere else, including the browser extension.
- Variants — named value sets, such as fixed login roles or reference rows. Variants round-trip to Excel: export them as a TSV table and paste an edited table straight back.
- Browser Capture — field mappings for the browser extension, plus URL and title patterns so the extension recognizes the right page and selects this template on its own.
Once the system is connected, you can use the browser extension to generate data where you test.