Over a million developers have joined DZone.

How to Test a Google Home Action

DZone's Guide to

How to Test a Google Home Action

Just wrapped up your latest Google Home Action? Time to test it. Here's how to enable testing for your action through the Google console as well as add beta testers.

· IoT Zone ·
Free Resource

Digi-Key Electronics’ Internet of Things (IoT) Resource Center Inspires the Future: Read More

For this article, we're assuming you've already built a Google Home Action. This example app has used the Conversation.one platform, but you'll be working through Google's console, so the instructions should apply to any Actions. Once you have built your Action, you can test it on the Actions on Google Console before publishing it for your users. 

First, enable the Google Action on the "Actions on Google" console. Then, log into the console. From there, select your action.

Select your Action

Then, enable it for testing. Select the "Simulator" tab on the left and activate the toggle:

Enable for testing

Test on a Device

Once your Action is enabled for testing, you can test it on a real device. This could be either from a Google Home device or from the Google Assistant app. To download the Google Assistant for iOS, click here. For Android devices, click here for more information on how to enable it on your mobile device.

Activate Your Action

All you have to do to activate your Action is to talk to it. For example, you can say: “OK Google, talk to Conversation One”. (Use your own activation word instead of “Conversation One”).

Activate your actionActivate your action

Account Linking

To activate your action and have access to your data, you are required to link your account. The Google Home Action will provide a link that will redirect you a secure account linking page. If you are using the Action from a Google Home device, you will be required to open the Google Home mobile app to continue. Fill in the required information and your 4 digits pin code for to assure secure access to the account.

Account LinkingAccount Linking

Once done, you can start your conversation. You can say, for example, “OK Google, talk to Conversation One”. This time the action will reply with a welcome message.

Use Your Google Home Action

Start the conversation by providing your 4-digit PIN code. Then ask for additional information, for example: “What is my balance?” or “What are my latest transactions?”

Use your Google Home ActionUse your Google Home Action

Beta Testing

When you've completed building your action and have activated it, you can add additional beta testers to use and test it. Let's walk through setting up beta testers.

First, log into the Actions on Google Console.

Open the Simulator Tab

Click the “SHARE” button on the top right corner

Open the Simulator Tab

Then click on “Permissions”.Click "Permissions"

Add Users

Add beta testers and grant each a “Viewer” role. Note that beta testers must have a Google account. If they don’t have a Google account, they will be instructed to open one.

Add Users

Share the Link

Copy the link and share with your beta testers. They will need to log in with the same Google account they enabled on the Google Home Device or the Google Assistant.

Share the link with your users

Beta Tester Instructions

After clicking on the provided link, the beta testers will have access to the new action on their console

Beta Testers

They will be asked to select the desired action and accept the terms.

Beta Testers

Then, they will select the “Simulator” tab on the left and click the “START” button:

Select the "Simulator" tab on the left, and click "START"After activating the toggle of the simulator, they will be able to start testing the new action on the simulator — on a Google Home device as well as on the Google Assistant app that is linked to the same Google Account.

Activate the simulator

Digi-Key’s IoT Component Selector is your one-stop-shop for the IoT

iot ,google home actions ,conversational interfaces ,beta testing ,tutorial

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}