This is part 2 of this article discussing the reasons why you should test your app or website on multiple browser configurations. Today we continue with browser functionality and the differences between devices.
How your product functions on different browsers
Ideally, the way your product functions would be the same on all browsers and operating systems. However this is often not the case, and is another scenario in testing where the end user experience needs to be taken into account when writing test plans.
Your site or app’s functionality will affect which parts the software tester will check for bugs. If you are launching an ecommerce website for example, then the software driving the shopping cart and payment section is of highest priority, as it is where visitors convert into customers. Therefore you would need to perform end-to-end testing, mimicking the process a user would go through to make sure everything works as it should. The purchase information displayed to the customer needs to be accurate, their payment details secure, and the billing correct. Anything less, and you damage your reputation as well as invite potential legal ramifications.
Don’t forget devices: desktop, tablet, mobile
Before the age of mobile, desktops ruled. Now, screens sizes are fluctuating, the number of devices available to users is rising as new products enter the market, and multi-platform Internet usage is the norm. When choosing browser configurations for your test plan, consider which devices the majority of your site or application’s traffic is coming from. You can analyse these trends on Google Analytics, which tracks and stores this data for you.
In particular, look out for the rise of mobile devices, especially when it comes to ecommerce. Mobile has overtaken desktop as the top traffic source for ecommerce websites in the past year, and a study by Demandware predicts that this share will rise to 60% by the end of this year. If you wish to test the performance capabilities of your ecommerce site or app, ensuring that it is optimised for browsers hosted by smartphones is absolutely vital.
Emulators or physical devices?
In addition, we observe that testing software on physical devices produces a more accurate result than using an emulator. Emulators allow for greater convenience, but testing on real devices provides a more reliable picture of real-time bugs that users may encounter. Using real devices reduces the risk of high-impact bugs slipping through, ruining a developer’s hard work and your end user’s experience. If you don’t have access to a test lab with all the devices you need, we can help you as have one available for use.
Whilst it is impossible to find every bug, testing your website or app as though you were an end user greatly reduces the risk of impactful bugs appearing when your site or app goes live. Testing your software helps to protect your reputation as a brand.
• Is your website cross browser friendly?, Testing Whiz, October 23, 2013
• Strategies for carrying out – Gotta test ’em all?, Mozilla, last updated July 9, 2017 [at time of writing]
• Dave Chaffrey, Mobile Marketing Statistics compilation, Smart Insights, March 1, 2017
• Declan Harty, Smartphones Overtake Computers as Top E-Commerce Traffic Source, Bloomberg, July 25, 2016