Staging environment
Agents and tools · test environment, test stand, staging, pre-prod
A separate copy of a system where you can try and break things without touching the live one (production). There are usually three environments: local on the developer’s machine, test (staging) and production; a change moves through them in order. Some teams add pre-prod right before production: a stand as close to production as possible. An agent reproduces bugs and checks changes on staging. The system’s dependencies, data and external services, are plugged in as copies of the real ones or as mocks: copies are closer to reality, mocks are cheaper and so used more often. Staging differs from a sandbox in purpose: a sandbox fences in the agent’s actions, while staging is a copy of the whole system. In 1C, staging is a test database.
Development vs staging vs pre-prod vs production
| Development | Staging | Pre-prod | Production | |
|---|---|---|---|---|
| Where | the developer’s machine | a separate server or database | a server set up like production | the server users work with |
| Data | test or anonymized copy | a copy of production or mocks | a fresh copy of production | real |
| What for | write and try right away | check the whole change | the last check before release | users’ work |
| Always there | yes | yes | not always | yes |
| What the agent may do | read and write | write and run checks | run checks; changes only through a release | no writes; read only if allowed, a person moves changes |
Source: Wikipedia: Deployment environment
Read more: Local, test and production databases in 1C
Where it appears · 3
- MCP server and AI agent for 1C · Harness
- Claude in Chrome · Harness
- QA work after support with an AI agent · Harness