Skip to main content
This section describes the available actions in the test mode area. Using these actions, test mode can be activated, deactivated, and switched. When activating it, you can also enable extended debugging and simulate failed payments.

Actions overview


Actions

TestModeOn

This action activates test mode. The user must provide the configured test mode password. With the makePaymentFail parameter, payments in test mode are additionally simulated as failed. This causes orders to run into the error case on purpose, so that the templates and workflows designed for it can be checked. The current configuration can be queried in the template via $wsTestMode. Usage example
Can be used on the test mode page (testMode.htm), through which shop operators or testers can activate test mode with a password to see test-specific content.
Parameters Error codes Related modules, variables & methods Example showing how test mode is activated via a password form, optionally with debugging and simulated failed payments.

TestModeOff

This action deactivates test mode and the shop returns to normal live operation. Usage example
Can be used on the test mode page or in the shop header to deactivate test mode directly in the shop.
Related modules, variables & methods Example showing how test mode is deactivated via a button.

TestModeChange

This action switches the active test mode without completely deactivating it. This is useful when multiple test modes are configured. Usage example
Can be used on the test mode page when different test scenarios or configurations are available in parallel and you want to switch between them.
Parameters Error codes Related modules, variables & methods Example showing how the debug setting of the active test mode is changed.