Please enable JavaScript.
Coggle requires JavaScript to display documents.
IOT測試 (Connectivity (The system has to be available all the time and…
IOT測試
Connectivity
The system has to be available all the time and should have seamless connectivity with the stakeholders.
Connectivity, transfer of data, receiving job tasks from the devices should be seamless when the connection is UP and running.
The other condition is the connection down scenario. Doesn’t matter how robust is the system and the network, there are chances that the system will go offline. Being a tester, we should test the offline conditions as well.
Once the system is not available on the network, there has to be an alert which can prompt the physicians so that they can start to monitor the health conditions manually not depending on the system till it is up.
Once the system comes online, all that data should get propagated.
there has to be a mechanism in the system which can store all the data in it during the offline period.
-
Usability
-
The medical healthcare tracking device used should be portable enough to be moved into different segments of the medical.
The equipment should be smart enough to push not only the notifications but also the error messages, warnings etc.
The system should have an option to log all the events to provide clarity to the end users. If it is not capable of doing that, the system should push those as well to a database to store it.
The notifications should be shown and handling of the display should be done properly in the devices [computers/mobile devices].
Usability in terms of displaying data, processing data, pushing job tasks from the devices should be tested thoroughly.
Performance
When we are talking about a system for a healthcare domain, we need to make sure the system is scalable enough for the whole hospital.
When the testing is carried out, it is done for 2-10 patients at a time and the data is propagated to 10-20 devices.
When the whole hospital is connected and 180-200 patients are connected to the system, the data that is propagated is much bigger than the tested data.
As testers, we need to make sure the system performs the same even though the added data is propagated.
We should also test the monitoring utility to display the system usage, power usage, temperature etc.
IoT Security
IoT Security challenges: IoT is data centric where all the devices/system connected operate based on the data that is available.
When it comes to the data flow between devices, there is always a chance that the data can be accessed or read when getting transferred.
From a testing standpoint, we need to check if the data is protected/encrypted when getting transferred from one device to the other.
Wherever, there is an UI, we need to make sure there is a password protection on it.
Compatibility Testing
Looking at the complex architecture of an IoT system, compatibility testing is a must.
Testing items such as, multiple operating system versions, browser types and respective versions, generations of devices, communication modes [For e.g. Bluetooth 2.0, 3.0] is necessary for IoT compatibility testing.
Pilot Testing
During pilot testing, the system is exposed to a limited number of users in the real field. They use the application and give feedbacks on the system.
Only testing in Lab makes sure the product/system works fine. But, this may backfire badly when exposed to real-time conditions/steps/scenarios.
Regulatory Testing
It is a better practice to get the regulatory requirements in the starting of the development cycle itself. The same should be made part of the testing checklist.
This being a healthcare system needs to pass through multiple regulatory/compliance checkpoints.
By doing that, we make sure the product is certified for the regulatory checklist as well.
Upgrade testing
IoT is a combination of multiple protocols, devices, operating systems, firmware, hardware, networking layers etc.
When an upgrade is performed, be it for the system or for any of the involved items as stated above, thorough regression testing should be carried out/strategy should be adopted so as overcome upgrade related issues.
IoT Testing Tools
Software
Tcpdump: This does a similar job that of the Wireshark except, this does not have a GUI. This is a command line based utility which helps the user in displaying the TCP/IP and other packets that are transmitted or received over a network.
Wireshark: This is an Open source application used to monitor the traffic in the interface, source/destination host addresses etc.
Hardware
JTAG Dongle: This is similar to a debugger in PC applications. This helps in debugging the target platform code and show variable step by step.
Digital Storage Oscilloscope: This is used to check various events with time stamps, glitches in power supply, signal integrity check.
Software Defined Radio: This is used to emulate receiver and transmitter for a large range of wireless gateways.