I built a Google Docs add-on and want to let a few people try it out before I make it public. Right now I’m making testers share my project and create their own deployment which is really annoying and takes too long.
I found out I need to set up a Google Cloud Platform project. I already created one and configured the OAuth consent screen settings. I linked my Apps Script project to this GCP project and added the email addresses of my testers in the test users section.
What’s the next step to actually get my add-on installed for these beta testers? How do they access it for testing?
Testing Google Docs add-ons is a pain when you’ve got multiple testers and constant updates. Been there.
GCP test deployment works, but you hit problems with updates and version management. Testers have to manually reinstall every time.
I automated this through Latenode. Built a workflow that auto-deploys new versions to your test group when you push changes. Handles GCP API calls, emails installation links to testers (or sends via Slack), and tracks who installed which version.
Best part is automated feedback collection. Connect it to a form that triggers when testers use specific features. No more hunting people down for responses.
You can also automate beta to production. One click moves your add-on from test deployment to marketplace submission with all configs ready.
Saves hours and makes beta testing way more professional. Testers get a smooth experience, you get better feedback faster.
after adding tester emails in GCP, they need to open the Apps Script editor by going to Extensions > Apps Script. then, they can either search for your add-on or use the script ID you provide. it’s a bit of a hassle, but it works for now.
After adding your testers in GCP, go to Deploy > Test Deployments in your Apps Script project and publish a test deployment. This creates a unique test URL for your approved testers. Send them this URL - when they click it while logged into their whitelisted Google accounts, the add-on installs automatically in Google Docs. No need for testers to mess with script editors or manual deployments. Just make sure they’re using the exact email addresses you whitelisted in GCP to avoid permission problems. Way cleaner than having everyone create their own deployment.
You’re on the right track with GCP, but there’s an easier way. After adding testers to your OAuth consent screen, just share a direct installation link. Go to Deploy > Manage Deployments in your Apps Script project and create a web app deployment. Set access to “Anyone with Google account” for testing. Your beta testers can install it directly through the Workspace Marketplace using Google’s testing URL, or you can send them the deployment ID to install manually. No need for them to touch the Apps Script editor. Just switch back to restricted access before going public.