Course code: HP-1

Years with company: 27

Years programming: 33

Primary programming language: C

Other programming languages: C++

Unit test harnesses: unity, cpputest

Something else: I am one of the architects of the entire system that we call 'Sirius'. I am primarily responsible for the underlying system infrastructure framework that spans across ThreadX (RTOS) and Linux (the main application OS). This includes system composition, startup, shutdown, IPCs, system memory management & performance, MFP system contention, OTA FW updates and device security. The rest of the application code relies on the framework layer to access various system services.

Test practice now: I test on a representative target using special (UDW) commands that is part of the embedded code that allows direct API access into specific modules. These commands could be run from a target shell or driven by external scripts.

Target system: ARM baed asysmmetric multi-processing system on a custom ASIC running ThreadX and Linux OS.

Dev tools: ARM gcc, git, gdb, MULTI, shell

Build time: 1-5 minutes

Coding standard: HP Sirius coding guidelines

Function too long: The number of lines do not matter as much as very intricate nesting of conditions that makes the code difficult to follow after some time

Code reviews: peer review using gerrit

Code time: 60

Test time: 20

Debug time: 20

Favorite thing about dev: New challenges that makes me eager to come to work on Monday morning.

Least favorite thing about dev: Anything that is not productive and slows me down.

Tdd knowledge: Write tests that has good code coverage. Tests are written first based on requirements before developing code. Test automation helps to keep the code healthy in the future.

Why are you attending: I hope to find some useful tools and methodologies for better test automation.