Discussion
Open question
- Posts
Testing against production can expose real data or disrupt operations. When should a buyer require a separate environment?
Accepted answerRequire a test environment when integrations, upgrades, configurations, or high-risk workflows need repeatable validation before production. It should have representative interfaces and controls, synthetic or protected data, version alignment, reset rules, access controls, and defined availability. Clearly define differences from production so a passing test is not misleading. FAR Part 46 provides the general model for inspection and acceptance against contract requirements.
Community replyHow close does the test environment need to be to production for a security or performance test to be meaningful?
- You must be logged in to reply to this topic.