TechBlog:Stay up-to-date on the various technical aspects of IoT developing.

Welcome to the fourth part of our “embedded testing” series. From our former blogposts, you are now familiar with PlatformIO and its powerful features like unit testing and remote controlling.

A lot of iteration speed within web development comes from Continuous Integration & Testing pipelines – Services that completely automate build and testing processes, as well as deployment of software artifacts to servers. It would be nice to have something comparable for the world of IoT as well.

With the help of the this little post, you will be able to do that!

In the previous parts of this blog post series we’ve been looking into unit testing of IoT devices, using PlatformIO and its test capabilities. This blog post is going to be about how to get Remote up and running.

In the first post of this series we’ve been looking into architecture styles and explored both centralized and decentralized application architectures, and highlighted the differences between those and a truly distributed application architecture. Both decentralized and distributed architectures are really interested within the domain of IoT, because the projected fleet of billions of devices will probably be communicating in these ways. That’s a good reason to explore this a bit more.

In our first part of this testing series we outlined how to set up unit test cases for an embedded project using PlatformIO’s testing capabilities. Our first test cases have been running on the native platform, that is, a developer notebook or a CI server. Now we’re going to look at bringing test code onto devices.