Q & A
Why would I care about test mode?
Test mode allows you to run experiments without affecting production.
You can be confident that your payees will never see statements / payouts from test calculations.
You don't have to delete test calculations immediately after you are done to keep your workspace tidy.
You can keep your test calculations because you know they will never affect production.
Is test mode dangerous?
When you enable test mode, payees and other admins are NOT switched to test mode because this is an admin-only individual setting.
Test calculations are never be visible to regular payees.
Test calculations are only visible to other admins with test mode enabled.
When exporting payouts / running reports / viewing dashboards with test mode enabled, keep in mind that amounts from test calculations are included.
In the example below, the payroll export indicates that some amounts should NOT be paid, because they originate from test calculations.
Do I need to create test transactions to use test mode?
If you only want to run tests against production transactions, you do not need to create test transactions.
However, if you want to test some edge scenarios, then you have the option to create test transactions.
They will only be processed in test mode.
Additional Notes
- The setting to automatically run calculations ignores test calculations
- This setting is only responsible for running production calculations
- APIs such as the OData API ignore test calculations
- API callers do not need to indicate whether test data should be included or not