Hands On - Moto 360

Some nights ago, late, my wife and I were watching TV. While I was constantly changing channels, as I always do, I stopped in an infomercial "Paint Zoom". After 5 min watching all the stuff it can do, I turn to my wife and say "Dear, I want that" smiling she says "You always want everything, you are a marketing victim". I had to agree, I really am a victim of marketing. Since I remember I always wanted a lot of stuff, the garden hose that is like the firefighters, the "Mercury Clean" spray, and lots of other stuff.

That aside, from sometime to now, I acquired a zest for electronics and I have become an "Early adopter" mostly for Google Devices. During the last 2 years I've been one of the firsts on buying a Nexus 4 and Nexus 5 on their launch date, and I was preparing for the Nexus 6 but, not anymore, little bit expensive and the Nexus 5 is still hanging on. But, this time, I got the most new device from Motorola, the Moto 360. Bought it during the launch date and I was one of the lucky ones to get it then. These are my impressions:


Quick tip: How to install or uninstall an app in several Android devices with just one command

From my contribution in my company's blog

Recently, while working on a mobile project, I found myself spending a lot of time connecting a device, uninstalling the previous version of the Application Under Test (AUT), installing the new one, and then disconnecting the device, just to do it again on another 6 or 7 devices (I would like to talk about why it is better to test on actual devices than in a simulator, but that topic deserves its own blog post).


Parameterization or Randomization tools

In my previous post I was talking about parameterization or randomization in our tests, why is it necessary and how to add it in our tests. In this article I would like to talk about a tool that can help us achieve that, a tool that can save us a lot of tedious work.

Let's say we need to do some validation tests on a set of fields in a form that will be displayed on a page after saving them, this fields are:

  • Name
  • Lastname
  • Phone
  • Address
  • City
  • Country

We need to validate some different things like:

  • Text once saved fits the design and it doesn't overflow or overlaps anything
  • Min. allowed char.
  • Max allowed char.
  • Accented or other funky chars (á ç ñ) 
  • No numbers on Name and LastName fields
  • No letters on Phone fields

And we can go on and on and we could end up typing (and thinking about) 100 or 1000 different names, last names, phones, etc but. It wouldn't be better to have a tool that generates all that info for you?

Well, "there's an app for that". One of them is Generate Data it basically generates random data for us to use in our tests. Next I will detail how does it do it.


Back to the basics: The best browser add-ons for Quality Assurance

Originally posted on the blog of my company.

Recently, Firefox 29 was rolled out with a new redesign and, while downloading and installing it, I realized all the history Firefox and I have together. I believe the first version I installed was 2.7; since then we've been BFFs.

I've seen some browsers rise, grow, and die, like Flock (based on Firefox) and Rockmelt (based on Chrome). I have also seen others that always have been there, like Opera and Internet Explorer, but they have never been good enough.


Parameterization or Randomization

"Insanity is doing the same thing over and over again and expecting different results".

Albert Einstein

While reviewing a test script that I had setup to run daily, I found a test case had failed and decided to investigate further.  In doing so, I used a different user to run against the same script, but ran manually due to the previous user not meeting the perquisites I have defined for that script. The solution, I found, turned out to be more difficult than I had been expecting.  After trying with the different user, the script returned 3 more different errors.

While analyzing these errors, I discovered something odd.  Why would the same script return different results for two different users?  The difference, I discovered, was that my new testing user had been registered as a male, instead of my original, which was registered as a female. My script, in a nutshell, uses a test account to login to a social network to review different languages strings that appear on the site.  The string differences on this site of a male and female user are vast.  But, as it relates to my script, I noted the 3 errors as a result of using a different gender.

How can I solve this for future testing scripts?


Page 2 of 4