![]() ![]() Pay attention to how performant the add-on is. Make sure any error conditions are handled gracefully. That the service can be accessed and behaves as expected. ![]() If your add-on connects to a third-party API or other service, verify Make sure the add-on behavior is correct as the user movesįrom context to context, and between non-contextual and contextual cards. Test card navigation flows thoroughly in all the host applications theĪdd-on extends. In addition, be sure to do the following: While testing your Google Workspace Add-on, be sureįor add-on development. You can reinstall the deployment at any time by These steps immediately remove the deployment and the add-on no longer appears To uninstall an unpublished add-on deployment, follow these steps: You may need to refresh the host application tab before the add-on Once installed, the add-on is immediately available in host applications itĮxtends. With their account (edit access is required). You can let other users test the add-on by sharing the Apps Script project Open the script project in the Apps Script editor.You can install unpublished add-ons from Apps Script's Deploymentsįollow these steps to install an unpublished To let other people in your organization test the add-on, grant them editorĪccess to the script project.You must have editor access to the add-on's script project.This page describes how to install an add-on that is currently underĭevelopment (called an unpublished or developer add-on) for testing or Before publication, however, it is useful to test theĪdd-ons that you develop within the host applications they extend. When you publish an add-on, users can install it through the host application ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |