5 misconceptions about the mobile application test to absolutely forget

by bold-lichterman

Imagine: you barely walk out of a store with your purchase and you realize it’s broken. You return to the store to make a complaint or an exchange, right? Why is quality mandatory for a “classic” consumer product but not for a digital product? Why are “damaged” mobile applications tolerated?

And yet, we read it every day in the press: the French are spending more and more time on their smartphone, the majority of 20/35 year olds exceeding 2 hours per day. The smartphone is no longer an accessory, it has become essential and the appetite of users for quality digital products is exponential.

In 2015, m-commerce sales are expected to increase 24%, the French market being one of the most important in Europe. Users want what is easier and more intuitive, they want to be able to make their purchases on smartphone or tablet or desktop without having to wonder about the omni-channel strategy adopted (or not) by their merchants. !

In constant progression, m-commerce represents only 7% of online sales: this low percentage is explained above all by the frustration experienced by consumers during the purchase journey on mobile. Why the frustration? Most often because the application crashes: 70% uninstall an unstable application after a single use, which makes the crash the most prohibitive bug. Many other anomalies alter the digital experience of users. It is therefore imperative that they feel confident when using an application, hence the importance of testing, guaranteeing quality, unfortunately too often underestimated or misunderstood.

Let’s take a look at some preconceptions that detract from the test:

  • The mobile application test is time consuming and expensive, “We will test if we have the time”, “this remains a good practice”, we hear very often. However, if it is integrated as early as possible in the development of the project, the test will be more efficient, less expensive and will bring good results.
  • Users will report bugs to you. Certainly, some users will give you feedback, but your users are not testers. They don’t have the tools or the expertise to do it, they just want to use your product.
  • The developers test and debug what they have designed, this is enough to guarantee the quality of the App. Please note, developers are not Quality experts: they lack an objective view of their developments and the ability to put themselves in the shoes of the end user. Above all, user testing is not their job. Only experienced testers will be able to give quantitative (list of bugs) and qualitative (user feedback) feedback on a project in development.
  • A successful test on one device ensures that the application works on all other devices of the same OS. False, given the fragmentation of the current digital environment (screen sizes, resolutions, OS versions), the risks are all the more important. Testing on a wide variety of devices is not a plus, it’s mandatory.
  • Mobile app testing is like website testing. Still false: it must be treated differently due to the specificities of mobility: submission, installation, performance, connection (WiFi, 3G / 4G), interruptions (call, message), ergonomics, memory, multi-devices (smartphone, tablet , phablet) …

Anticipating, defining and organizing a testing strategy before launching a mobile application is vital. Not taking Quality Assurance into account correctly, or doing it in a hurry, is not to take into account what is really at stake: a loss of user confidence, a degradation of the brand image , loss of income. The benefit of a structured QA far outweighs the cost of its implementation. The longer we wait to correct the bug, the more it costs! In short, prevention is better than cure.

Seat : Marseilles

Creation date : 2011

Workforce : 52 employees

Founder : François Joseph Viallon

The site StarDust

[Contenu proposé par StarDust]