Hello, I have a question about virtual-alexa. how can I do an Intent confirmation with this library on an intent that doesn't require confirmation (and hence doesn't have a dialog with the same name as the intent)? If I manually add a dialog to the model, the test framework does work, but through manual testing this breaks upsells.
We again started seeing "Invalid response: 400 Message: " for our virtual alexa scripts executed via Jenkins. We saw this before and we increased the timestamp validation limit to 150 seconds which is the max value suggested by Amazon (https://developer.amazon.com/docs/custom-skills/host-a-custom-skill-as-a-web-service.html#timestamp), which resolved that issue but it again started happening. Any suggestions?
Hi @ash-at-github , have you had any recent change in your jenkins environment or development server. A likely culprit, if it was working before, is that the timestamp has issues due the development server and jenkins being in different machines with their clocks on different times.
if you are using virtual alexa directly as a Javascript library, you can use the filter property to log the requests and verify the timestamp.
If you are using virtual Alexa through YML tests, then you enable the "trace" property and it will print out the complete requests and responses for each interaction.
If you are using virtual Alexa through YML tests, then you enable the "trace" property and it will print out the complete requests and responses for each interaction.
Hi Bespoken Team! Is it possible to use the virtual-alexa library to test interaction models only (for skills that don't use lambdas, and instead rely on external services)? I'm hoping to write unit tests to test the interaction model only; basically a bunch of "utter" tests where I'm asserting on intents and slots. Make sense?
I'll be looking into e2e later (with bespoken) to test speech reco, but right now I'm looking to build tests that assert that given an utterance, a specific intent is resolved with specific slot values. Maybe this isn't advised given that there may be a delta between what virtual-alexa resolves and what the actual Alexa would resolve?
It's called Usability Performance Testing - our most recent case study on it is here: https://bespoken.io/blog/the-mars-agency-case-study/
Our pleasure - and of course reach out if you have any additional questions
Or is it custom and you provide a quote?
It's the same pricing as for our subscription product: https://bespoken.io/pricing/ - that includes the usability performance testing
All of our products rely on interactions with Alexa/Google Assistant at their core, whether it is for end-to-end testing, monitoring or usability testing
@jperata, amazon has acknowledged an issue with upsells when using certain models. my ugly workaround is to have 1 model for testing and 1 model for deployment :/
https://forums.developer.amazon.com/questions/207372/upsell-not-responding.html?childToView=210963#answer-210963
https://forums.developer.amazon.com/questions/208737/alexa-does-not-respond-to-request-for-upsell.html
https://forums.developer.amazon.com/questions/207372/upsell-not-responding.html?childToView=210963#answer-210963
https://forums.developer.amazon.com/questions/208737/alexa-does-not-respond-to-request-for-upsell.html
I'm very new to testing. noob.
const NBA = require("../lambda/custom/nba-voice-library/NBA");
test("gets schedule from endpoint", async () => {
expect.assertions(1);
const data = await NBA.schedule();
expect(data.length).toBe(4);
});
Hi @mrseth01 , your way sounds about right. Since you are not testing the Alexa section you don't need to introduce virtual-alexa in that section. We recommend that you also add some tests with our library to emulate Alexa too, it will interact with your endpoint unless you do some steps to mock it.
Hey I'm getting an error about my network connection every time. I even tried following the node example but got this same error:
```
```
Something went wrong. Please check your network connection and try again.
I installed bespoken-tools globally with npm v10.18.1 and also tried doing it in a local project,
Is it maybe because I use node version manager and I have my default set to v13?
Hi there, i have problems while mocking dynamoDB. Running it locally works fine, but when using it in the GitLab CI following error occurs:
Uncaught exception: AskSdk.DynamoDbPersistenceAdapter Error: Could not create table (...): The security token included in the request is invalid. Any ideas?
Hi @akhil1296 , our full documentation for unit testing in Alexa using YML scripts is here. For your specific question if you are using YML, we set up an environment variable that you can use to change to get specific responses.
Since you are asking in the Virtual Alexa channel maybe you are using Virtual Alexa directly with Jest or Mocha, if that's the case then Nock is a great solution to mock API calls as @allthepies suggest.
Since you are asking in the Virtual Alexa channel maybe you are using Virtual Alexa directly with Jest or Mocha, if that's the case then Nock is a great solution to mock API calls as @allthepies suggest.
Cannot find module '/home/sylvain/spham/alexa/skill-sample-nodejs-hello-world/index.js' from 'ModuleInvoker.js'