I have made a phone call in my android instrumentation test in test-lab, but it failed because the device in the test-lab can't connect to the mobile web. How to solve it?
I would recommend asking on the official Slack channel (firebase-community.slack.com, #test-lab), since the Firebase Test Lab eng team can directly look at your test runs. There are also other users that may have run into the same issues as you.
Related
We have created a bot which uses Luis to address user queries. Would like to understand how can we perform a performance testing to my bot which can be like a VSTS testing. Yes tried with VSTS also but of no use, since my bot api is always sending a request and response couldn't capture the exact one. Please help.
I'm not sure if you are using Azure bot service directly or the other way. Considering if you are using the Azure Bot Service following are the steps to configure performance test.
You can do performance test using Azure Bot Service from continuous integration tab
Select the team services account, subscription and location.
You can track the build and errors using Azure App insights
Let me know if you are looking for anything else.
Regards
-Jyo
I am trying to use the sample code provided for Amazon Alexa API, and trying to run hello world / history buff examples through the computer. How do I test from my local machine, about the request and response formats. In the README file it is given to visit this website : http://echo.amazon.com/#skills, but I could see nothing there as it mentions more about connecting to the device. I dont have the device, but I would like to test things locally through my laptop.
We have a tool that we built specifically for this purpose:
https://bespoken.tools/blog/2016/08/24/introducing-bst-proxy-for-alexa-skill-development
Requests and responses from Alexa will be sent directly to your development laptop, so that you can quickly code and debug without having to do any deployments. We have found this to be very useful for our own development.
Our Github project is here:
https://github.com/bespoken/bst
We are also adding other useful commands for Alexa development.
Yes, the Test tab in the Alexa Developer Console allows you to interact completely with your skill during development.
You will type in your utterances instead of speaking them, but from a program logic perspective, there is no difference.
The Test page also provides a place to type in your skill's reponses, to see what they'll actually sound like. I recommend that you do so if you don't have an actual device. Sometimes adding or removing a comment can help make the responses easier to understand, or sound more natural.
Use http://ngrok.com
See my video for a tutorial:
https://youtu.be/eC2zi4WIFX0?t=108
I'm guessing the key point in OP's question is "dont have the device".
There is a web simulator at https://echosim.io
It behaves just like any other Alexa 'device'. Login with your Amazon account and it picks up all your selected skills, etc. Shows up as just another device in the Alexa app.
Only downsides: You have to click to talk, and it's pretty slow, presumably because it has to receive, buffer, convert and re-ship the audio.
Also, I'm not sure how you register/connect to the Alexa service in the first place without an Echo/Dot device, but I assume there is a way.
UPDATE:
More recently, there are a number of free 3rd-party apps on Android and iOS devices to also simulate an Alexa/Echo device. It can be less klunky than the web site. Search for 'Alexa' in your App/Play store and try a few of them out. "Reverb" is one: https://itunes.apple.com/us/app/reverb-for-amazon-alexa/id1144695621
Good luck.
I dont have the device, but I would like to test things locally
through my laptop.
If you are developing the skill using an AWS Lambda function in Python, have a look at: https://pypi.python.org/pypi/FirstAlexaSkills/0.1.2
It can generate custom Alexa events based on your parameters (utterances, slot variables) and allows you to create test cases against your local code, as well as against AWS Lambda itself.
You can also test your skill locally by following this tutorial:
How to test your Alexa skill locally
I am currently looking for the best way to test my receiver app code. I would like to know if there is a way to have a non-production version of the receiver app code running, which is not visible to my users, so that I can test new functionalities without possibly breaking others that are currently live and in production. So far I have been doing trial and error with small snippets, but this is far from optimal.
My final goal is to be able to create different GIT branches of my code, which I can test on my Chromecast that is not visible to the public.
Thanks
One approach is to create another app id to be used for testing/development; as long as you do not publish that app id, no other device but your registered devices can see that app.
Is there any easy way to repeatedly test the installation process of a Google Marketplace App on a new domain? It seems as though when you try to install an app to a domain to which it's already been installed, parts of the process are short-circuited, even if the app's permissions on that domain have been revoked. Is there any way around this short of registering a throwaway domain for every test? Being able to automate this test would be even better, but even a repeatable manual test would be very useful.
Unfortunately you need to delete the application and install it again each time from what I gather.
You can revoke the auth here: https://www.google.com/a/your-domain-here/IssuedAuthSubTokens
You definitely don't need to register throwaway domains every time.
If you're trying to test your integration, there is "TEST INSTALL FLOW' button right in the Google APIs Console that starts a test flow. Here's a screenshot:
That's especially useful when you want to test your integration before it is published to the Google Apps Marketplace (but it still works once it is published.)
If you actually install it from the Marketplace as a tester or once published, you can go to the app listing and remove the app. Since we've launched I've added and removed my apps that way quite a few times :) Here's a screenshot:
#aleckz suggestion won't actually work since tokens are Admin authorized and not revokable by the domain user.
I’m working on technical part of a project for big bank and looking for information about using Secure Element (SE) that is embedded into Google Nexus 4.
What is a process to get access to SE?
I mean how to initiate a process with Google.
You may try to contact them directly, but Google will not give you access to (embedded) SE: they don't want competitors on their wallet application (specially on Android systems).
You can do this, current android version(4.0.4) has enabled access to SE without having support of platform vendor.
Please refere
http://nelenkov.blogspot.sg/2012/08/accessing-embedded-secure-element-in.html
Depends what your ambition is, can you elaborate ? Loading an application of your own onto the secure element will require crypto keys that only Google can provide, and they probably never will, for many reasons.
Alternatively, you should be able to do the same with a SIM. It only takes a few tools to load and configure an application on a test SIM (with test SIM), then you can fit it into a phone and access it through the Open Mobile API (see the SEEK for Android open source project) which is available on many devices.