I'm currently working on a chat-bot for IBM Lotus Sametime. I'm following this tutorial.
My problem is, that I don't know how to test my bot: I've got access to a Sametime server, but I only have my personal account. It's no problem to log the bot in with this username and password, but I can't test it, because I can only log in with the same account and the bot won't react.
My question is: What is the best way to test such a bot? Can anyone point me at a working public server where I can register two accounts? Am I missing something?
Thank you
Btw: I already tested http://bleedyellow.com/ and the link from this tutorial. They all seem to be unreachable or long since abandoned.
The best way to test a bot, as with any software development exercise like this, is to do so on a test server, with a test account. bleedyellow.com is an active community, but it doesn't offer public test accounts. You'll need to set up a dev / test Sametime instance.
Related
Can you explain about Automation Anywhere Bot Testing.
Automation anywhere Bot require to test by Testing team?
If yes then can you help me out about process & documentation?
Please refer to Automation Anywhere Univesity, where you will find the detailed explanation on the bot and it's usage.
Absolutely. We used the following process at the CoE I previously led:
Developer creates and tests bot locally
Developer tests bot on a new bot runner in the QA environment
Developer tests bot running "headless" in the QA environment
QA Team/Business Owner does some testing with the bot to be sure that it performs as expected while running headless
Bot is finally promoted to production after the prior development/testing has been documented.
My app is rejected by
2.3 Apps that do not perform as advertised by the developer will be rejected
It said that the file copied into "~/Library/Fonts" failed.
It works when test by myself, I find that it will get permission fail when using the sandbox mode, did Apple reviewer will accept this feedback?
thanks
Apps must work in the sandbox no exceptions allowed.
A sandboxed application cannot write to ~/Library/Fonts.
Either store the font in the app bundle and use it from there, or put up a standard file dialog asking the user to grant permission to write to ~/Library/Fonts by selecting it.
If you get stuck doing either of those ask a specific question on them showing what you've tried. Such a question is unlikely to be seen as off topic.
HTH
My question here is pretty simple: how to properly (and 100%) configure both Live Connect and project in Visual Studio 2013 in order for the local application run and authenticate an user properly against Microsoft account.
My question may be simple, but the answer is most likely not as simple. I've been reading countless articles and possible tutorials about this, but they are all fragmented and divided into small parts that do not really conciliate each other.
So below is the situation better described, with the steps I have followed.
[Steps Followed]
1) I have created a simple MVC application using Visual Studio 2013.
2) I have configured the project (using its properties) to use IIS Express with current Project Url : https://localhost:44302/
The project runs quite well, and external authentication with Facebook, Google and Twitter run very well too. Now for the tricky part:
3) I have created account with Microsoft and successfully created application in the Live Connect Developer Center.
4) Since configuring the field Redirect URLs to a simple http://localhost:<port> will not work (well...just because they didn't want it to, I suppose), I have additionally done the following..
5) Mapped in hosts file the following domain to localhost: # 127.0.0.1 mytestdomain.localtest.me
6) Reconfigured in Live Connect the Redirect URLs field to use the newly mapped domain: http://mytestdomain.localtest.me (although I have tried this with or without the port as well).
[End result]
With this configuration, the site runs properly locally. However, when I try to sign in with Microsoft account credentials (so, when I click the "Microsoft" button), I have redirected and received the following message:
"We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later."
I honestly do not understand why wouldn't this work, when a couple of articles suggested that doing these specific steps would make it work.
What can I be missing, why would this happen at all?
If someone can write here what am I missing and we could all join effort and create in this topic a full fledged, 100% working configuration for local application testing with Microsoft authentication, I believe it would help everyone. If such topic already exist and you can point me to it (because clearly I have missed it) it would also be great.
Thank you in advance,
Mad
Actually I just found out a proper and direct answer to my question. I totally missed it somehow during the last few days of research.
Microsoft's blog has all you need to make it work, and now mine does too. No big explanations and discussions, just basic and direct step by step article.
For those who could not find it and stumbled upon my topic here in StackOverflow, here is the link. Follow it word by word, and it will work.
Answer : Configuring your ASP.NET application for Microsoft OAuth account
Background:
One of my clients' websites has become a malware infested hotbed.
Disposing of the malware has proven difficult and time consuming, and, in the meantime, we still have had to do work on the site.
For now, we went to some trouble to do our work - creating a disposable VM to just run a web browser, so we can see what the site looks like for the designers' work, for example.
I'm wondering if there's an easier (and faster) way to get an idea what the design of the site looks like. Not everyone on the project is tech savvy enough to be trusted with, for example, properly handling switching VMs.
Question:
Is there a method for safely seeing what a malware infested website looks like (for example, a service which will browse the site for me and send a screenshot), one which ideally is easy and simple enough to use that I can trust our non-tech-savvy designers to user?
You might take at look at Internet Archive: Wayback Machine to see if the site has been archived.
If a screenshot is all you need, there are several online browser simulators, such as Net Renderer (which will run any inputted web URL in a given version of Internet Explorer and then supply a screenshot). You might also try BrowserStack, which requires an account, and is not free, but does have a free trial period, and offers more than Internet Exploder.
You could also try running a browser in Sandboxie, which is simpler to set up and use than a VM (you just install it, and then use the windows right-click menu to launch any program in a sandbox of your choosing). However, it isn't free for commercial use.
I don't know if exist a standalone tool to parse a website for malwares, but I think this can help you, it's a google tool that you can you with a request and they will send you a response.
Follow the link:
http://support.google.com/webmasters/bin/answer.py?hl=en&answer=168328
Hope it helped.
Forgive me for what may seem as a stupid question but, after some rummaging around on the web, I can't seem to find how to test my Windows Phone Application. I'm not referring to the guidelines, I'm actually referring to sending it to Microsoft for them to check if it's "okay" or checking it on Visual Studio as I think there is a way of doing that in VS.
Any help is highly appreciated.
Thank you.
This should help. Keep in mind that before you send it to microsoft (or appHub) your app needs to be fairly perfect. Submissions aren't free :)
edit: this is assuming you were asking how to submit it for review. When you submit your app, the review process starts.
For app testing you need the sdk... With the sdk you have a perfect emulator for test your apps. For app deploy on your device, after you've bougth the annual subscription to be a developer, you have to associate your phone and install zune on your pc (read here).
After you tests you can submit your app through this process (read here).