Course code: WEB-31
Years with company:
Primary programming language:
Other programming languages:
Unit test harnesses:
(In the past) a proprietary, eclipse based framework for embedded C++ (I guess derived from JUnit).
Microsoft Visual Studio build in Unit Testing Framework.
Software development is my passion. In the past, I brought up serial codes for commercial products within an international development environment.
Nowadays I am working together with many external partners.
Test practice now:
We try to set up different stages:
1. Unit tests (e.g. Microsoft Visual Studio Unit testing - but not all projects are covered, yet)
2. Integration tests - right now executed manually we distinguish between stress tests, fault injection, boundary value, and error guessing. Jenkins CI is planned here in the future.
3. Acceptance tests - Finally we have a test report which we can hand (together with the system) to uninvolved people (e.g. Product managers)
Depends on the project - most likely a 32 bit ARM Cortex Mx processor.
Microsoft Visual Studio
Microsoft Visual Studio Code
Eclipse based environment
We are about to integrate the MISRA coding standards, checked by PC-lint (an ongoing process).
Function too long:
It does not fit on one screen. (Use a commercially available screen resolution ;))
The external partners have a 4 eye principle. We applied a rule to our DevOps environment. For critical features, there is an additional review.
Favorite thing about dev:
To see the physical interaction between the real world and our system at the end of the day.
Least favorite thing about dev:
The tingle when a new release goes into serial production - bear in mind that software is always faulty.
To be honest - not that much yet. I guess I heard about that in theory - but I've never seen a project developed under tdd in practice.
Why are you attending:
The development lead from our daughter division asked me to participate in the course. But I am really happy and keen to learn more about tdd.