What Can’t be Missed While Testing Network Performance Of Wearable Gadgets

It’s like we are living in a James Bond movie

Watches that are smarter than some older computers and glasses that are displaying you a roadmap just before your very eyes are now reality. We are living in a world in which it’s OK to talk to your wrist now. And, of course those devices need application users will love. But, as always there are several issues and most of them are related to the devices size. An app needs to be well optimized in order not to eat the watches full battery charge in a couple of minutes. And there is internet connection of course.  Let’s resolve one issue at a time. For starters we will need to…

…Understand how those devices are connected to Internet

  • Connected to a smartphone via Bluetooth (often to a very specific app of the kind you may just be testing right now)
    • LG Wear
    • Samsung Gear
    • Gear Fit
    • Google Glass
      • What testing is required in this case? As for now, the devices are connected to an app installed on some Android device. Let’s begin with the easy part. There is a thing as an ARO data collector that will be tracking an apps data usage from a SIM card possessing cellular device. That has to give you a general idea of the paired device’s incurred traffic. What you are actually interested in is the packet data of the Bluetooth layer located in between the device and the gadget-wearable. Luckily KitKat and newer Android versions already have a nice built in developer option by the name of ‘Enable Bluetooth HCI snoop log’. It will lead you to a log of every single Bluetooth transaction. Copy the log to your PC, analyze it with, let’s say, Wireshark and you are almost good to go. You will also wish to check the statistics via Wireshark’s IO graph or the transferred KB will provide you with more additional info.
  • Via Wi-Fi
    • Once more, Google Glass
      • First of all you will need to ROOT the Android device to proceed with testing. Afterward you are to install ARO, set the device up as a nice little Wi-Fi hotspot and commence ARO to trace all that. Connect the wearable gadget to the hotspot and, afterwards, commence all the required tests. Easy as that.
  • Cellular Internet connection (via a SIM card)
    • There are some smart watches like Tizen that just might have a SIM card in to provide connection
      • If the device is on OS Android then ROOT it and do some usual ARO magic. Things may get trickier with non-Android devices though as there may be various limitations thus making it hard to make a general how-to.

You may as well do some automate android testing now.


TestFort Blog

About TestFort Blog

TestFort blog is an official blog of TestFort QA Lab company and is dedicated to various QA and software testing issues.


no comments yet

Be the first to comment this post!

Would you like to share your thoughts?

Software testing & QA blog by TestFort © 2017

×