Promising a convenient life by enabling machine-to-machine and machine-to-human communication, IoT (Internet of things) technologies are fast gaining ground. In the not-too-distant future, we might see refrigerators automatically ordering items that need replenishing and cars steering us around on their own. This means designers, developers and QA engineers will have more opportunities than ever before to significantly impact the lives of millions.

There will never be enough QA engineers for testing IoT offerings, because there will be numerous layers and devices to test for functionality, interoperability, security, and more. Although a certain high level of manual testing will be required for , having more to test means that they will need to prioritize and automate whatever you can. This would increase the demand for better automation testing, leading to a rise in the number of sophisticated testing models in the connected world.

APIs connecting our connected world should be automated as much as possible because without a fully functioning API, there will simply not be connected to the Internet anymore. Creating API tests manually, based on a written description, can be time-consuming and inaccurate.

An API, typically based on JavaScript Object Notation (JSON), is often layered on top of the transport protocol. This transport layer helps interact with the device. Automation Engineers can use these protocols and APIs to automate IoT devices. The Automation framework must be able to support these protocols and APIs in order to be effective.

An IoT gateway helps connect smart IoT endpoints with sensors over cloud. With the help of the rest APIs of the IoT endpoints we have developed a test environment where all APIs are integrated with our automation framework.

In this talk, we will demonstrate how to integrate established connection between IoT endpoints and cloud server with automation environment to help teams to bring APIs into automation of IoT devices which helps in detecting reliability, functionality of IoT endpoints.

Today’s smartphone users are serious about device data and battery usage and do not want to be left in the dark about some app eating up their device battery life. Studies show that battery life is the most important feature considered by a smartphone buyer today. Google has been adding frameworks like dynamic app permissions, battery optimizations in recent Android versions to bring more transparency to end users on how apps are running on their devices.

In this era where most mobile apps (Gmail, twitter, facebook, EMM clients, Google Maps, etc) tend to offer near real time experience to users using push notifications, data sync, long polling, it’s easy for developers to err and leak unnecessary data and battery on device.

App Developers are constantly striving to design mobile applications that will have minimal impact on data and battery usage and at the same time offer a real time data sync. In this session we will talk about how we measure mobile battery and data usage using Selenium integrated with Appium, and how this helps in optimizing the Battery and Data usage.

Any app that supports a push notification or data sync typically includes a server component, which sends out commands to the client, and a client component, which runs on the device and receives, executes the commands. In our implementation we have integrated Selenium and Appium Scripts to perform actions on server and client as a continuous process, creating and sending the command from the server to the client is automated through Selenium scripts, and on receiving the command on the device, Appium scripts capture the battery and data usage before and after the command has been executed from the Application settings, this is repeated for several commands and measured, baselined and optimized.