@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'
Hi @jkelvie - the Lambda handler is being invoked as a JS function directly.
import { handler } from 'src/index';
import { VirtualAlexa } from 'virtual-alexa';
const alexa = VirtualAlexa.Builder()
.handler(handler)
...
. build()I've tried setting the env variables before and after the virtual alexa client is built, but no luck. I can only seem to set variables outside of our test file i.e. SOME_VAR=true jest
Also, I take it that it does work if it is set in the CLI via an export?
@jkelvie Yes you're correct. It works when the environment variable is exported as part of my test command e.g. FOO=BAR npm run test.
My Jest test file looks something like this:
import { handler } from 'src/index';
import { VirtualAlexa } from 'virtual-alexa';
describe("Given some state", () => {
beforeEach(async () => {
process.env.FOO = "bar";
const alexa = VirtualAlexa.Builder().handler(handler).build();
await alexa.launch();
})
it("Then some expection", () => {
expect("something").toBe("something")
})
})This is not currently working, as the environment variable is NOT picked up inside my handler.
I will try and create a minimal reproduction this weekend, if that will help?
I naturally tend to focus on the process-spawning that Jest does, but that would not apply in the sample code you show.
OK, I've added a session object using the same request() and it works, nearly! You have a bug in your Connections.Response code, the status.code value should be a string e.g. "200" whereas your code uses a numeric, 200. My code performs a type-safe check on the status code and rejects the numeric 200. You can find the Amazon documentation for the request here -> https://developer.amazon.com/en-US/docs/alexa/in-skill-purchase/add-isps-to-a-skill.html
Hi
@dmarvp @jkelvie
I was trying to run the https://gitlab.com/bespoken/utterance-testing-recipe locally, but was getting this error
> utterance-testing-recipe@0.1.0 utterances /mnt/c/Users/thedreamsaver/Downloads/utterance-testing-recipe-master
> bbt process input/utterance-test.json
command: process arg: input/utterance-test.json
No device-pool provider specified - using default.
DEVICE create token: google-3a592bde-0dcf-43a9-9c90-5910223643dd skipSTT: false tags:
Config loading class: ./csv-source using paths: /mnt/c/Users/thedreamsaver/Downloads/utterance-testing-recipe-master,/mnt/c/Users/thedreamsaver/Downloads/utterance-testing-recipe-master/node_modules/bespoken-batch-tester/src for service: source
CSV-SOURCE LOADALL input file: input/utterances.csv
BATCH READ pre-filter: 4 post-filter: 4
DEVICE LOCK tags: count: 1
DEVICE LOCK acquire tags: available: 0 token: google-3a592bde-0dcf-43a9-9c90-5910223643dd
RUNNER PROCESS run: utterance-tester_2021-04-27T20-21-42 utterance: search for museums near me
DEVICE LOCK tags: count: 0
Config loading class: ./src/utterance-interceptor using paths: /mnt/c/Users/thedreamsaver/Downloads/utterance-testing-recipe-master,/mnt/c/Users/msi/Downloads/utterance-testing-recipe-master/node_modules/bespoken-batch-tester/src for service: interceptor
DEVICE MESSAGE error: invalid literal for boolean. Not a string. retrying 10 seconds
DEVICE MESSAGE error: invalid literal for boolean. Not a string. retrying 10 seconds
when i run
npm run utterances