LifeLine Response Reduces Manual Testing Time Ten-Fold

LifeLine Response is a personal protection app that calls 911 when you trigger an alarm. LifeLine Response uses the GPS information on your smartphone to provide emergency responders your exact location and personal identifying information in order to provide you the fastest and most accurate assistance possible.

When Giacomo Listi, CIO of LifeLine Response, got in touch with testmunk, their life-saving application was being tested purely manually. This meant that the organization kept several devices on hand and manually tested key changes on each device in turn.

Mr. Giacomo Listi, CIO

LifeLine Response faced the following core issues:

• Manual testing on multiple devices took an exceedingly longer time to accomplish – often several days
• Release dates would be postponed because of unexpected bugs and new regressions
• Lack of resources to perform adequate manual testing
• Lack of a formal testing process
• A small but growing number of user complaints due to bugs

The Testcase Overview

The first undertaking for test automation of any new app through testmunk is to set up a testcase overview. Lifeline was no exception, and we proceeded to determine what needed to be tested overall as part of a given release. In order to get this baseline in place, we arranged a 45 min conference call with Giacomo to walk us through some of the testing procedures that he and his team had recently gone through.

In particular, we focused on the following questions:

• What are the top 10 most important use cases for LifeLine?
• Where have you seen predominantly seen regressions / bugs in the past?

Prior to the session, one of testmunk’s automation engineers had obtained the app and installed it on his phone. This allowed us to follow along as Giacomo walked us through the app. Based on Giacomo’s walkthrough, our engineers experience with the app itself, and several questions, we took copious notes, which were later were transformed into the testcase plan below.

Within less than 24 hours Giacomo received this testcase overview that listed the key use cases identified in our meeting. The testcase plan was designed for dual functionality, acting as a status document, indicating which testcases were ready for immediate automation by marking them as “Done.”

The results were as follows...

READ MORE