Course code: VIAVI-2
Years with company:
Primary programming language:
Other programming languages:
Unit test harnesses:
I would prefer not to
Test practice now:
We have Overnight regression tests, but code/feature coverage is very patchy, and bugs frequently get through to released code.
Test are normally only run on main branch, so bugs are often not detected until after code is merged this makes re-working code to fix things slow and difficult.
Module level testing often tests functions in a way that is not representative of the way they are used in released code.
Often a lot of testing done by the developer does not end up in regression tests
Under 10 seconds
We have a company C/C++ coding standard that defines naming conventions and gives guidance on how to structure code. It is not always followed by our team.
We do not have a coding standard for Matlab (We try to put headers on files/functions)
Function too long:
Not sure :- If the function can be broken into sub functions in a logical way then it probably should be, as this will make the code easier to understand
We carry out code reviews when anyone merges code onto the master branch. It is often difficult for the people reviewing the code to understand the feature (or the code)
Favorite thing about dev:
Developing algorithms, problem solving, simplifying complicated things, elegant solutions.
Least favorite thing about dev:
Unclear requirements. Focus on (narrow) features rather than quality/efficiency/ maintainability of code, working to deadlines.
Why are you attending:
To learn about TDD.
I am hoping TDD might help with the following:
More rigorous testing of code.
Making re-factoring/optimization of code easier.