Skip to main content

Testing your Configurations on Statsig

Statsig enhances your engineering velocity by offering tools and features that allow you to test configurations quickly while ensuring reliable outcomes. This page highlights key features across the product to help you test efficiently.

Overrides: Test Features, Experiments, or Holdouts​

Overrides allow you to manually configure features, experiments, or holdouts for testing purposes. This method enables safe testing without affecting live production data or skewing experiment results. Overrides are excluded from Pulse analysis to maintain unbiased results.

  • Use Segments to target overrides to pre-production environments or specific groups (e.g., employees) for testing.

Feature Override Example Experiment Override Example

For more details on adding overrides, see:

Unit Testing with Statsig​

Statsig's Server SDKs offer a localMode feature that disables network access, ensuring that tests run locally and independently of production systems. When localMode is active, the SDK returns default values, allowing you to mock features and experiments in a controlled test environment.

Override APIs for Testing​

You can use the overrideGate and overrideConfig APIs to set specific overrides for users or globally during testing.

function overrideGate(
    gateName: string,
    value: boolean,
    userID?: string,
): void;
function overrideConfig(
    configName: string,
    value: object,
    userID?: string,
): void;

For example, to override a gate for testing:

statsig.overrideGate("example_gate", true);

Environments: Configuring Development, Staging, and Production​

Statsig enables you to assign environments to feature gates, experiments, and events. By default, checks without a defined environment are assigned to Production. You can customize environments (such as Development, Staging, or Production) and use them to target different versions of feature gates or segments.

  • Non-production events appear in diagnostics but are excluded from Pulse results to ensure production data is prioritized in final analyses.

Customizing Environments​

You can map your internal environments to Statsig's built-in environments or create custom mappings. Common setups include:

  • Assigning Dev One boxes to Development.
  • Creating an Early Access slice (e.g., 1% of production users) as part of the Production environment for phased rollouts.

For more details on environments, refer to this Statsig blog post.