The Assistant directory for the web is not supported for opt-in to alpha or beta.Run concurrent tests on the same action.
Provide feedback by email, via a website, in a message forum, or through Alpha and beta channelsĪre only available to your own testers.
Provide a channel for testers to send you feedback. Test stable versions of your Actions that are near release. 
Small and test the least stable, experimental versions of your Actions (suchĪs within your company or team). Google account or a G Suite account to join a test. Provide feedback by email, via a website, in a message forum, or through another Instead, you should provide testers with a way to Note: Users cannot rate your Action in the Google Assistant app if they are If there is no Production version, users will notīe served with anything. The No testing option will serve users the Production version Of the Google Assistant app labeled with one of these modes: Alpha, Beta, Testers will see your Action in the My Apps section They should click on the I'm in button at the bottom of theĪction's directory page to opt in as a tester for the first time.Īfter the tester opts in on their phone, your Action is immediately available When users click on this link, they are directed to the corresponding Action'sĭirectory page.
Log in to the Google Assistant app using the same account which youĪfter you deploy your Action, any new testers need to wait for at least 3 hoursīefore they can access the Action using the opt-in link. Have the Google Assistant app downloaded on their mobile devices in order. Make sure to indicate to your testers that they must: Once your Action has been released to the alpha or beta release channel, you should invite your testers by sharing your opt-in link (which is the same as your Assistant directory listing). To handle release channels in your fulfillment, you should provide different fulfillment URLs (for example, one fulfillment URL for the beta and another URL for the production version of your Action). The release channel information is not included in the HTTP request from Assistant to your fulfillment. Implement fulfillment for an alpha or beta release If you listed the same testers for alpha and beta, they are eligible for both and see an opt-in card for the alpha version first. The link points testers to your directory page and see the opt-in card for the eligible environment. The opt-in link represents your Action directory page and never changes. You should send an invitation email to your testers with a link to the alpha or beta version of your Action (the opt-in link). You cannot designate multiple users via a Google group email alias.Ĭopy the Opt-in link to share with your testers. Note: Testers must have a Google account or a Google Workspace. You can specify up to 20 testers for alpha testing and up to 200 testers for beta testing. 
Type in the email addresses for the testers, separated by commas.
Click either Manage Alpha testers or Manage Beta testers. To set up your testing for alpha or beta, follow these steps: Note: If you are using Dialogflow versioning, you can deploy different versions Publicly available to all Google Assistant users The table below summarizes the differences between deployment channels.Įarly testers within your team, friends, and familyĭeveloper-defined list of users. Note: You can only have one "live" alpha or beta version of your Action released. 
Since the beta version has passed Google review, you can elect to make it public at any time without another review by Google. Users will be informed that the Action is a preview version. You should use this channel to give users outside your organization access to early versions of the Action. #Alpha vs code on time full#
Users are given warnings that the Action hasn't undergone a Google review for policy compliance.īeta: This channel lets you distribute an Action to a limited set of users after passing a full Google review.Lets you distribute your Action to a small set of users without going through a full Google review.There are two types of pre-production release environments that the Actions console supports:Īlpha: This channel should be used to quickly test early versions of your Action. Lifecycle of an Action with release environments. The following diagram shows potential paths the lifecycle of an Action can take: Figure 1. The Actions console supports release environments so that you can give a limited set of users access to test a new Action, or newer version of your existing Action, before deploying it to the public. Testing your Action with users gives you the opportunity to get early feedback and fix any technical or user experience issues before you release it widely.
0 kommentar(er)
