ezeetester

Posts Tagged ‘Automation’

Are we headed towards Prediction Driven Development?

In Automation, Machine Learning, Prediction on December 2, 2016 at 12:49 pm

In a recent tweet about Sanity Testing,  I started thinking about certain Machine Learning tools in the market which seem to predict defects for various change requests submitted.

Now assuming that this defect prediction tool “actually works”,  it would become extremely useful to conduct an extended Sanity (in the least).  This would lead to major issues caused by the change requests to be resolved even before it gets to the hands of a tester, thereby saving money and time.  Changes keep happening up-to the last minute of a Product release, and this could well be another way to develop Software.

Quick Tip: Machine Learning can help improve your Customer Service

In Automation, Customer Service, Machine Learning on November 1, 2016 at 5:51 am

In an email to the customer support team of  a well known electronics company, I had asked a simple question before placing an order.  The question was, if one of their products was compatible with a specific OS.  The response from their customer support took about 4 days.  In response to it, I asked them if there were any drivers available.  The response,  “We will let you know when it’s available” took 4 more days. I had already placed an order after looking at some online posts regarding it’s compatibility.  I believe such simple queries can be addressed in their “Automated Response System”.  A typical response could be a set of recommended links (using Machine Learning) which could suggest what customers are saying, or pointing to certain solutions that have been suggested on the net.  Of course they can absolve themselves of any guarantees, if they really do not have a clue (which I doubt).  Oh! and did I mention the product worked fine without any drivers?  Please feel free to leave a comment.

Are we headed towards Image driven Automation – using Sikuli ?

In Automation on March 6, 2014 at 5:11 pm

What do you do when your application has tons of UI issues?
Apart form the other issues, regressing on the UI issues can definitely be a pain, especially the clerical stuff that involves comparing 2 images (one from your app to the one in your UI design document). So why not use a tool that can be used exclusively on interfaces? The answer is a tool called Sikuli (www.sikuli.org). Although I have just started using it, I found this tool interesting because it can capture images of GUI elements of an application on your desktop, and gives you the option of locating other elements down to the exact pixel count as might be specified in your UI document.
Additionally you could also use it to test web applications by just using the link in a slide.  For beginners in automation this could be fun, if you want to customize your tests you may have to learn Python.  We have had Data driven automation, we have had Keyword Driven automation and we are probably on our way towards Image driven automation with Sikuli and moreover its free of cost.  There are lots of cool stuff you can do with Sikuli and it’s headed in the right direction.

%d bloggers like this: