Mobile Device Testing: Top 5 Testing Tips

Properly testing your mobile devices before any app releases, new website launches or software updates is crucial to weed out the potential bugs. Bugs bug people and cost you customers, visitors and most importantly, time and money. But device testing can be incredibly time and money consuming itself!

That’s why we’ve created a list of the Top 5 Mobile Device Testing Tips so let’s get started!

  1. Do Your Research First

An ounce of prevention is worth a pound of cure. By making sure you have enough data before testing, you can significantly streamline the process.

Where do app crashes usually happen the most? Are 60% of crashes on say the Checkout page? Or maybe they occur the most on a level 5 of your game?

What about types of devices? Are most of your app downloads on tablets or phones? What kinds of tablets and phones? Are 90% of downloads on the iPhone 6s? Or maybe the Samsung S7 Edge?

Do you want your app to target people between the ages of 18 and 24? Then you need to find out what the most common devices are for that demographic and build and test your app on those devices.

By knowing the data, you can establish starting points and priorities as well as most thoroughly testing common pain points and not wasting time on areas that do not typically have bugs.

2. Test Proportionately

After you’ve done your research, you can now spend a proportionate amount of time testing on devices based on your market share or desired market.

For example, if 70% of your app downloads are on Android devices, 25% on Apple devices and 5% on Windows devices then you should spend 70% of your testing time and budget on Android, 25% on Apple and 5% on Windows.

Easy right? By making sure you are most thorough on the devices that have the most downloads, you have a better chance of keeping more people happy. If you miss a bug on Windows devices, you’re only upsetting 5% of your customer base instead of 70%. You can fix bugs on less popular devices as you hear about them while keeping the bulk of your customers and subscribers happy.

You should further refine by device type as well as manufacturer. If 90% of the 70% of Android devices with your app are made by Samsung, then you spend your testing time proportionally there as well.

3. The Right Tools for the Job

PCIt’s important to do both manual and automated app testing and having a tool that can effectively do both makes your life a whole lot easier. Device Connect by Mobile Labs is great for mobile device testing because you can do both manual and automated testing on one machine.

Oh yeah, it’s also connected to real devices too so you can see real-world results instead of simple software that uses an emulator like Perfecto which only simulates the software. Why is that important? Because an emulator leaves out how well an app software interfaces with the hardware!

Not to mention that when it comes time for manual testing, you don’t need to hunt down people with the devices you need. Forget about BYOD testing policies!

4. Focus, Focus, Focus

Once you know where the problems are, focus on one at a time and make surgical fixes, not broad sweeping ones.

Make one code change, record the changes, then test your devices again and record the results.

Not only does this provide valuable insights into what exactly went wrong so you can prevent making the same mistake in the future, it also prevents you from over correcting and causing other issues in other areas of the software.

5. Be Scalable and Think Long Term

Building an app is exciting and it’s easy to get into the mindset of just “launch it and fix things later” but your short term monetary gains will be short lived as you spend money and resources fixing issues and losing subscribers in the long term. The less problems there are at launch, the less time you spend testing in the future.

On top of that, you want to make sure your software has a solid foundation to build on from the very beginning that can support your company goals and initiatives for years to come. If not, then you will need to start over from scratch–which will of course require you to start from scratch when it comes to your mobile device testing.

Like they say, measure twice but only cut once!

Conclusion

So what did you think of our mobile device testing tips? Are they helpful? Do you have others that you would like to share? Let us know in the comments!

Happy testing everyone!

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s