How to test embedded systems?

Question

Software testing

Hi guys,
I got into a company that develops a device, it has a lot of different settings.
The problem is that individually all the settings work, but when some unpredictable settings start, errors appear, tell me how to identify all this? Was it all supposed to be at the design level? How to organize testing of such a monster, manually sort through all possible options or programmatically disable everything in the code?? Or make a list of required tests before each release? And then after each firmware release, bugs appear where they were not there before.
With all respect, Andrew

Answer 1

• Write a (minimal) simulator to compile for the host
  
• (Optional) screw on a static analyzer
  
• Use assert wherever possible
  
• Write tests and run them on the host under valgrind
  
• If it’s difficult to simulate something, make a stand for a piece of hardware and write tests for the stand (matrix testing is supported by many things, and even if it’s not difficult to generate something)
  
• Raise CI and automatically run tests on the buildhost and stand
  
• Raise sonarqube and fix _all_ remarks
  
• (Optional) Find a controlled heat chamber and run tests in it
  

Answer 2

With a large number of input parameters, you can try using the Pairwise technique for test design. Allows you to significantly reduce the number of cases and subsequently automate them.
Creating cases manually with this technique is long and relatively difficult. There are specialized tools for this.