Course code:
WEB-3
Years with company:
0.33
Years programming:
9
Primary programming language:
C
Other programming languages:
Bash
Unit test harnesses:
PUnit
Something else:
I have been in the embedded software field for about 9 years now, but have never applied TDD in embedded software (only desktop software)
Test practice now:
Python scripts that perform component testing
Target system:
SSD firmware
Dev tools:
Confidential
Build time:
1-5 minutes
Coding standard:
Micron internal coding standard
Function too long:
When it is trying to implement more than a single well-defined job
Code reviews:
CodeCollaborator
Code time:
60
Test time:
30
Debug time:
10
Favorite thing about dev:
I like controlling hardware components...
Least favorite thing about dev:
I don't particularly like debugging (most of the time)
Tdd knowledge:
Tests are written along-with (perhaps even before) the code to be tested. The tests are run and debugged immediately as the coding is completed for a given unit of code.
Why are you attending:
1. Renew TDD concepts
2. Possibly learn how TDD could be used with hardware based systems (typically embedded systems)?