> This is a huge disparity from web development workflows where file watchers are prevalent—you save a file and instantly see the results of the change.<p>> Pigweed’s pw_watch module solves this inefficiency directly, providing a watcher that automatically invokes a build when a file is saved, and also runs the specific tests affected by the code changes. This drastically reduces the edit-compile-flash-test cycle for changes.<p>Eh, no thanks. Web dev environments can get away with this because the turnaround time is so quick, but even a medium sized embedded C++ project can easily take minutes to build, plus 30+ seconds to download, even with a debugger.<p>Please don't try to bring webdev workflows into the embedded space. This isn't javascript.
Correct me if I'm wrong, but this seems to run unit tests on the embedded target. Why?<p>In the embedded space I've found unit tests to mostly be useful for testing logic and algorithms but not terribly useful for testing hardware integration, which is where all the really painful and tedious problems happen. If the unit test passes on the board but fails on your host it's likely due to a compiler bug or a bug in the MCU, and you usually just work around those.<p>What would be more interesting is creating an environment to support manual and automated integration and system-level testing. I haven't seen such a system in practice because such systems require a very lengthy and painful characterization of the system under test. They also require hardware support, meaning a tool needs to be integrated with the software to interface with and measure the output of the system under test. These can range from simple I2c-based GPIO expanders for monitoring and controlling IO lines to pressure and flow meters for pneumatic measurements, or current probes for instantaneous and aggregate power draw measurements. This is more like laboratory automation so I think a lot of software people try to avoid doing these things.<p>Do you have any plans to implement APIs that might enable development of such a system in the future?
When I saw this, I thought Google was making a vendor-independent HAL and I got excited.<p>But it looks like it's just a set of small plug-ins like statically-allocated strings and easy tests.<p>I guess that's cool too, but...eh. I agree with others who say that it seems counterproductive to try to run embedded integration tests every time a file is saved. This sort of looks like a solution in search of a problem.<p>Also, when has Google ever supported a novel project like this over the long term? I'm not too eager to buy into something that'll get discontinued a few years down the line.
I'm just starting to wrap my head around embedded development but what kind of audience is this aimed at?<p>Is it bare-metal embedded developers? Can it work with yocto or buildroot for those who rely on deploying linux on embedded?