Test mode: development and release data
You use one app key everywhere: while you develop and in the app you ship. There is no separate test key. Every signal carries a debug flag, and Pulse keeps test signals and release signals apart.
How it works
- The SDK decides for each run of your app whether its signals are test signals (debug flag on) or release signals (debug flag off).
- Both kinds are stored under the same app and the same key.
- The dashboard shows one kind at a time. With Test mode off you see release signals, your real users. With Test mode on you see only test signals.
- Test signals never mix into release numbers, so trying things out while you develop does not distort your charts.
What each SDK does
| SDK | Marked as test data when | How to change it |
|---|---|---|
| Swift | The app is built in the Debug configuration (the default when you run from Xcode). Release, TestFlight and App Store builds send release signals. | Set options.debug to true or false. |
| Android (Kotlin) | The app is debuggable (the debug build type, the default when you run from Android Studio). Release builds send release signals. | Set debug in PulseOptions. |
| Flutter | The app runs in debug mode (flutter run). Profile and release builds send release signals. | Set debug in the options. |
| Unity | The editor and players built with Development Build checked. Other players send release signals. | Set Debug in PulseOptions. |
| JavaScript | In Node, when NODE_ENV is development or test. In the browser, when your bundler replaces process.env.NODE_ENV at build time and it is development or test. A page without such a bundler sends release signals. | Pass debug: true or false. For example debug: import.meta.env.DEV in Vite, or debug: location.hostname === "localhost" on a plain page. |
| .NET | The app is built in the Debug configuration. Release builds send release signals. A host without an entry assembly sends release signals unless you set debug. | Set PulseOptions.Debug to true or false. |
| Plain HTTP | You send "debug": true in the signal. | Leave the field out or send false for release signals. |
Your first signal
The first signal usually comes from a development build, so it is a test signal. The setup page of your app shows it arriving and says that it came from a debug build. To see it in the charts, turn on Test mode, the switch above the charts. If a chart is empty because only test signals arrived, the page says so and offers to turn Test mode on.
Before you ship
- Keep the same app key. Where the SDK reads the build by itself (see the table above), nothing changes in your code: a release build sends release signals by itself.
- Where you set the debug option yourself, make sure it is off in the build you ship. For JavaScript on a page without a bundler, make sure you do not pass debug: true.
- After release, turn Test mode off in the dashboard to see your real users.