Sandbox testing protocols
Set clear rules for how changes are tested before reaching production. The protocol defines which environment to use, what evidence must be recorded and which approvals are required. This gives tested in sandbox a consistent, verifiable meaning across your team.
“It worked in sandbox” needs a clear testing standard
A change may be tested once using outdated data and an administrator role, then described as ready for production. That provides little evidence that it will work for the users and processes affected.
Sandbox testing protocols define the level of testing required for each type of change, the user roles involved, the data needed and the evidence recorded for every result. They also set the approval requirements a change must meet before it can move into production.
How we run sandbox testing protocols in NetSuite
Senior consultants oversee the work, and you can see progress as it happens. Approvals and decisions stay with your team.
- Testing levels by change typeEach type of change is assigned an appropriate level of testing. A simple field update may need a basic smoke test, while a rebuilt workflow requires complete scenario testing. The rules are agreed in advance, keeping the effort proportionate to the risk.
- Testing with real user rolesChanges are tested using the roles that will use them in production. This helps identify permission and access problems that an administrator account may not reveal. Administrator-only testing isn’t accepted as sufficient where other roles are affected.
- Data freshness requirementsThe protocol identifies which tests need a recently refreshed sandbox and links them to the refresh schedule. This reduces the risk of relying on results produced from outdated test data.
- Testing evidence standardsEach testing level specifies the evidence required for a pass, including the steps completed, the results observed and any supporting screenshots. This creates a lasting record that others can review.
- Production approval gatesThe protocol defines the evidence and sign-off required before a change can move into production. Only changes that meet the agreed testing standard proceed through the release process.
- Protocol upkeepTiers and standards are revisited as the account and the team evolve, keeping the rules proportionate over time.
Testing done differently each time?
We write sandbox testing protocols your team can follow and evidence. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.
What handing it over buys you
Test claims carry content
Tiered, evidenced runs mean ‘worked in sandbox’ has a defined meaning.
Permission surprises end in rehearsal
Role-realistic testing catches the change that breaks for real users before it reaches them.
Production changes arrive proven
The promotion gate means untested change loses its route in.
Effort stays proportionate
Tiering keeps the small change untaxed and the big one properly tested.
From tier map to a working gate
Define the tiers – change classes are agreed and mapped to test depth.
Set the standards – roles, data vintage and evidence are set per tier.
Install the gate – promotion rules are built into the change lane.
Run & refine – the protocols go live and are revisited on a rhythm.
What to know before you hand it over
- !Testing effort should match the risk. If every minor change requires the same process as a major release, users are more likely to bypass the rules. Tiered testing keeps simple changes efficient while applying stronger evidence and approval requirements where the potential impact is greater.
- !The same rules apply to changes made through the service. Any work we complete must meet the agreed testing, evidence and approval requirements before it moves into production. This keeps the promotion process consistent for everyone.
- !Sandbox testing has practical limits. Differences in data, integrations and environment settings mean some behaviour may only become visible in production. These limitations are documented during testing, with post-release checks used to confirm the change after deployment.
Sandbox Testing Protocols FAQs
Which changes need full testing?
How do sandbox testing protocols relate to user acceptance testing?
Do we need a separate sandbox for each type of testing?
Who approves a change for production?
Does this slow down small changes?
Last reviewed: 9 November 2026 · Written by the Suite Generation team
Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.
