When setting up a new project, or even a new functionality, its important to be able to test things first, before releasing them into production. For this sake, its usually necessary to configure test credentials for carriers, or configure dummy values that make testing easy. None the less, when releasing into production is crucial that all configurations can be done in advanced, as to release downtime to 0.

Thanks to our test environment feature, you can apply a test value to a field, while still having access to the site value (initial value). Test values will only be used in the test environment you are at, and will never be imported into production. This allows to safely test functionalities, and then deploy into production, the site values.

Test values and initial values

Test value overrides the current environment's initial configuration value, enabling testing with a different setup while retaining the original one (Initial value).

The initial value represents the configuration applied when no test value is set (an empty test value counts as a value; the test value section must remain unconfigured for this to function).

Example

Initial value

When there is only the original value, that’s the one used. In the following configuration, john_doe is considered as the set value for user identifier.

Open

Setting up a test value

It is possible to override the initial value thanks to a test value. In the following configuration john_doe_test will be used, and john_doe will be kept as a reference in the intial configuration.

Adding a test value

Open

 

Setting a value for the test value

 

Removing a test value

If we no longer require a test value, we can delete it, as a result, the initial value will be applied.

After removing the test value, the intial value is applied.

Form-based configurations

Code-based configurations

Only the subset of field overwritten will take the test value, other fields will take the value of the site initial configuration.

Example

In the following example, only credentials.account_id and credentials.password are ovewritten, while the rest of field keep the initial value.

Importing/Exporting test values

• Test values will never be imported into production, only initial values can be imported.

• In non-production environments, test values have to be manually selected for them to be imported. By default, they will not be imported.

Frequent Asked Questions (FAQ)

If I modify the configuration in production, is a manual action required to adapt the initial value part of the qualification, or is it automatic?

Yes, a manual action is required. Configurations are specific to the environment where they are made. To apply them to another environment, they must be migrated manually.