Test Management and Snow Ball effect of “Agile Development”

Most of us have been exposed to project that never follows actual project plan; the changes can be new features, new add-ons, defect fixes or new integrations. For every test manager these projects take a snow-ball effect, that is they keep on growing along the way, and you are never sure what to expect from them. And to make the mater worse more rapid the changes or defect fix, lesser the duration between the builds. But the area to test keeps on increasing. Another factor to consider is the trend of software development companies to “fall” in to Agile Development, where they “think” everything must be parallel.

Now what it do to test managers is very scary, you cannot get the automation kick in, as application is being updated regularly, you cannot add more resources, as “You don’t need more resources, you already have got it tested”, while if they do not get it all tested, you get to hear, “Mr. what are you doing, look there is very important bug your team missed”.

To tackle all this I have made my policy that for a project that is behaving like this (let’s say every new build is within less than two weeks of other) I usually deploy two resources; both resources do test new features for first week. For next week depending upon the available time, needs to change test cases, I on daily basis try to cast a net on areas that are near to new features, where one resource test the application, and other update the test data and test cases for next build.

And for last couple of days before the next build, we do a strategic exploration of application, which is for every build we select one or two modules and do exploration for the application.

This is not the ultimate test management process, but honestly since the advent so called agile development, and lack of cohesion between builds and marketing team’s insistence of new build every other day; this is the best I could devise in 5 years of my test management.

Industrial Mobile Application Testing

Introduction

Mobile applications still have a largely horizontal character, but new developments and capabilities are beginning to show how certain vertical markets can gain unique business benefits from mobility. The growth of mobility-enabled applications is driven essentially by the same factors that are driving IT and business process change, namely the need to be more responsive, optimize the efficiency of staff resources, and shorten the cycle time of key processes throughout their value chain.

Another driver of industry-specific mobile application adoption is the evolution of the technology, including the development of platforms such as the Research in Motion, Android, Windows Mobile and iOS, whose feature enables the extension of enterprise applications to mobile employees as well as improvements in security and the availability of applications from major ISVs.

Defining Industry Oriented Mobile Applications

The key distinction of Industry Mobile Applications is that they facilitate one or two major processes of industry instead of whole application. So set of similar stakeholders are given a similar applications. Some are transactional and order-entry component, while other might contain only the results and graphs, some required advanced content validation and verification others help in remote data manipulation.

All this is because industry is taking a turn where need for

  • More responsiveness to their customers
  • More facilitation of collaboration, operations and management environment
  • Optimization of efficiency
  • Shorten the cycle of key processes
  • Availability of information on the go

Challenges in Mobile App Testing

It’s been clear for a while that mobile devices are the current market players, even more so that some experts have been counting on them to take over the PCs and Desktops in near future. But as with any emerging technology, developing and implementing mobile applications can pose a number of unique challenges.

Mobile applications, although have limited computing resources, are often built to be as agile and reliable as PC-based applications. In order to meet the challenge, mobile application testing has evolved as a separate stream of testing.

By missing the major user characterizations, mobile application lose the “gloss” within first couple of months and therefore, user retention period for mobile applications is very low, only around 10% users are found still using the same mobile application after six months of its download.

Mobile application user retention over period

Many people have pointed fingers at many aspects and loop holes in Mobile App Testing, some of which are mentioned below.

  1. The major challenge in Mobile App Testing is the multiplicity of mobile devices with different capabilities, features and restrictions. Devices may have different technical capabilities such as amount of available memory, screen resolution, screen orientation and size of the display, network connectivity options, support for different standards and interfaces.
  2. Many mobile solutions involve a significant hardware element in addition to the PDA, such as scanners, mobile telephony, GPS and position based devices, telemetry, etc… These extra hardware elements place additional demands on the tester, particularly in terms of isolating a bug to hardware or software.
  3. Mobile applications are often intended to be used by people with no technical or IT background; such as meter readers, milkmen, insurance sales people; on devices that have small screens, and no or awkward keyboards. Good usability testing, carried out in conjunction with key users, in their own environment, is essential.
  4. There are multiple operating systems that are prevalent in the mobile space like Symbian, Android, iPhone OS, Windows, Linux, Blackberry OS, palm OS, Brew, etc. Each of the operating systems can have further versions for different types of devices which makes platform testing complex and further challenging
  5. Another challenge is that the developers need to focus on developing applications that are easy to use on a mobile and consume less power.

The Most important aspect that our analysis, development and testing teams often miss is that mobile application development takes a lot less time duration then mobile application testing, compared to the conventional model where application analysis & development takes more time precedence over testing. We therefore, deliberately tend to give less time for testing which might result in the application starting to lose out to competition over time. Due to this misunderstanding and thus improper testing strategy in mobile application; growing number of mobile applications are being taken off-app store every month, just in September 2011 alone following stats were witnessed

Percentage of applications taken off the stores

These trends show, that we can never use the same testing methodologies as we have been using on the conventional web and desktop applications, we have to devise a new strategy and methodology, which is going to take into account what actually is the mobile world, what it constitutes of and the adjustments it calls for in our conventional testing patterns and strategies.

Translate »