IoTMap: Testing in an IoT Environment
Testing in an IoT Environment
No matter the reason, situations occur where a connectivity stack (like Bluetooth or WiFi) is added to an existing product. A next step can be that “things” are expanded with apps that run on a multitude of platforms (let alone all versions of these platforms and different kinds of hardware!). Only adding connectivity is maybe a small growth in test activities, but adding all other elements of an IoT solution causes this to really grow exponentially! Adding a little bit of IoT to an existing product has a very big impact on the test activities related to the existing product. Where functionality was a main concern, now we add performance, security, usability, rules and regulations to the test focus.
Testing an IoT chain requires a different approach compared to regular product testing. A shift to less functional testing and more “IoT-experience-testing” is taking place in IoT testing. For example, the number of users is still unclear when releasing the new IoT product, and they can use the product as intended or differently.
Testing the IoT product will become more complicated when used in different environments, and with many possible connectivity issues. What we see happening now is:
- Testing every possible situation will therefore be practically impossible.
- We want to launch a product and have confidence in the working of new IoT features for all users.
- The need for good and automated regression testing is present from the very beginning of product development.
- IoT solutions and adding small amounts of IoT to existing products, imposes lots of new focus areas for testing such a product.
We need new test varieties to describe the test activities that belong to IoT testing. We need new test design techniques to cope with all the situations an IoT solution can encounter. There is also the need for more interaction with end users and how to involve them more (earlier) in the test process.
The TMap methodology is still valid in an IoT project. Each of these steps provides input to the creation of, for example, a Master Test Plan, Detailed Test Plan or a high-level test roadmap for a company doing IoT development.
“IoTMap – Testing in an IoT environment” gives insight in testing an Internet of Things solution.
Setting up an IoT test approach is explained in five clear steps. Using a simple IoT model, each step is described and put into IoT context. We put existing building blocks from the TMap Suite in IoT perspective and add some new ones. This book gives you all the handles you need to cope with the trend that less functional testing is asked and more “IoT-experience-testing” needs to be put in place.
Tom van de Ven, Jaap Bloem, Jean-Pascal Duniau
Auch als E-Book erhältlich!