Software Testing for esp32
Posted: Fri Jun 28, 2024 3:43 am
I had a technical doubt regarding embedded systems.
How do you do functional and coverage testing?
We surely cannot perform these 2 tests on top of a hardware because the analysis won't be provided in a report format. Only a computer can perform these 2 tests on behalf of the microcontroller and provide us with a software test report.
We can surely use a test jig but that won't be able to do coverage testing of the software.Now the problem is, functional and coverage testing cannot be done for the I2C, SPI and other hardware drivers.
3 final doubts:
1. How should we do software testing (functional and coverage)? (any MCU with C language)
2. Do we do software testing for the I2C, SPI and other h/w drivers? OR should we ignore the I2C, SPI etc drivers while doing software testing (functional & coverage)?
3. How to do software testing for ESP32?
How do you do functional and coverage testing?
We surely cannot perform these 2 tests on top of a hardware because the analysis won't be provided in a report format. Only a computer can perform these 2 tests on behalf of the microcontroller and provide us with a software test report.
We can surely use a test jig but that won't be able to do coverage testing of the software.Now the problem is, functional and coverage testing cannot be done for the I2C, SPI and other hardware drivers.
3 final doubts:
1. How should we do software testing (functional and coverage)? (any MCU with C language)
2. Do we do software testing for the I2C, SPI and other h/w drivers? OR should we ignore the I2C, SPI etc drivers while doing software testing (functional & coverage)?
3. How to do software testing for ESP32?