Hi @TomV , we usually recommend running them with a CI solution like Circle Ci or Travis, to run when you commit something instead of when the file changes.
In order to run jest on file changes usually, you use the --watch option, but we haven't implemented directly that option on bst test. We will continue looking into it to see if it's something you could add from the configuration or if we are able to add that as a feature in the near future.
In order to run jest on file changes usually, you use the --watch option, but we haven't implemented directly that option on bst test. We will continue looking into it to see if it's something you could add from the configuration or if we are able to add that as a feature in the near future.
Any ideas about the html response with a
502 error? Is that something other people have reported? I assume when I start on a new tool, I'm making the mistakes everyone else makes, so usually it's been documented somewhere.. :-)
One quick follow up regarding tests not running if inside of
/lambda folder (which does make sense..) The video from Sept 2019 has Emerson Sklar demoing command line but tests are in /lambda/custom, and they run fine. Seems like that would no longer work. ( https://youtu.be/YR7y2PA0ekI )
We do recommend keep them outside of the lambda folder, typically as a top-level directory called tests
With regard to the 502 error, that is not something that has been reported before
If you share more about the specific tests we might have some ideas, but just from what you have shared, nothing comes to mind
Is there any info on how and where jest is configured? (And Happy New Year to the Bespoken team 🎉🥳🎉 )
But you can override any of them by setting a "jest" property in your testing.json - then set the configuration to whatever you like
For example:
const request = alexa.request()
.intent("MyIntentName")
.slot("SlotName", "SlotValue")
.set("forceError", true) // Setting additional property
And then my code that reads it and throws an error:
https://github.com/jkelvie/ClassicMovieMusts/blob/master/lib/index.js#L16
https://github.com/jkelvie/ClassicMovieMusts/blob/master/lib/index.js#L16
how do i revoke virtual device access to my alexa developer account?
With regard to removing access, we are listed as a device like any other and can be removed in the same way
Such as explained here: https://www.cnet.com/how-to/how-to-remove-alexa-devices-from-your-account/
How can I assign a4b room and profile with the virtual device?
Are there other ways to associate a4b information during integration testing?
1) Deploy the skill as a normal skill in development mode and test that way
2) We can also test it using our Test Robots with actual devices - this allows for true end-to-end testing of A4B experiences
If you message me directly, I can send over more information on the second approach
I am trying to access my virtual device using curl with the following command: curl -v -k https://virtual-device.bespoken.io/process?message="What Time Is It"&user_id=<my access token>
I receive the following message :
I receive the following message :
<!DOCTYPE html>
<html lang=en>
<meta charset=utf-8>
<meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
<title>Error 400 (Bad Request)!!1</title>
<style>
*{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}
</style>
<a href=//www.google.com/><span id=logo aria-label=Google></span></a>
<p><b>400.</b> <ins>That’s an error.</ins>
<p>Your client has issued a malformed or illegal request. <ins>That’s all we know.</ins>
<html lang=en>
<meta charset=utf-8>
<meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
<title>Error 400 (Bad Request)!!1</title>
<style>
*{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}
</style>
<a href=//www.google.com/><span id=logo aria-label=Google></span></a>
<p><b>400.</b> <ins>That’s an error.</ins>
<p>Your client has issued a malformed or illegal request. <ins>That’s all we know.</ins>
curl 'https://virtual-device.bespoken.io/process?message=%22what%20time%20is%20it%22&user_id=TOKEN'
It did NOT work when I took out the character encoding in the message parameter - just saying "what time is it" as opposed to %22what%20time%20is%20it%22
h
The quota and credit card details don't appear.
number of devices does load up.
thanks,
Hi, @akhil1296 are you perhaps behind a firewall or any network restriction? We have heard from such cases in corporate settings. https://read.bespoken.io/cli/faq/#my-organization-uses-a-firewall-how-do-i-use-your-tools-with-it , if that's not the case, a screenshot of the error or the bst-debug.log content that should be on the folder where you run bst can help us with the debug.
You can send those privately to me by direct message if you don't want to expose any kind of personal information