Course code:
UBL-1
Years with company:
5
Years programming:
37
Primary programming language:
C/C++
Other programming languages:
Python / Groovy / Arm assembly
Unit test harnesses:
ctest
Something else:
I am married, two kids and I enjoy writing embedded software, reading scifi and watching movies
Test practice now:
Depending on the problem, I work to a predefined API, create the framework and then write a test to exercise this API. Fixing as problems occur.
Or start working on a problem, developing / optimising the code and then write the test to exercise the final API, fixing as problems occur.
Target system:
multi-core ARM based modem
Dev tools:
Eclipse
Jtag debuggers
Software emulators
Build time:
5-30 minutes
Coding standard:
The coding standard is designed to
keep the code looking the same between users to reduce 'pickup' time.
reduce the number of "stupid" programming errors by making things more explicit
Function too long:
I cannot read it on a single (portrait oriented) monitor
Code reviews:
Use Jira to invite multiple interested parties to look over the changes. Typical reviews rely on trusting that the originator has passed regression tests
Code time:
50
Test time:
25
Debug time:
25
Favorite thing about dev:
The challenge of taking a problem and coming up with an elegant solution AND being given a failure case and having to triage it to the point that the problem is identified and it can be fixed.
Least favorite thing about dev:
Poor tool support
Tdd knowledge:
my understanding is that you start with a problem, write the tests, then implement the code, passing the tests as you develop.
Why are you attending:
To see if there is a way to improve my test coverage without significantly impacting on the time to run sanity checks.