IoT – Internet of Things
IoT or the Internet of Things is growing huge today. It’s comfortable and convenient to end-users hence people are already addicted to the comfort they are receiving from smart devices. Every single industry from household to healthcare are adopting IoT into their business model.
Number of IoT devices grows by the minute hence new challenges in software testing are emerging as well: complexity, security, privacy rapidly growing demand and user expectations – those things will determine new QA standards and will bring in a hell lot of trouble shortly. Focusing on quality is the only way of leading a business to success today. It’s just that users don’t care why your software failed and don’t care whose fault was it, your apps or their TV set’s. Get where this is headed?
So are there any key challenges or any new things you should watch out for? Are there changes in good old tricks you are already used to? Let’s just see.
Unite tests as we all know are testing a particular piece of the application like a function or a class, etc. The rest is mocked or simulated and Unite Tests are usually automated. What does IoT add to Unit Tests? Physical I/O would be the first challenge. I/O environment interactions are extremely difficult to simulate in an efficient manner. Surely appropriate simulating hardware is often provided, though there are times when running tests on real devices is the only option.
And one more thing: automating Unit Tests is a pain. Well building unit tests is not hard however automating the process of test execution, loading and receiving results may be hence not all IDEs are supporting scripting. And even if they do it’s not always well documented.
It may seem System tests should go smoother than Unit tests hence a complete system is available. However this delivers new challenges:
- The system may be huge
- The system may be covering a large geographical area
- The system may be designed for operating in harsh environments
That’s when FATs come in handy.
Integration is done after unit tests. Several components are stuck together to make sure they work well and functionality is not damaged. This means you will be facing the same challenges you have been through while Unit Testing sessions. Surely as more modules are combined things get easier, though the hardware issue never leaves you.
This is the primary threat as more tech connected with each other and with access to internet makes it significantly harder to determine possible entry points hackers will be using. You probably are aware what that means, right?