Display test data separately

Display test data separately

In order to effectively test the platform and not clog up real reports, we implement the ability to view all sandbox data separately from the production environment. This applies to test transactions, bonuses, logs, employee actions and debug scripts - everything is neatly highlighted and marked, with filters and isolation from real players and data.

This approach allows QA, marketing and support to work safely and clearly understand where the "test" is and where the "reality" is.

What is displayed separately

Data Type	Description
Test Transactions	Refills, Withdrawals, Cancellations - Simulated Scenarios for Logic Validation
Test bonuses and promotions	Individual appointments, wagering, burning - with the label "sandbox"
Test Users	Special Profiles Not Included in Analytics
Reports and logic	Split dashboards and uploads: sandbox ≠ production
Activity History	Test mode activities are logged in a separate thread

Functions and management

Show sandbox data only filter in all sections
Individual roles with access to test users only
Reset and clear sandbox data without affecting combat
Export test activity separately from the main activity
Protection against accidental sending of data to the combat system

Advantages

Pure analytics - no distortion by test actions
Clear separation for QA, marketing, support
Secure debugging without the risk of clogging reports
Quick validation of logic and campaigns in a sandbox environment
Convenience for external teams and partner integrators

Where especially important

Casinos and platforms with bonuses, transactions and advertising mechanics
Fintech solutions with high data sensitivity
SaaS systems with custom business functionality
Products with A/B tests and regular implementation of new features

Testing means checking, not spoiling reports. We will give you the ability to view and analyze all test data in isolation so that the sandbox is a useful tool, not a source of confusion.