Comments by "TheEvertw" (@TheEvertw) on "5 Steps To Fast u0026 Reliable Software Development" video.

  1.  @almari3954  Or use a language like Rust...
    1
  2. It can. In several ways. I have personally used: * Hardware in the Loop testing, where a hardware setup is dedicated to running automated acceptance tests. The setup most include ways to update the firmware, vary the conditions in which it runs (load, variations in supply voltage, etc) and measure behaviour. All under automation. Obviously, these tests take time and are thus only applicable for the acceptance phase. * Automated tests with simulated IO. By mocking the low-level hardware of the micro controllers, the higher levels of code can be exhaustively tested automatically as part of the commit cycle. These tests can be run on several levels, from integration to module tests. I have been doing this since 1999 in C++ for 16-bit micro controllers. * unit testing higher-level modules etc. The only thing you can't do is deploying the accepted firmware to actual controllers in the field. Well, you probably could, but I don't think you should. But you can e.g. automatically deploy the updated firmware to a website for download by customers & field engineers.
    1