One comment about remote testing. The IPv6 test equipment should be connected to the system(s)-under-test by a L2 network. Using a router can prevent some of the malformed packets from making it to the system under test.
This article lets me see that testing can be done with different tools but nowadays seem to be concentrating in using some kind of scripting language for automating tests. Also its necessary to use source code management to handle the set of scripts and an issue tracking system to follow up on bugs. But most importantly, a good test management system which simplifies and orders the test plan and execution. It also eases the reporting tasks. I once worked without a test management system and yikes... it sucks! Mostly at the time of gathering the results and preparing a report.
Ideally all these systems should be linked so that if there's a failure or bug found in a certain test case, the test plan should link with the issue tracking system where a bug for that defect should reside. Prove of the failure in the form of log files should also be linked with the bug and the issue tracking system. Ideally perhaps through good old fashion hyperlinks. Testing is good when you have the right tools!
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.