Setting Up A Virtual Device


In order to test your Alexa skills and Google Actions, you need to create a Virtual Device. What is a Virtual Device? It is like a physical Amazon Echo, but one that can be interacted with programmatically.

We’ll create a trial Virtual Device for you, the only thing we need you to do is to grant us to access to your Amazon Alexa or Google Assistant account. Once completed, you will have a token, which uniquely identifies the Virtual Device, that you can use in your tests.

There a couple steps for the setup - but don’t worry - you will only have to do it once. And if you run into any issues, just ping us here. We’ll get it sorted out quickly!

Creating A Virtual Device

Virtual Devices for Alexa

  1. The way to get a token is through Bespoken Dashboard. Sign up for free or login; you will see a screen like this: Bespoken Dashboard

  2. Add a source for your skill, to do it just click on the big + icon below the llama, you will be asked to input the name for this source, for example, “my awesome skill”. Then click on the text saying “Validate your new skill »“. You will see a window like this: A skill source inside Bespoken Dashboard

  3. Click on the “Get validation token” link, you will see an Amazon window where you have to log in: Window to log in with Amazon

  4. After providing your credentials you will return to Bespoken dashboard and the “Validation Token” will be retrieved automatically: Skill source with token retrieved

Virtual Devices for Google

To create a virtual device for Google, use this link:

Once you have gone through the authentication process, the token that identifies your virtual device will be presented on the screen. Use this token in the subsequent steps.

Using the Device In Your Scripts

Now you can use the virtual device with your test script. Place it in the testing.json file of your project like so:

    "virtualDeviceToken": "MY_TOKEN"

See how we do it here.

And that is all you need in the setup process, now you can continue with the creation of your test scripts, or using Virtual Device programmatically.