Hi everyone,
I am looking for input on how other teams handle plugin testing and lifecycle management. I'd appreciate hearing what is working well for you!
Our current process:
We build and test in our Sandbox environment. We temporarily add testers, and once testing passes, we remove them to keep the environment clean and restrict access. We then export the plugin to Production and run a quick smoke test to confirm it works. For enhancements: We build the changes in Sandbox, export the new version to Production, and then swap them (turn off the old Production plugin and turn on the updated one). We have to keep the original plugin active in Production while we build the enhancement in Sandbox. What we are trying to figure out:
We are looking for a simpler approach. We considered just building directly in Production and using the Launch Configuration to whitelist our testers (via "Allow selected users"), but we hit two roadblocks:
System Triggers (Ambient Agents):
- How do you safely test webhooks or scheduled triggers in Production? Since System Triggers don't support Audience Settings (you can't whitelist testers), we aren't sure how to test these without accidentally impacting the live environment.
- Live Edits: How do you handle making updates to a conversational plugin in Production when saving your edits immediately pushes those changes live to users?
If your team has a cleaner testing approach, or if you have found workarounds for the two roadblocks above, I would love to hear your strategies.
Thanks!