Test Mode

Test mode in Bubble is a development environment where you can run your app and check how it behaves without affecting your live production data. It uses a separate database from your live app.

Every Bubble app has two environments: test and live. Working in test mode lets you experiment, fix bugs, and verify workflows before pushing changes to real users.

Key Takeaways

• Separate database: Test mode has its own isolated database so your testing never touches real user data or live records.
• Safe experimentation: You can try new workflows and features in test mode without risk to your production app.
• Debugging tools included: Bubble's debugger and step-by-step workflow viewer only work in test mode, not in the live environment.
• Preview URL for sharing: You can share your test mode URL with others to get feedback before publishing to production.

What is Test Mode in Bubble?

Test mode in Bubble is an isolated version of your app that runs on a separate database from your live app. Changes you make to data in test mode do not affect your live environment, and vice versa.

When you click "Preview" inside the Bubble editor, you launch your app in test mode. Everything looks and behaves like your real app, but any data you create, update, or delete only affects the test database.

• Accessed via the Preview button: Clicking Preview in the top right of the Bubble editor opens your app in test mode in a new browser tab.
• Separate URL from live: Your test mode URL includes "version-test" in the address, making it easy to identify which environment you are in at any time.
• Independent data storage: Any records you create during testing stay in the test database. They do not migrate to production unless you explicitly copy them.

Test mode is where all your development and verification work should happen. It exists specifically to give you a safe space to build and break things before real users see them.

How Test Mode Works in Bubble

Bubble's test mode runs your app using the same logic, pages, and workflows as your live version, but against a completely separate database. This means you can test full user flows without any risk to production data.

The mechanics are simple: your app code is shared between test and live, but the data layer is split. A workflow that creates a record in test mode creates it in the test database, not the live one.

• Workflows run identically: The same workflow logic runs in both environments. If a workflow works in test, it should work the same way in live assuming the data matches.
• API calls still go live: Third-party integrations like Stripe or Mailchimp use real credentials in test mode unless you switch to sandbox or test API keys for those services.
• Debugger is test-mode only: Bubble's visual debugger lets you step through workflows one action at a time, but this tool is only available in the test environment, not in production.

One important thing to know: external services like payment processors make real transactions unless you configure their own test or sandbox modes separately from Bubble's environment settings.

Why Test Mode Matters for No-Code Apps

Test mode protects your live app from broken workflows and bad data. Without it, every change you make to your app would immediately affect real users and their records.

Building without a test environment means every experiment is a production risk. Test mode removes that risk entirely by giving you a safe sandbox for all your development work.

• Protects real user data: Users never see broken features or half-finished workflows because you catch and fix them in test before they ever reach production.
• Speeds up debugging: The step-by-step debugger in test mode shows you exactly which action in a workflow failed and why, saving hours of guesswork.
• Enables confident releases: Knowing that a feature worked correctly in test mode gives you confidence to push it live without second-guessing your workflow logic.

The concept of staging environments in software development is standard practice for good reason. Bubble's test mode applies this same principle to no-code development, making it safer for non-technical builders to experiment.

How to Use Test Mode Effectively in Bubble

Use test mode to run complete user flows end to end before publishing changes. Treat it as your final check, not your first one, and always verify that third-party integrations use sandbox credentials while testing.

Most Bubble builders underuse test mode by only checking the feature they just built. Effective use means testing the entire flow a real user would follow, from start to finish.

• Test full user journeys: Do not just check the new workflow. Test everything a user would do from login through the feature you changed to make sure nothing else broke.
• Use the debugger for every failed workflow: When something does not work as expected, run the debugger to step through each action and find exactly where the logic breaks down.
• Set third-party services to sandbox mode: Configure Stripe, SendGrid, or other integrations to use their own test credentials when running tests so you do not create real charges or send real emails.

Building a habit of thorough testing in Bubble's test mode before every publish is one of the most valuable practices you can develop as a Bubble builder at any skill level.

Conclusion

Test mode is one of Bubble's most important features for building reliable apps. It separates development work from production completely, so your experiments and fixes never reach users before they are ready. The built-in debugger makes it far easier to find and fix workflow problems quickly. At LOW/CODE Agency, we've helped 450+ clients build and scale apps on Bubble and other no-code platforms. Our clients include global brands like Medtronic, American Express, Coca-Cola, Zapier, and Sotheby's.

Frequently Asked Questions

What is the difference between test mode and live mode in Bubble?

Test mode uses a separate database for safe development and debugging. Live mode is your production environment where real users interact with real data.

Can I share my Bubble test mode with someone else?

Yes. Your test mode URL contains "version-test" and can be shared with anyone who has a Bubble account or the right permissions.

Does deleting data in test mode affect my live app?

No. Test mode and live mode have completely separate databases. Deleting records in test mode only removes them from the test database.

Can I copy test data to my live database in Bubble?

Bubble does not have a native one-click data migration between environments. You need to recreate data manually or use workarounds like CSV imports.

Why does my Stripe integration charge real money in test mode?

Bubble's test mode does not automatically set payment providers to sandbox. You must configure Stripe's own test keys separately in your API settings.

Where do I find Bubble's debugger?

Click the bug icon in the bottom left of the preview screen while in test mode. The debugger is only available in test mode, not in live.