# Global JSON File for Scenario Editor Tests

## Recommended guidance

Use a Global JSON file when Scenario Editor tests need reusable configuration, environment values, or controlled data that should not be duplicated across many scenarios. Keep the file structured, reviewed, and version controlled.

## Good candidates for Global JSON

- Environment-specific base URLs, feature flags, or labels.
- Reusable test values that are safe to store with the project.
- Shared configuration used by multiple scenarios or suites.
- Non-secret identifiers that help tests remain portable across environments.

## Do not store

- Passwords, tokens, API keys, or production customer data.
- Large datasets that should live in DPLs, CSV files, or controlled test-data systems.
- Values that change every run and make results difficult to reproduce.

## Maintenance checklist

1. Validate JSON syntax before committing or uploading the file.
2. Use clear property names and avoid duplicate keys.
3. Document which scenarios depend on the file.
4. Review changes with the same care as scenario or service code changes.

*Last updated: October 5, 2026*