Test Mode is a safe environment to try out and demonstrate features without affecting your real data. It creates a separate database; while it is active, everything you do happens in that parallel database, and your real one sits untouched, waiting.
What it is actually for
- Learning without risk. Trying category deletion, bulk moves or a strange import with no fear of ruining months of history.
- Showing the app to someone. With data masked, you demo how it works without exposing real amounts and names.
- Reproducing a problem. If something looks wrong, you can repeat the steps in a disposable database before touching the one that matters.
The five test formats
| Format | What you get |
|---|---|
| Full mask of text and amount | A copy of your data with names, classification expressions and amounts changed deterministically. Analysis patterns are preserved — the shape of your spending stays recognizable — but nothing sensitive is exposed. It is the default choice for demos. |
| Minimal text mask | Masks only the text and keeps the amounts. Useful when you need the totals to still match reality. |
| Fill with random data | Generates a demo dataset from scratch, unrelated to your data. Good for exploring screens you don't use yet. |
| Empty database | Starts from absolute zero. It is the closest thing to seeing the app as a brand-new user sees it. |
| Identical copy | An exact replica of the real data, with no masking at all. Only do this in a safe environment — and the app requires you to acknowledge the terms before releasing it. |
This option creates an exact copy of your real data, including sensitive information. If the goal is to show the app to someone, always prefer the full mask — it exists precisely for that case.
Getting in and out
- Initialize. Choose the format and generate the test database. While the app builds the file, a progress bar shows how it is going.
- Enter test mode. From then on, a notice stays visible across the screens — including the main one and inside each category — so you never mistake where you are.
- Exit with confirmation. Exiting asks for the device's security confirmation. That is deliberate: it is the border between fake and real data, and it deserves a pause.
- Discard when you're done. Discarding deletes the test file and clears its configuration. Nothing you did in there touches the real database.
Test mode is not available in the web environment — it depends on a local database file. And there is a single test database: generating a new format replaces the previous one, so discard it first if you want to keep the current state.