Course code: MEG-1

Years with company: 4

Years programming: 4

Primary programming language: C++

Other programming languages: C, matlab, python, C#

Unit test harnesses: matlab, simulink, xUnit

Something else: ...

Test practice now: I currently mostly test simulink models (from which c++ code is being generated) via matlab scripts: framework inheriting from matlab.unittest.

Target system: The system is a electrical measuring instrument which has two microcontrollers: STM32F7(GUI) and STM32L4R5 (measurement)

Dev tools: matlab/simulink, visual code, gcc (wsl on windows 10), stmcube ide

Build time: 1-5 minutes

Coding standard: It has been voted on by most firmware engineer in the team and it quite comprehensive. However, It needs to be updated for newer features of C++.

Function too long: Well, we have a recommended maximum of 50 lines for functions/methods in the coding gidelines so it's as good as a referential as any.

Code reviews: Our code review are either informal (just one reviewer without any records of any requested changes when the original work is relatively small) or done using pull request on bitbucket when the work is more substential.

Code time: 33

Test time: 33

Debug time: 33

Favorite thing about dev: I like solving problems as well as design new things. Developing software/firmware allows me to do that withing a relatively well defined scope.

Least favorite thing about dev: Having to maintain untidy code and some limitations from the tools.

Tdd knowledge: I am familiar with it using the matlab/simink framework, have put together a few tests once when writting a desktop C# program and I have maintained a few unit tests.

Why are you attending: I have bought the book (Test-Driven Development for Embedded C) a couple of years back but have not gotten around to finish it during my free time. I figured this course would give me a nudge as well as some additional perspective regarding tdd.