Course code:
WEB-34
Years with company:
2
Years programming:
9
Primary programming language:
C#
Other programming languages:
VB
Unit test harnesses:
Visual Studio
Something else:
I lead a group of SW engineers who are in charge of SW regression testing ( on application side). Hence my strong interest to understand TDD philosophy/methodology. I don't have any embedded background.
Test practice now:
Since we ( my team ) are not developers we don't deal with unit testing. We design and implement regression testing using frameworks such as Selenium, FitNesse
Target system:
Windows. Android
Dev tools:
Visual Studio
Build time:
1-5 minutes
Coding standard:
I am not trained as a SW engineer and picked up coding throughout my career. I simply follow guidelines established by our department and am by no means an authority on this spcace. I do get help from my senior staff members during code review.
Function too long:
Generally a function should perform one thing only. It should be written to perform a specific task and be easily understood by human reader.
Code reviews:
Mostly I am concerned with use cases and how best we are covering them as oppose to coding standards. I leave that to my senior SW team members
Code time:
20
Test time:
30
Debug time:
50
Favorite thing about dev:
As soon as you hit build, you have a product!!
I am trained as EE and to realize a product it often takes months and you are dependant on multitude of disciplines such as fab houses.
Least favorite thing about dev:
Too many languages around :)
Tdd knowledge:
Just basic terminology.
Why are you attending:
Since my team role is testing the application and ensuring quality, I really want to understand TDD, its benefits, and how we as a department ( SW developers) can employ it to write more purposeful and higher quality code.