Testing an app when it's already live and deployed - plugins!

I have to make some changes to my live app that is deployed everywhere already.

I am doing so in the development branch.

HOWEVER - the plugins are the same for live and for development, right??

As in, I can’t go messing around with plugins in my development branch and pointing them to sandboxes to test a bunch of things because that will break my live version. Right??

Are these separated somehow?

How is anyone handling the situation where you need to test in sandbox mode with a bunch of APIs while also having a live version up and running?

You can’t make any change on your live mode

You make the change on the development version and update it to reflect on the live version

You won’t break your live version when experimenting in your dev branch. However, it will break if you push those changes to live. That’s the whole purpose of having a development branch…

I’d recommend creating a dedicated branch for testing new features without messing with the main development branch, though this requires a Growth plan subscription.

Sorry. I guess I didn’t explain this well.

I’m asking about Plugins - specifically the Bubble API Connector plugin.

When you are using some service such as Stripe or something, you have a sandbox on that service for testing purposes. When you are live, you are out of that sandbox and using real money.

Bubble only has ONE area for the API calls that both the development and live environment use so once you go live, you have to use your live Keys. And you can’t test in the sandbox anymore.

How is everyone dealing with this?

Stripe plug-in for example has sandbox and live keys section directly in the plugin section.

If you are creating manual api calls, just use a variable for the key/env and when you publish, make sure to remove anything thats exposed

ooh I see. The “isn’t live version” conditional can help you sort out which functionalities to use in your workflows to handle this perhaps.

1 Like

Testing in development mode, confirming issues, fixing issues, testing in development mode again, confirming no issues exist, deploying to live knowing no issues exist in live because no issues existed in development. If I’m hyper concerned, I test with real money in live.