Book Review – “Jasmine Cookbook”

I have been involved in doing evaluation of a lot of tools and frameworks to suite the day to day project and client needs. Recently did a research on “Jasmine” to validate and check it’s implementation feasibility for BDD when I hit “Jasmine Cookbook“.

I was quite intrigued when I received this book written by Munish Sethi, as it provides practical ways how a novice can actually learn Jasmine quickly and easily. So, is it a ideal reference book for a product team to get handson on Jasmine quickly?

In short: Yes. It acts as a great reference for the teams who want to implement Jasmine for their products. More importantly it acts as a quick reference for anyone who wants to begin with Jasmine.

This book is divided into 9 logical chapters with each chapter focusing on a particular need that any team might be having at any particular phase of a SDLC i.e. from evaluation phase till actual implementation and measurement phase. Some of the key focus areas that the writer has brought out very clearly are

  1. How Jasmine can be implemented in teams following either TDD or BDD. It becomes easy for the user to understand and implement it in the projects thereafter.
  2. All examples relate to the real world scenarios a layman might get into, hence, makes them easy to understand
  3. Provides a detailed step by step approach to write your own custom “equality” and “matcher” functions in Jasmine
  4. Performing mocking using spyOn() method, Asynchronous operations and  Implementation of Fixtures and manipulation of DOM with Jasmine tests is explained in detail.
  5. Includes practical usage and designing of Jasmine based automated tests to validate complex functionality developed using AJAX, jQuery, JSON Fixtures
  6. Apart from the automated tests, it also includes methodologies to validate the code coverage achieved through the automated tests using JavaScript Code Coverage tool Karma and Istanbul that can enable product teams to keep a check on what they are testing.

Towards the end, Jasmine integration and usage with other tools like Angular JS, Node.js and CoffeeScript is touched upon. Though these could have been detailed further, but it gives a platform to quickly start in case there is a need for these technologies. But, overall the book is a great guide for a product team to take small steps to learn and implement Jasmine as per their needs.

Internet of Things: iBeacon and it’s adoption in Travel

As technology advances, organizations are feeling the need to be more and more connected with the customer to increase user experience. Apart from user experience, they also want to keep a track on the customer habits so as to utilize them for targeted marketing. With this aim in mind, there is a lot of innovation happening and “iBeacon” is one of them. There are lot more Beacons being developed by many companies for both iOS and Android, but to keep it simple, we will focus on iBeacon for now.

What is an iBeacon?

iBeaconiBeacon, as the name contains an ‘i’, definitely is developed by Apple. It is a Bluetooth low energy (BLE) device, that is specifically designed to connect iOS devices, to provide a location based information and services. It enables apps on iOS7+ based smartphones and tablets to connect and perform actions when they come in close proximity to an installed iBeacon. How does it work? iBeacon works along with a customized app on your iOS  device, specifically designed and developed to listen to the signals being broadcasted by iBeacon. An iBeacon categorizes the broadcast based on whether the user has entered, exited, or lingered in the region where iBeacon is installed. Apple has categorized the distance between iBeacon and receiving iOS device into 3 distinct ranges:

  • Immediate – Within a few centimetres
  • Near – Within a couple of meters
  • Far – Greater than 10 meters

Based on the distance between iBeacon and actual devices, apps can be instructed to perform different actions on the user devices. As per wiki, iBeacon can be configured as below

iBeacons come with predefined settings and several of them can be changed by the developer. Amongst others the rate and the transmit power can be changed as well as the Major and Minor values. The Major and Minor values are settings which can be used if you want to connect to specific iBeacons or if you want to work with more than one iBeacon at the same time. Typically, multiple iBeacon deployment at a venue will share the same UUID, and use the major and minor pairs to segment and distinguish subspaces within the venue. You can for example set the Major values of all the iBeacons in a specific store to the same value and use the Minor value to identify a specific iBeacon within the store.

How can iBeacons be useful for Organizations and individuals? There are various ways travel and transportation industry can use iBeacons to improve user experience. Some of the real world use cases can be

  • Hotels can implement iBeacons in premises to provide indoor mapping. In case of any emergency, guests can be guided to a safe place.
  • While visiting an airport, iBeacons paired with an app can keep a track of your movement within the airport. The app can guide you to the right direction based on your boarding pass.
  • You are a very frequent traveller with an airlines. As you approach to the checkin counter, the Agent receives an alert with your image, name and status level. (S)He signals you and calls you by name to invite you to help you in checkin quickly.
  • If your tagged baggage comes within iBeacon threshold configured in your app as it arrives on the airport, alert is triggered on your phone and you can take your baggage without looking at tags of other suitcases.

These are just few use cases, but industry is aggressively waking up with the plans to utilize iBeacons to get more connected to the consumers and improve customer satisfaction. As per SITA Labs iBeacon technology has a great potential to trigger better passenger experiences in airline and airport apps“. Virgin Atlantic has started trials to improve Upper Class passengers experience at Heathrow airport using this technology. It would be good to wait and watch and see how industry finds more and more uses of this technology! Not only Apple, but there are lots of other companies that want to evolve this technology further and are involved in developing BLE enabled beacons. Some of them are

  • PayPal
  • Qualcomm
  • Estimote
  • Swirl
  • GPShopper
  • Accent Systems
  • April Brother
  • BlueSense
  • Gimbal Series 10
  • Glimworm
  • Kstechnologies
  • Minew
  • Radius Networks
  • RECO
  • RedBear Lab
  • Roximity
  • Sensorberg
  • Sensortag
  • Todally

In this blog the focus was more to understand the iBeacon. In the next blog, I will start with the testing part of iBeacons and it’s surrounding apps and will try to uncover some of the nice to know things for the testing world :).

Stay Tuned!

7 Tips to screw any Test Automation Initiative

Companies often spend a lot on performing test automation to reduce the efforts spent by testing team. We read a lot about how to make the automation projects successful, but, have you ever thought on how you can achieve it otherwise. If you are one who want to make any of the automation initiatives unsuccessful, do proceed reading further.

Don’t involve team during planning

Planning is not important. Just tell people what areas they will work and they will deliver. This will ensure that people are spending time in delivering what they are asked to do without putting their brains behind.

Select tool based on team knowledge

Irrespective of the technology used by the application, use the tool that the team members assigned to the project knows. Don’t waste time on hiring or updating the skill sets of people.

Estimate based on your scripting speed

Don’t consider test case complexity/team skill sets/learning curve/hiring time etc while estimating the efforts. Just estimate based on how much you alone will be able to achieve.

Automate areas having high probability of changes, first

Consider that the critical areas from the point of testing are the ones that are getting changed in every build. Start automating them first. This will ensure that the team spends the time on maintenance rather than new development.

Freeze the build for the complete duration of project

Before starting the project, be strict on not changing any product build, irrespective of releases made to the testing team in between. Just make your scripts compatible with the initial version of the build provided to you. This will ensure that your scripts do not run on the latest build and hence will help in failing the UAT.

Avoid any communication with stakeholders

Stakeholders always ask for reports that often decreases the productivity. They also do not have any rights to get information on the challenges that the team is facing. If you want to fail miserably, it is seriously advised not to tell stakeholders anything about the project before the final delivery.

Keep Script integration at low priority

Do not estimate for script integration and do not even care for it. If time permits, then do it immediately before UAT so as to ensure there is enough evidence of script not working.

In case you have any other tip, request you to share it in comments and I will add it up in the upcoming post.

Automation – Shall I invest in building dedicated team?

There are many instances where it has been seen that organizations complain of not getting enough ROI from their automation initiatives. When they get to identify this, the blame game starts and people start pin pointing the test automation team for not creating the right strategy beforehand.

One of the major issue that I have seen is that many a times people are reluctant to admit that there needs to be a dedicated effort and plan in place for automation. They feel that if they outsource the work of framework development to any third party contractor / vendor and then ask the vendor to train the current manual/business team, the job will be easy. In case of optimization of efforts, they might be correct, but they fail to understand that this will put a lot of burden on the automation solution and it might not be best designed based on product needs.

Another issue that I have seen is that the current testing team (with manual mindset) is asked to upgrade the knowledge and start the automation work in their free times. This again puts a lot of risk on the whole initiative and at last it does not work for the long term.

We all definitely need to understand that the automation is not a part time activity that can be done by part time people. It is a niche skillset that is equivalent to development. As any product success depends on a good architecture and team, automation solution is also dependent on a good framework architecture and good team.

On a high level, the automation plan / initiative should consider the following from team perspective

  1. What do we want to achieve from automation?
  2. How will we achieve it? Do we need to hire from outside or do we have experts inhouse?
  3. If we hire the complete team from outside, what will people do once automation implementation is completed?
  4. Can we hire experts using subcontracting? What is the rampup and rampdown plan?
  5. How to handle the maintenance phase?

Reusable Test Automation Framework – Do Not Trust!

In any software company, wherever you go, you find typical species of people who want to just break the software, do not want to bow down under business pressure to release low quality software and are often termed as fussy. This species is specifically termed as ‘Testers’.

Nowadays, there is a special requirement that is being given to this species. It is to automate as much as possible. This poor specie is under pressure to learn automation and implement it and behave like a developer. So what is happening? Is the automation that is being proposed or done under such pressures really worthwhile? Are the companies really getting benefits out of it?

I am seeing it a fact that reusing a framework has become a fashion nowadays. Everyone is talking about so called ‘Hybrid’ framework. Even if the application is complex and steps are repetitive, testers end up developing a keyword driven framework (which they call hybrid as well) for it. I have been confronting with these people about why they are doing so when that framework might not yield a good return in the longer run for that particular application. The answer that I get is.. I developed it in the past in one of my projects and hence it is a proven way to automate!

It seems to implement an already known framework has become a fashion in the industry. The reason is simple. No one wants to take risk and try something new or may be no one wants to understand the exact need of the application under test.

REQUEST -> Please do not treat test automation as an activity that can be based on a poor framework. The framework should be designed to fulfill the application needs and not your personal needs.

Why…Test Automation?

Spending hours in test execution is cumbersome,
Manually executing each testcase is not done.
Efforts if calculated, in this activity are huge,
Total testing time also needs to get reduce.

Test Automation is the key to this situation,
That means executing scripts again and again,
Without manual intervention.

So many tools are available in this category,
You can easily select one,
Based on your requirement and budgetary.

Record-Play and Framework are popular in automation,
Where Record-Play comes with huge maintenance,
A robust Test Framework is the final destination.

It’s me!… A BUG

When developer missed something, I was born.
When developer fixed something, I was born.
When reviewer neglected something, I was born.
And when functionality does nothing, I was born.

I was born with so many types…
At times I am critical, at times I am time-pass.
I was in disguise and could not be caught,
Until a tester finds me and I was just draught.

Though I was the same but now got a status and a name,
I am lying at developer’s task queue,
I know I will either die or grow.
But if I live, I make everyone sway.