I ran into this question recently while helping a friend test firmware for a small smart device. I usually work with web applications, where testing means spinning up a staging server, running automated tests, and checking things in the browser. But with embedded software, it felt completely different. We had to deal with physical hardware, limited debugging tools, and situations where the device would just freeze without clear logs. It made me realize that testing embedded systems must come with its own serious challenges. So I’m wondering, what are the toughest aspects when comparing embedded testing to testing regular desktop or web applications?
