| 2 |
10 |
c++ |
c, python |
gtest |
I studied Biomedical Engineering and developing embedded software for medical devices since 10 years |
gtest |
X86 & Arm A |
VS code, Cmake |
5-30 minutes |
C++17 |
currently we don't have tool. |
we do it in Bitbucket Pull request. |
30 |
30 |
40 |
- software for embedded system
- critical software
- using different features of language |
- slow deployment/testing |
only some theory |
I like to learn how to apply TDD practically |
Show
|
| 6 |
20 |
C++ |
C, python, Java |
cpp unit, gtest/gmock |
na |
gtest/gmock |
qnx/windows |
qcc
Visual Studio
git
Atlassian tool suite |
11-30 seconds |
Company has a coding standard |
Rule 1. Keep functions small Rule 2. keep functions smaller than that |
Code reviews are mandatory for every commit, several reviewers both internal and external of teams |
60 |
20 |
20 |
Its a combination of creativity, art, science, and engineering. |
It can feel like a grind sometimes |
Writing test firsts based off requirements and executing continuous test runs while developing code |
Manager suggested it and it sounds interesting to me |
Show
|
| 1.75 |
7 |
C++ |
C
Python
JS/Css/HTML
Rust
|
Gtest |
I love C++ templates/generics |
Gtest |
Real-time Linux-like OS |
VS Code
Linux
clang
coverity |
31-60 seconds |
Pretty modern, similar to Google's |
If you have to start commenting sections of the function. ~40 lines max. |
Done through bitbucket PRs |
50 |
10 |
40 |
It's fun solving problems and satisfying getting a solution |
N/A |
It's a way to layout behavior before coding functionality |
I want to see if TDD is all that it's cracked up to be (actually useful) or if it's just a buzzword. |
Show
|
| 5 |
12 |
C/C++ |
Python rarely |
Gtest |
I have a hardware background and enjoy bouldering! |
Unit and integration tests |
x86 and arm7 target nodes running an OS |
VSCode, target IDEs for smaller applications |
30-60 minutes |
C++17 |
Too many nested statements or multiple logic steps |
Deploy/test burden makes iterations a lengthy process |
40 |
30 |
30 |
Logic, organization, and being able to observe an action when something is successful |
So many options to accomplish the same thing. |
Design test first, then write code to make the test pass. |
To improve my design and test efficiency while creating robust software |
Show
|
| 7 |
45 |
QML |
c++, python, bash |
Google, others but I forget as it's been a while |
Studied Virtual Reality under Tom Defanti at University of Illinois at Chicago. |
run it on Linux laptop.
run it on robot.
run automated test framework. |
HUGO Surgical robot -- QNX and Windows x86 systems.
Linux laptops. |
VS Code.
g++, cmake, Qt tools |
1-5 minutes |
We have a pretty comprehensive c++ coding standard, but does not cover other languages. |
When it exceeds the height of the screen. |
every line of code is reviewed, often by more than one person. |
50 |
25 |
25 |
working in quiet on a cerebral problem;
automation;
solving real problems. |
In medical -- the long time it takes to develop a few lines of code. |
not much. Sounds like a good buzz phrase. |
My manager volunteered me for it. |
Show
|
| 2 |
8 |
C/C++ |
Python, Java |
Gtest |
I live in Colorado and love to snowboard |
Smoke Tests, Integration Tests, Ad-Hoc Tests, Unit Tests |
Linux and QNX OS, ARM and x86 arch |
Visual Studio |
11-30 seconds |
We have a whole document that outlines this |
When it is over 50 lines approximately and/or has too many if/else statements |
We use atlassian tools for code reviews |
40% |
40% |
20% |
Many problems to solve with a large thought connection chain |
Overhead of pushing code to a joint repository |
Not much |
To learn about TDD |
Show
|
| 1.5 |
35 |
C/C++ |
C++ |
GTest |
What else? |
GTest + Adhoc |
RTOS = QNX; multiple nodes communicating over EtherCat bus; Simulink based motion control algorithms |
multiple... |
1-5 minutes |
Internal |
takes more than a page |
100 % reviews Fish-Eye and Bitbucket |
40 |
20 |
40 |
I like seeing the interactions of SW with the "real" world. I am an low level embedded engineer.
|
Sometimes it takes very long time to see the results - medical industry... |
not much |
hope to learn more advanced techniques. Hope to make code base more debuggable |
Show
|
| 1 |
6 |
C++ |
Python, C#, Javascript, Rust, Solidity |
not sure |
:) |
GTest / Pytest |
qnx 7.1.0, ubuntu 20.04 |
VSCode, WSL, Docker |
11-30 seconds |
. |
If it solves more than one problem (S in SOLID principles) |
Comments about things not done properly, improvements in speed/robustness (why and how) |
30 |
65 |
5 |
Creating new things and solving problems |
Writing unit tests |
It seems it is about writing unit tests before the actual functionality. |
I want to know if tdd is useful, and if yes, I would like to do tdd in the future. |
Show
|
| 4 |
10 |
C++ |
Java, Python |
GTest |
I have a background in biomedical engineering and work remotely from Nashville, TN. |
Unit, Integration (HW + SW), and system verification |
QNX Armv7 |
VS Code to develop, Docker to build |
5-30 minutes |
Collaboratively developed and reviewed by colleagues who volunteer. Updated almost yearly. |
When it encompasses more that one main functionality. |
Code reviews are completed on the pull request |
20 |
70 |
10 |
There are many ways to accomplish tasks, and code reviews are helpful to learn from other people. |
Spending more of my time working with machines instead of with people. |
It's a way to ensure software is doing what's specified by requirements, unbiased by implementation. |
To learn how to better integrate tdd in my day-to-day. |
Show
|
| 4.5 |
12 |
C++ |
C
Python |
googletest
cpputest |
please mention that tests should be broken down meaningfully test cases and tests for readability. |
static analysis
unit-test
functional-test
system software in system |
qnx
windows
linux |
clang toolchain
qnx toolchain
|
1-5 minutes |
in-house coding standard with selected rules from google coding style, cpp corerules etc |
too complex: check with static analysis tool. Too long: measure execution time. |
we use Atlassian online tools to review the code changes. |
2 |
6 |
2 |
You can know what the software should do and check what it actually does. |
iteration takes long time. |
test if software outputs the expected result with certain input |
team exercise |
Show
|
| <1 |
15+ |
C/C++ |
C# and some python, but not really. I Know enough to get in trouble. |
None, experimented with Unity and CppUTest due to TDDEC Book |
I started my career as an industrial electrician were I worked with PLC,s variable drives, etc. I went back to school and studied EE where I was introduced to embedded systems and quickly realized that was my passion. I like building model rockets. |
Bench test, toggle IO, printf, hw in the loop testing. |
Cortex-M7 with external memory,sensors, xcvrs. |
VS Code
GCC
CMake
cppUTest
WSL2
MSYS2
AtmelStudio
IAR |
1-5 minutes |
Dated |
When the functionality is not apparent with a quick review of the code. |
Minimal |
UNDEF |
UNDEF |
NaN |
Recently, I have been trying to learn more about architecture/designing sw vs just coding. |
Lack of documentation/requirements |
Failing tests come first, the test is the first client, test doubles help w/absent dependencies |
I have read the book and want to exercise what I have learned to share with my team |
Show
|
| 1.5 |
7 |
C++ |
Python
Bash
JavaScript |
GTest |
I enjoy building thing my spare time and don't like huge frame works. |
Unit tests and SITL tests |
armv7/x86 qnx systems |
VS Code |
1-5 minutes |
We have one, no specific guidance on unit test coverage. Req of no static analysis errors. |
Personally, when It tries to accomplish more than one objective. |
At lease two dev reviewers. |
40 |
30 |
30 |
Using code to use hardware to interface with the real world. |
Unnecessary complicated code, and arch, left by devs trying to be clever. |
Design tests(establish functionality needs) first then write the code. |
Testing code in units is faster than testing on HW. Want to get better at it. |
Show
|
| 7 |
30 |
C++ |
Python, Rust, C, Bash |
GTest |
I enjoy looking into hard to debug problems.
In my spare time I like to go running, hiking and rock climbing. Also I like to spend a lot of time with my two kids. |
GTest |
QNX 7.1 and Linux |
Vim, VSCode |
4-8 hours |
Custom coding standard based on various publically available coding standards. |
Gut feeling. Mainly where it concerns readability. But that's very subjective. |
Done in the Bitbucket pull request. >= 2 reviewers need to complete; all comments addressed |
10 |
10 |
20 |
I like building things and thinking about challenging problems. |
Waiting for long builds or tool runs. |
Write the test first, then make the test pass by implementing software. |
I can't imagine how TDD can work in real life. I want to find out if I'm wrong about that :) |
Show
|
| 2 |
2 |
C |
C# |
NUnit/JUnit
Ceedling/Unity/CMock |
|
Mostly system level tests that are automated. |
Microcontrollers |
Visual Studio
GCC
GDB
Bash
Python
Git |
11-30 seconds |
There are some guidelines for the coding style.
Indentation, naming, etc. |
N/A |
GitLab to manage merge request. Colleagues will review the change. |
33 |
33 |
33 |
It's fun to build something useful. |
It can be frustrating. |
I have heard about TDD a few times, also had a course in software testing while studying. |
Curiosity. |
Show
|
| 3 |
4.5 |
C or C++. It varies. |
Assembly(device specific), Python, C#, JavaScript, TypeScript, Markdown, LaTeX |
Ceedling and GoogleTest |
I enjoy making things in my free time, Whether it's baking, cooking, knitting, modeling and 3D printing, soldering, or writing microcontroller code. |
Depending on the project, either with Ceedling or GoogleTest for unit tests and Python for tests that interface with hardware. |
Usually a microcontroller that's either running FreeRTOS or a custom Linux image built with Yocto. |
Atmel/Microchip Studio, VS Code, PuTTY, CMake, hardware JTAG debuggers, GitHub Copilot or ChatGPT |
1-5 minutes |
We don't have a formal standard at the moment. I mostly follow what I was taught in college. |
When there are comments labeling chunks that could be moved into their own function calls. |
We create pull requests and if a reviewer flags an issue we discuss it, though issues are rare. |
25 |
25 |
50 |
Problem solving and being able to make computers do anything, with enough thought and creativity. |
Banging my head against a wall chasing down bugs for hours at a time. |
It's a method of writing software to be easily tested & write tests, to reduce time spent debugging. |
To learn how to structure code to be tested and how to set up and write tests. |
Show
|
| 25 |
20 |
C, C# |
JAVA, Python |
JUnit |
love coding. |
Manually |
Various |
Various IDE |
30-60 minutes |
Company Standard |
Code Standard |
DevOps Pull Request |
50 |
10 |
40 |
Challenging |
Hard to find bugs. |
Tried once. |
Need to use it |
Show
|
| 9 |
20 |
C |
I've been really focused on C for the last longest time. |
Unity |
I love caves. I can't wait to go spelunking again. |
Unity |
The next target I know of is called the Platform Development project. |
IAR, Codewarrior, MPLab |
Under 10 seconds |
It needs an update |
It just feels too long |
Done online through DevOps |
30 |
30 |
40 |
I like the relatively quick sense of accomplishment when the plan comes together |
All the documentation to go along with it. And UL. |
I've had a little experience with it. |
To brush up in preparation for building our AOS code library |
Show
|
| 2 |
10 |
c |
C++ |
TDD |
no |
TDD |
ARM cortex-M3/M4 |
Keil IAR e2-studio |
31-60 seconds |
no |
no |
DevOps |
30 |
30 |
40 |
no |
no |
know a little |
To let code strongger |
Show
|
| .5 |
2 |
C |
python |
cunit |
my experience is in v/r & re. I want to learn the other side of it. my personal projects at home fail miserably because ive never devoted time to learning how to do things in small/incremental steps |
right now its non existent |
arm32 bit embedded systems running linux |
vscode, make, scripts for upload |
1-5 minutes |
I dont have one, does clang-format count? |
when it does more than one thing |
very informal, usually a small amount of discussion and a pull request soliciting teammates comments |
10 |
10 |
80 |
I like building things, and i have little experience doing this. my experience is in v/r and re |
i hate debugging, and getting sucked into writing a bunch of code at once, instead of incrementally |
only the basic concept behind unit tests, ive never written any. |
I want to learn how to build embedded systems reliably. |
Show
|
| 11 |
28 |
C# |
C++(Arduino)
|
Never used one. |
The 1st computer I saw was in the 80's @10yrs old. I started programming @15 on a toy laptop in BASIC, then @16 I got 1st PC, a 486 with Win3.11 and moved into QBasic, VB, C#. BA Comp Eng. @35. Was an Electrician, Machine Maint. Facilities ENG. |
Just look to see if what I wrote does what I want it to do. |
I'm not sure |
Visual Studio
E^2
IAR
Arduino IDE
Unity3D |
1-5 minutes |
I've been prog. for 28 years. I've been a hobbyist, until 1.5yrs ago. So I've not used a standard. |
when it repeats itself, or my finger gets tired of scrolling. |
Not what they should be. |
45 |
5 |
50 |
Time disappears, I get on an emotional rollercoaster with lows and highs. It keeps me engaged. |
That I eventually get tired and have to stop. |
Just the very little of your book I've read so far. It sounds very interesting. |
Company encouragement, but I want to learn anything from experienced programmers I can. |
Show
|
| 2 |
10 |
C |
C#, C++ |
Unity |
I have experiencein designing temperature controllers, power switching devices, thermostats etc. |
using debugger |
temperature controller pcb with ARM microcontroller |
Renesas E2 Studio |
1-5 minutes |
We follow company's coding standards. Try to write code that will be easly readable and portable. |
when it's hard to read and follow |
Code reviews are done using DevOps. |
50 |
25 |
25 |
I like to design sofwtare because I like to solve problems and be creative and innovative. |
pressure to deliver bug-free software within short time frame. |
It is used to create more bug-free code by first designing the test methods. |
TDD course is required by my company, but I'm also courious how it works and want to learn more. |
Show
|
| 1 |
9 |
c |
python |
unity
Cunit |
I enjoy music and the outdoors |
unit tests around Cunit framework |
embedded linux device running on beagle bone type hardware |
VSCode with gcc toolchain |
1-5 minutes |
Covers practice of Coding Conventions, Validation and Test, Defensive Programming and Formatting |
when it starts doing more than one task |
code is peer reviewed through git Pull Request from dev branch into feature branch for testing |
40 |
30 |
30 |
I like determinate logic |
debugging |
start with the test design then develop the application to satisfy the test cases |
i want to develop my approach to TDD |
Show
|
| 3 |
8 |
C |
Python |
None. |
Electronics and telecommunication engineer, Control and Automation specialist, learned SW in 2002 (Delphi), worked in 10 different companies, worked with: IT, software, database, hardware, SW QA, Management, etc. |
Using framework-less unit tests. |
Telematics device for transport refrigeration systems |
VS Code, Git, CMAKE, MAKE. |
5-30 minutes |
Try to follow as best as possible the guidelines shared among the team, but sometimes differs. |
personally when it's doing many different logics, or repetitive, or much bigger than a screen page. |
reviews based on logic, best functions, comments, variable types, magic numbers, use of enums, etc |
70 |
10 |
20 |
Put ideas to work in the real world. Challenging myself. Different tasks. Math. Logic. Teamwork |
Testing. Solitary. Long time in a chair. low interaction with other people. |
I understand the concept and tried to implement something. |
Because my manager wants that we all start making more unit tests and he wants to use TDD approach. |
Show
|
| < 1 |
5 |
C/C++ |
Python, JavaScript |
CppUTest, Unity |
In my free time, I enjoy reading, engaging in various forms of digital media (video games, shows, films), exercise (particularly martial arts), LEGOs, and working on personal software projects. |
Yes, but not unit tests. |
Generalized I/O systems, capable of running various peripherals. |
VS Code, some kind of Terminal, some Eclipse-based IDEs for platform-specific development. |
31-60 seconds |
MISRA-C |
When it eclipses 100 lines and has multiple instances of repeating code. |
We don't conduct code reviews. |
20 |
20 |
60 |
I enjoy solving simple to complex technical problems and applying an elegant, simple solution. |
I don't enjoy working within a codebase that doesn't apply software development best practices. |
I've read James Grenning's TDD book a couple times and have tried implementing it once or twice. |
I would like to practice my TDD skills more and apply it to my work from the bottom-up. |
Show
|
| 3months |
10 |
C |
C++, python, bash, c# |
GTest, NUnit, CUnit |
Also want to become a better project manager |
CUnit |
arm |
VSCode, git |
11-30 seconds |
Google standard |
More than 70-100 lines |
2 approvals/reviwers per merge request |
40 |
30 |
30 |
Writing software |
Debugging |
Writing tests before beginning development |
Write better tests |
Show
|
| 6 |
15 |
C |
Python |
Ceedling |
I'm a foodie |
Ceedling |
Bare-metal ARM |
Vendor provided tools |
1-5 minutes |
Loosely based on K&R |
When it's doing multiple things |
Conducted during PR review |
60% |
15% |
25% |
Creating new apps |
context switching |
Few concepts (having used ceedling) |
To formalize my TDD learning and fill any knowledge gaps/ learn best practices |
Show
|
| 2 |
5 |
C |
Python, Bash |
Internal company framework, gTest, unity (not the game engine) |
A nerd not only at work, but in a lot of things. Love hiking, cooking, gaming, and learning new things. Soon to have a second son (being able to set my own pace with this course will come in handy :)) |
Code first, unit and integration tests later. |
Mainly an ARM Cortex M processor from STM32 |
VIM for writing code, VSCode for debugging. VM and Docker environment for building and unit testing. |
Under 10 seconds |
Main focus is readable AND memory efficient code. Functions and components should do one thing. |
When it does too many different things. When it's hard to read. |
Find potential bugs, suggestions for cleaner code, tests run in CI |
50 |
20 |
30 |
Problem solving, collaboration, it's a craft you hone, mix of tech. knowledge and creative thinking. |
Debugging is fine, but doing it under time pressure is awful (which is normally the case) |
Not much, test before you implement. People have very strong opinions of it (on both sides) |
I've heard a lot of negative opinions on TDD, and some positive. I'm want to form my own opinion :) |
Show
|
| 3 |
5 |
C |
C++, Rust, Python, LabVIEW |
ucunit, Google Test, |
Worst question ever... hmm, I like speed and I also like to think. I chase perfection and don't like sloppy, not-thinking-enough people. I like caffeine and it's REALLY hard to do something I'm not interested in :D |
Unit tests running on target using ucunit framework, and partially the same tests on PC with the same framework. Also there's obviously debugging and manual inspection. |
TI C2000 |
Code Composer Studio, Visual Studio Code, LDRA. |
1-5 minutes |
Pretty rigorous as I work in aerospace - for example no function pointers. |
When it becomes hard to follow - for example > 60 lines of code? |
What can I say, they are performed by other team members. They are OK I guess? |
50% |
10% |
40% |
The magic of making the logic work, thinking about ideas and then creating code from them. |
Slow development environment, tedious tasks (boring debugging included) |
I understand the general idea and I would like to try it in practice. |
Well, I wanted to know more about TDD and maybe try to introduce it in our work. |
Show
|
| 3 |
12 |
C |
C++ assembler |
VectorCast, CUnit UCunit Gtest Gmock |
nothing special |
unit and integration test |
embedded systems for automotive and aerospace
|
lauterbach gcc eclipse beyond compare |
1-5 minutes |
it is |
use my brain |
we have |
10 |
70 |
20 |
there is no ideal code |
I like |
I used it |
test only |
Show
|
| 3 |
7 |
C |
Python |
zephyr ztest |
I'm a slow learner, I have had difficulties with programming but I'm improving. I enjoy it and I like embedded systems. |
zephyr ztest, unit, integration and system test |
Lock platform. |
python, zephyr, jlink, VSCode, docker, and others. |
5-30 minutes |
Readability and functionality - code does what it intends to do |
When irrelevant or repeated logic is available. |
Review all code that is ready for contribution. |
60% |
20% |
20% |
Creating |
Not getting enough time for research or improving solution. |
To achieve reliability, find bugs, and modular approach during development. A way to limit errors. |
I want to learn more about TDD, I have heard and read stuff but really not got time to get hands-on. |
Show
|
| 14 |
20 |
C |
python |
ztest, company´s own |
I am an embedded software engineer that is really passionate about testing. Not only unit testing and TDD, but all forms of testing. For me, testing is the heart of product development. |
Unit tests with ztest / fff. Integration and system level testing on real hardware with Robot. |
Locks, readers, door automatics |
Tools provided by the Zephyr platform |
Under 10 seconds |
Following the coding standards from the Zephyr platform (similar to Linux coding standards) |
It doesn´t fit on the screen :) Or sonarqube tells me it is too long |
Every change is reviewed in merge request using Gitlab. Each merge request needs 2 approvals |
40 |
50 |
10 |
It is fun to see the code in action. Problem solving |
Nothing really. Perhaps fighting with tools that doesn't work or slows down your work |
I know quite a lot of theory. I try to practice it when I can. I teach TDD in the company sometimes |
Evaluate if this is a good course for colleagues that want to take programming to the next level |
Show
|
| 5 |
23 |
Python |
Java, PHP, Javascript, C/C++ |
unittest,behave,JUNIT,Cucumber,Mockito,PHPUnit, Behat,mocha, sinon, jest,googletest, CppUTest |
I am a programmer who likes his job. I don't like stress or pressure at all, but I can deal with it. |
I started strictly programming through test driven techniques 5 or 6 years ago. Before that, I used to write some tests or partially going through something like BDD. Making many common testing mistakes though. |
My job is about web environments, and part of a personal project is about microcontrollers and comm. |
From many years ago I have the personal license for all Jetbrains tools. CLion for C/C++ |
Under 10 seconds |
I try to "objectify" everything in order to stick to SOLID principles. |
function does many things, or I cannot quickly understand it, or it does not fit my little screen |
I'm a bit strict but at the same time I understand that there is not only one way to do things right |
40% |
50% |
10% |
It's a cheap way to create very powerful things. Things that may seem to have its own life. |
My code from last year backwards. I will think the same next year |
It's a "pathfinder" technique for any development journey. Very helpful in the structuring process. |
Reading "TDD for embedded" book improved my TDD knowledge a lot. I want to go to the next step. |
Show
|
| 2 |
26 |
C |
Assembler
TKL
Flavors of BASIC |
CUnit |
All of the above answers are from my memory of doing it more than a decade ago. I have not been coding for a long time. This is an adventure! |
Debug |
x86 microprocessor. 48K RAM. 4K ROM |
Visual C |
1-5 minutes |
Our own definition that is updated as needed. Mostly about syntax, little about structure. |
It's longer than 50 lines on the screen |
Happen when an engineer expresses difficulty or requests a review. Also when a debugging. |
40 |
20 |
40 |
Inventing worlds inside a microprocessor. |
Complex and emergent behaviors |
The cycle: write test, fail, pass, refactor |
You generously offered it to me! |
Show
|
| 33 |
45 |
C |
Visual Basic for Applications |
Unity |
I am semi-retired, would like to train other on software quality. Resolving all the issues at our company to retrain them. Hope to do that when my contract is up. I love learning; the "aha" moment when I found what I was doing wrong. Best practices. |
TDD until it breaks down because we were not doing it right. |
Mostly water heater controls |
Eclipsed based IDE (KDS, MCUXpresso, starting Renasas E2Studio). Used others. |
Under 10 seconds |
Our company standard was based on Object Oriented in C using PC-Lint/Misra, formatting. |
We have not limited it. But usually TDD breaks down long before it gets big. |
We have used several tools most recently DevOps for pull requests. |
20 |
20 |
60 |
It is creative and I like seeing things "come alive", even a blinky LED is satisifying. |
When the code gets way to complicated and hard to debug. |
Took this course live at the Barr group years ago. Taught others including wrong practices! |
You gave me the chance to check out the online version to recommend to my colleagues. Learn more. |
Show
|
| 1 |
12 |
C |
Python, C++ |
Ceedling, GTest |
I am a heavy metal singer and an avid Magic the Gathering player in my spare time. |
Unit tests and integration tests. |
ARM processors in general. |
VS Code |
31-60 seconds |
Our company has its own internal coding standard, which is somewhat similar to MISRA-C. |
When it has too many lines and does too many things. |
We have a classical merge request/review/approval process. We need at least one approval to merge. |
50 |
20 |
30 |
Having the power to control and see the result of my work becoming "alive" on the hardware. |
Bugs and writing lots of documentation, usually. |
We do it actively and I have a good experience with it, but I feel like it can be much better. |
Learn more and be better at TDD. |
Show
|
| 1 |
3 |
C |
C++ |
Unity |
I am passionate about software development, however I have not had the chance to be a sole contributor and practise my craft. My roles have been less software, and a mixture of embedded systems e.g. electronics design, and reverse engineering |
unit tests using the unity framework |
stm32 M4 core, AM335x beaglebone |
VS Code and platformio, and Buildroot |
30-60 minutes |
None, but follow C++ core guidelines for C++ code. |
When it goes above 70 lines. |
A pull request is made on the repo, then all developers view and comment in the code in Github. |
4 |
2 |
3 |
The challenge of solving problems.
The consistent learning of new things. |
Not knowing how to structure the code.
Writing buggy code and do not know where to start fixing it. |
I have viewed throwtheswitch course on udemy about TDD. |
Not to learn more and make TDD my core development practice. |
Show
|
| 23 |
30 |
C |
C#, C++ |
0 |
I am a clean coder but still old school |
Debug |
Embedded software on MCU's for the medical market and certain tools for testing on Visual studio |
IAR, Visual studio, LabWindowsCVI |
1-5 minutes |
We have coding rules |
by good practices |
done through PR's on GitHub |
50% |
25% |
25% |
the power it has |
when it is not working or badly |
first approach about 6 months back |
I really need to implement TDD in my habits |
Show
|
| 2 |
7 |
C++ |
Python, Bash |
GTest |
As a child an teen I disliked computer science. During my physics studies I had to develop software and started loving it. As it is difficult to work as a physicist this becoming a sw engineer was a great way to earn money and enjoy work |
We write unit Tests for new code or sometimes modified code. We test our robot software in the lab, where we have a robot emulation or we simulate it in a docker container. These tests are defined in Azure DevOps testplans |
Industrial PC with Debian Linux |
Docker Containers VS Code, CMake, |
Under 10 seconds |
Company Internal, inspired by Cpp Core-Guidlines |
If it does not fit on the screen (I have bad sight, thus <30 lines) |
Pull Request in Azure DevOps. Often it is not completely asynchronously but we have a call |
50 |
10 |
40 |
The struggle for good design: understand a problem and figure out how to cut it in orthogonal pieces |
Understanding 20 year old > 1000 line functions and the fear of others that improving it breaks it |
Write your test first an the implementation second. This improves the design. |
I a conference talk by James, my project leader loves his book, thus I expected a high quality class |
Show
|
| 3.5 |
16 |
C |
C++, python, bash |
pytest, googletest, cppunit |
I chose embedded as my career because I really liked working with FPGAs at university, but due to the job market situation in my country I have been working mostly with embedded software. I like the challenge of resolving HW/SW problems. |
On my current python project (3D camera calibration analysis software) I use a combination of unit tests and manual testing. For the camera side we develop Linux drivers and c++ demo and test applications, and this is tested by developers. |
Nvidia Jetson with Ubuntu Linux, but also other similar SoC Linux platforms (NXP, TI ...). |
Visual Studio Code, Git, RhodeCode |
1-5 minutes |
We have an internal coding standard but it is not enforced in my team. |
It doesn't fit on my screen or I can't follow it |
They are informal if any, we have been exploring making it part of the process but no consensus yet. |
33% |
33% |
33% |
The feeling of mastery, establishing order & repeatability, problem solving, making things work. |
Working on low quality software that behaves erratically. Chaos that ensues when requirements change |
I read your book "Test driven development for Embedded C"; my previous job used TDD in automotive. |
I think my software development skills have been stagnating, I hope to do more coding and learn. |
Show
|
| 3 |
7 |
SystemVerilog |
c,c++ |
google test, |
I like to play the guitar |
unit testing/googletest |
ARM A53 |
buildroot |
5-30 minutes |
We have a pretty decent coding standard with descriptive commit message and clean/organize code. |
Line limit |
We go through a robust review process with experienced reviewers. |
3 |
3 |
4 |
It is still much faster than developing rtl. |
Unit test takes a while to write |
None |
To become more efficient |
Show
|
| 0.5 |
2 |
C |
C#, C++ |
None really. Familiar with GTest. |
Highly motivated and willing to accept shortcomings. |
Test after programming. |
Microcontrollers (32 bit Arm Cortex) |
IAR, MPLABX |
31-60 seconds |
Overall good variable naming conventions, well formatted, constant == variable in condition, etc. |
When it starts to do more than one thing. |
We have reviews after the delivery of the code. Any review items are corrected accordingly. |
70 |
10 |
20 |
The ability to solve any (most) problems. Especially embedded systems solve meaningful problems. |
Overall when you lose track during debugging. |
Not a lot. Have read TDD for Embedded C but have not practiced it. |
To apply TDD to my job. Spend less time debugging and more time writing quality software. |
Show
|
| 2 |
5 |
C |
Python
C++ |
gTest
|
I enjoy prototyping. I have a 3D printer at home that I use to print broken parts / mods for diverse objects.
I love bike-packing and wish to discover the world by bike. |
I recently tried to have a TDD approach. (lower effort)
For long I did "custom main test".
Tests with hardware, simulating components to validate the system (higher effort) |
ARM cortex M4
|
ARM gcc toolchain
Makefile "build systems"
IDE: VSCode
Gitlab CI with Docker
Debugger: Segger
|
1-5 minutes |
We have linters that ensure the source code is well formatted (uncrustify) |
When I have to scroll up and down too much. |
We do merge reviews (enforced by Gitlab workflow). |
50 |
25 |
25 |
Continuously learning
Diversity of tasks
Unlimited ways of getting things done |
Useless meetings
Explain manager implementing a feature is not just some line of codes
Meetings
|
That we develop test before the code implementation. |
I like the concept of TDD, but I miss the knowledge of how to test the code well. |
Show
|
| 2 |
20 |
Python |
C, C++, Verilog, SystemVerilog, Tcl |
Google Test |
I was mainly a chip designer (ASIC, SoC) until a few years ago. Developing software at a professional level is still new to me. |
Google Test |
Linux, bare metal |
VS Code, Vim |
1-5 minutes |
I follow company coding standards. |
If I can't write a simple sentence to describe what the function does, then it's probably too long. |
We use PR (push request) review on Github. |
30 |
40 |
30 |
I like analytical and creative aspects of software development. |
It's somewhat detached from the physical world. |
Develop test while adding features. |
Multiple people from different companies have recommended me to take this class. |
Show
|
| 1 |
10 |
C |
Python |
None |
I'd prefer to be involved more in physical activities and staying fit. I cycle 10 miles everyday(up and down to work).
I love soccer. Not very social but I do not have problems in starting conversations. I'm patient and resilient. |
The python script executes commands on the controller via serial terminal. I check the return code and if execution is incomplete, it throws an error and stops further execution. |
High performance controller. It is for supporting industrial automation. |
Visual Studio Code, VxWorks OS, Eclipse IDE. |
1-5 minutes |
Split code into pages based on functionality.
Indentations. Comments. |
If it does something more than than what the function name suggests. |
Check for code readability(comments, variable and function names)
Edge test cases are covered |
30 |
20 |
50 |
Collaboration with team and ownership. |
Burnout |
Prevention is better than cure. |
Everyone can code but not everyone can write bug free code and handle large codebases. |
Show
|
| 0 |
13 |
C |
assembly, python |
unity, cmock, pytest |
Into gaming, hobbyist electronics and cooking/baking. |
Manual test cases |
Sensor data collector 32bit ARM microcontroller |
vscode, gcc, python, debug probes, logic analyzers |
31-60 seconds |
Organization coding standard focused on configuration management. |
When it has more than one responsibility. |
Through, spanning from 1 day to a couple of weeks depending on the size, complexity and impacts. |
30% |
30% |
40% |
Be able to see the outcome of my work, be it a blinking LED or data getting moved around. |
Having to deal with legacy code with awkward formatting/standard/architecture. |
Code the tests asserting behavior first, then code the modules that deliver those behaviors. |
To learn more about testing while being endorsed by the company. |
Show
|
| 0 |
20 |
C |
Python |
pytest, gtest |
i work on the build system at the moment |
pytest |
arm64 board |
cmake, gcc, g++, make |
Under 10 seconds |
none |
when control flow is difficult to understand |
none |
33 |
33 |
33 |
solving puzzles |
solving puzzles |
write test first, then write code |
company training initiative |
Show
|
| 6 |
20 |
C |
Assembly, Python, C# |
cpputest |
I'm working on a pilots license and building my own experimental aircraft. I have 2 dogs and 12 acres to myself in Wisconsin. I've only worked as an employee once before becoming a contractor for the last 15 years. |
Manually |
Embedded. Typically 8 or 32 bit. |
Usually just a syntax highlighting editor. Vendor tools if needed. |
Under 10 seconds |
It borrows heavily from the linux kernel. |
Minimizing complexity is more important than minimizing length. A function should do one thing well. |
I'm usually solo on any one module. For anyone affected I usually review over screen share. |
33 |
33 |
33 |
Creation. Automating a complex task to make it simple and useful. Also getting paid. |
Needless complexity. Design decisions being made by unqualified individuals. |
Automates testing of requirements from the design phase. I would say it promotes top-down. |
This project requires it, and I like learning new things. I'm also getting paid. |
Show
|
| 2 |
6 |
C |
Python, Matlab, Bash |
I do not know |
I like hiking in the mountains. |
We design code that tries to traverse all the functionalities of the code that make up a SW module. A main() program is designed to try to test the functionality and its outcome is recorded for comparison with a template. |
Embedded systems and microcontrollers |
Autotools, Make |
1-5 minutes |
The company defines a common standard for the code formating, naming and style conventions. |
Number of lines, excesive use of nested if-else, cyclomatic complexity measure etc |
Code is double checked by two reviewers and a Gitlab CI/CD pipeline checks compialtion,run tests... |
9 |
1 |
9 |
It's creative, you learn new things every day, you build things that a lot of people will use. |
Having to do it in a hurry because of deadlines |
It sounds to me like it helps to build tests as you develop code |
My company invited me to do it, but I hope it helps me in my daily work somehow |
Show
|
| 10 |
30 |
C |
C++, C#, Swift |
cpputest |
engineering manager, project manager, requirements engineer, architect, programmer..live/work remote from north central MN (i.e. north of twin cities, MN by 3 + hours) |
informal, started unit testing recently |
QP State Machine Code Generator in C++ on Linux with QT/QML |
pcs, scopes, logic analyzers, power supplies, protocol analyzers, ides, compilers, cmake (many more) |
1-5 minutes |
use existing style if maintaining /extending. new dev based on standard supplied by client or own |
need to scroll |
depends on project, mostly informal |
40 |
40 |
20 |
the challange |
interruptions when in flow |
a little, started reading you book and a few others and attempting on current project |
convinced boss that we needed to attend this class |
Show
|
| 7 years |
7 years |
C |
I don't use more languages |
Execute test suites of test cases. Generate associated test reports |
Everything I know and use programming I have done in this company |
in each commit gitlab executes developed tests in the project |
get a coverage of 80%. but it is not always done |
we use internal tools. we generate test reports or show test coverage |
31-60 seconds |
Execute test suites of test cases. |
the modules must be structured. You can't have a function that doesn't fit on the screen |
Must be reviewed by two reviewers. (since 2 years ago) |
6 |
1 |
3 |
new designs and find errors |
unit testing :) |
not much by the moment |
I've to spend more time testing the code i need more tools for that. I want to know more about this |
Show
|
| 3.5 |
7.5 |
C |
a bit of python and C++ |
CxxTest |
Apart from coding, testing, reviewing, I work very closely with the department in charge of defining specification (requirement definition). |
Manually. Sometimes I also implement code aside aimed to test specific functions within the main app. |
Final product are protective relays placed all along the electricity distribution network. |
Virtual Machine with Linux. Visual Studio Code. Gitlab. |
1-5 minutes |
I don't think we have one |
Intuition. Sometimes functions with more than 5 input parameters or over 1000 lines are not allowed. |
Every feature/bug is reviewed by 2 reviewers. We leave comments in Gitlab. |
3 |
4 |
3 |
Its related creativity. Its feeling of figuring out a riddle. |
Figuring out what a gigantic ancient piece of code does with no available written doc at all. |
All I know is that the approach when implementing should be: how will I test this? |
For building an automatically executable testing bench. We implement new tests per every ticket. |
Show
|
| 3 |
20 |
C |
C++
Python |
cppUTest
cppUTest for QPC/QPCPP |
I was skeptical of TDD at first, maybe still am but slowly seeing the value |
Attempting to get started with TDD. Prior testing has mostly been manual (with debugger, etc). |
Embedded control system |
MPLABX
Segger JLink
CMake
Lab equipment |
1-5 minutes |
No formal standard in place |
When the functions primary purpose is not immediately evident from looking at the code |
Not yet |
50 |
10 |
40 |
The reward of seeing things work |
Debugging extremely hard to find bugs |
I've been learning about TDD through reading your book and attempting to implement TDD |
Enhance my skills in TDD thru formal training, determine what to unit test and what not to unit test |
Show
|
| 1 |
8 |
C/C++ |
Python |
proprietary |
Big fan of classical music, which has a lot of technical/mathematical aspects as well. |
automated integration tests + manual functional tests |
Battery powered tracking device with a lifetime of multiple years, without easy way to update. |
J-Link, VS Code extensions |
1-5 minutes |
C++20 |
When I have to scroll back and forth to remember what happened earlier in the function. |
Almost none, currently only firmware developer in the company |
30 |
40 |
30 |
Bringing your ideas to life, solving the "puzzles", creating solutions to everyday problems |
Legacy code, bad documentation, unclear errors |
A bit from the book. Start writing tests, then implement the least necessary code to pass the tests. |
I want to become a better developer, create more reliable code and spend less time on release tests. |
Show
|
| 4 |
12 |
C |
Python, VHDL, C++ |
IAR |
|
Function test, module test |
Embedded, not mobile, control system and user interface |
IAR, SonarQube, |
1-5 minutes |
Based on MISRA |
Coding style |
min 2 devs
remarks written down in Excel template and graded on severity
follow up according |
30 |
10 |
60 |
Problem solving |
Testing |
Basic concept to first write a test, let it fail, write the code to satisfy the test case & iterate |
Improve my coding
Incorporate testing in my workflow |
Show
|
| 2 |
20 |
C# |
C, JavaScript, F# and C++ |
MStest |
I run a startup. |
with MStest |
Linux with Windows emulated |
VSCode and Visual Studio |
Under 10 seconds |
Try to adhere to Clean Code |
When it does more than one thing |
I work alone |
6 |
2 |
2 |
Creating something that works and makes thing easier is the best part. |
Hidden errors that show up when truly don't need them to show up |
Nothing at all except for peripheral talk. |
I want to code just work. |
Show
|
| 15 |
30 |
CLIPPER |
C, ASM, VISUAL OBJECTS |
Propietary tests. |
I want to know other points of view about programming. |
With our company tool. |
Embedded systems programed in C languaje. |
gcc |
1-5 minutes |
Using C languaje. |
when it has a lot of lines. |
Other programmers review my code and I review others code. |
50 |
20 |
30 |
The satisfaction when the application works fine. |
When the code is so complicated. |
Nothing except some notes from my boss. |
My boss says that is very interesting and could help us. He has done this training class. |
Show
|
| 4 |
20 |
C++ |
Qt/QML (framework)
.Net/XAML |
Usually in house harnesses |
I love crypto. Currently stacking crypto for the 24-26 bull run. Personally hitting the gym lately to improve body. Avid lover of Anime. Ready to learn TDD. |
Currently with a self made Unit Test |
Its a Debian linux system. |
Using C++, QP,QT/QML and Redis. |
31-60 seconds |
N/A |
N/A |
N/A |
7 |
2 |
1 |
Its a form of self expression. Its almost like poetry. Especially GUI work. |
Lack of documentation... when learning something new.. sometimes the documentation is lacking. |
That Tests should be modular/self contained. The test (should) be completed before you code. |
To learn about Test Driven Development To really think like a Tester and have a process for testing. |
Show
|
| 2 |
6 |
C++ |
C, Java, Python |
None |
No thanks |
Automated java test |
JBOSS |
Eclipse |
31-60 seconds |
Google Java standard |
When it's purpose can't be described simply |
Peer review and external review |
30 |
30 |
40 |
Immediate feedback |
Often requirements change |
Not much |
It was recommended |
Show
|
| 0 |
5 |
c++ |
C# and Python |
None |
This is my first professional job in the field so I hope to learn some good practices for my career |
We have unit tests that were set by a previous developer |
a machine that runs on C |
vs code and gitlab |
11-30 seconds |
I just go with regular c++ standards |
if I feel I can make it shorter or needs to be split |
I need to work on that |
20 |
30 |
50 |
solving problems |
how some simple tasks can be complicated |
Added by my project |
To learn how to test my code |
Show
|
| 7 |
12 |
C |
C++, Python, Lua |
For small pieces of code (C/C++), cpputest and unity. Once: GTest.
Python: unittest or pytest. |
I really like learning new things related to tech and looking for useful applications related to my personal or work life.
I'd like to convince my work group of the usefulness of the tests.
I don't like to leave things incomplete. |
Sometimes, I extract some pieces of code testable and generate some new C files to test them with some framework like cpputest.
Most of the times, I need to upload the FW of the device and test the application with traces, files or I/O and oscillo. |
I don't understand well. Arch? Tests? I want to test small SW pieces in PC (unit-testing). |
IDE:VSCode
Linux system
Docker
Doc: Markdown
Style:clang-format
Code complexity:lizard
VC: Git |
1-5 minutes |
Style: Similar to Linux kernel
Limited use of globals
Short length of functions
Doxygen for doc
|
First of all, common sense.
Sometimes, I use a cyclomatic complexity analyzer. |
I usually use cppcheck, flawfinder and lizard.
We also have a human peer review in our process. |
30 |
30 |
40 |
Tangible results, continuous learning, capability of automation and increase efficiency. |
Maintain certain bad-structured without test code, uncertainty of some development tasks. |
Test code is done before functional code. In that way, all the functions will be tested. |
The security that testing correctly, the maximum number of use cases, gives me satisfaction. |
Show
|
| 2 |
5 |
C++ |
MATLAB, Python, C# |
Tortoise SVN |
I graduated from UCSB in 2021. I am an EE so I always enjoyed doing math rather than coding. I am an active person who plays soccer and goes to the gym often. I am really into cars. |
I usually just debug and make sure the code is operating as it should. |
I am not sure what a target system is |
Debugger |
1-5 minutes |
Use appropriate naming, add comments, use exception handling |
When you see that you can make multiple smaller functions with the code in the long function |
Code reviews usually consist of renaming variables |
30 |
30 |
40 |
The sense of accomplishment of getting code to work |
It gets frustrating when the code does not work, I there is no logical reason |
I don't know anything about tdd |
I am an electrical engineer and I am not an expert at coding so I wanted to improve my coding skills |
Show
|
| 1 |
10 |
C/C++ |
Python |
CMock, Catch2 |
I am always looking for ways to improve my development skills. I am very keen on gaining significant skills in TDD domain. |
No unit testing, only behavioral. |
ARM v7 |
IAR, Clang-Format |
5-30 minutes |
C++17 |
If I have to start scrolling. |
Review by peers using pull requests |
30 |
40 |
30 |
Writing software is like solving a puzzle. There are many ways to solve the given problem. |
The time required to test changes. |
It is the right way of software development. Create the test first, before writing software. |
I am really bad at TDD, especially when it comes to implementing unit testing for legacy code base. |
Show
|
| 0 |
28 |
was C#, now C++ |
C, pascal script |
Unit test framework bult into Visual Studio Enterprise for .NET Framework |
My previous job had me doing as much process control as development. |
Will be using cpputest very soon |
stm32H745 controlled PCBs |
STM32CubeIDE and later VS Code, but hopefully it will become VisualGDB on Full Visual Studio 2022 |
11-30 seconds |
We are supposed to use the Google coding standard |
It takes more than one screen or does more than one real task or contains generic code go elsewhere |
Have not participated in one yet |
23 |
10 |
7 |
Creating automation |
Rigid enforcement of every possible design pattern that can be forced into an implementation |
Excellent way to reduce bug risk |
I do not know this framework and it is part of my onboarding |
Show
|
| 3 |
4 |
C++ |
MATLAB |
None |
I love the Lakers |
With external windows program |
I maintain test software for aircraft systems. |
Visual Studio |
1-5 minutes |
I just utilize the same style as what has already existed on the program |
When its performing too many actions |
Quick and not very thorough |
2 |
3 |
5 |
You can do it for everything |
When its not working |
Nothing |
So I can learn more about unit testing so I can be more efficient when maintaining my program |
Show
|
| 1 |
0 |
C++ |
C#, used a little of Java |
None |
I'm still fairly new to developing code in my career. I am mainly taking this class to expose myself to new thing and especially benefit myself for my current job. |
Very new to this so nothing as of now |
Not familiar |
GitHub |
11-30 seconds |
Just started |
If it is trying to do too much at once where it can be broken up. |
Just started |
20 |
30 |
50 |
It's good to keep track and keep revision control. |
N/A |
Nothing |
I want to learn more about test development. I have little to no exposure to it at this point. |
Show
|
| 3 |
5 |
C# |
C++, Javscript |
MSTest for C++ and C# |
I like coding |
For C++: using dependency injection, passing in mocks and monitoring behavior
For c#: using dependency injection, passing in mocks using a mocking framework (Moq) |
N/A |
Visual Studio |
11-30 seconds |
Follow the recommended coding standards from Microsoft and try to think hard about dependencies |
It is difficult to follow / read / understand and hard to break out into tests. |
Not done often enough due to shortage of people |
50 |
25 |
25 |
Designing code that is flexible enough to adapt to future problems is an interesting challenge |
Realizing you've made a mistake in your design |
You write tests before writing production code so that your code fits the testing requirements |
I believe the principles behind making code testable are very important whether or not you use TDD |
Show
|
| 4 |
4 |
Java |
Javascript, Python |
N/A |
N/A |
Unit tests, Integration Tests, End-to-End Tests |
N/A |
Git, Docker, Gradle, Jenkins |
1-5 minutes |
N/A |
N/A |
N/A |
30% |
40% |
40% |
The problem solving aspect |
Debugging can be time consuming |
Write failing tests. Rewrite tests to make them pass, then proceed to write implementation |
Learn more about test driven development |
Show
|
| 1 |
4 |
Python |
C++,C#, C |
None |
I enjoy traveling! |
Manual Tests, Some unit tests |
C++/C# |
Visual Studio Code |
1-5 minutes |
Try to keep things modular when possible and only allow access when needed. |
When you realize you can have multiple sub-functions live in it. |
Have others test/review code for things that I write and vice versa. |
40 |
20 |
40 |
Solving issues that present itself. |
Huge dependencies that touch many aspects of the code base. |
Have not had any experience with tdd. |
It looks like a good way to learn more about tdd and become better at development. |
Show
|
| 4 |
4 |
C# |
C++ |
None |
|
There is an option in the software to run in debug mode where hardware calls are simulated.
Test cases are performed during run time. They first run in debug mode, then in real mode. |
Target operating system is Windows |
Visual Studios 2008 |
31-60 seconds |
Prioritize code readability. |
The function has more than 300 lines of code |
Change existing code as needed:
* errors found
* new crucial functionality needed to old classes |
50% |
25% |
25% |
Fast iteration times |
|
Inputs and Outputs of test cases are set prior to coding the module that performs the test. |
I would like to learn new skills that may be applicable to my project. |
Show
|
| 8 |
27 |
Java |
C# |
JUnit |
a software engineer having BS and MS in computer science. |
number of complexities (n**2) - 1 |
different companies have different target systems. |
IDE, database (object & relational), UML tool, JavaScript, JavaFx. |
Under 10 seconds |
It is depending on the company or project has coding standard or not. I use my own if there isn't |
do more than what a function should do or by counting number of complexities |
I do code review but not very strict. Most coworkers do not because there is no process about it. |
45 |
45 |
10 |
I have a passion to do software development. |
Not clear about requirements. |
none. |
My supervisor recommends and register it for me. I didn't know. |
Show
|
| 1 |
1 |
c++ |
C#, matlab and system verilog |
none |
I like peanut butter a lot |
I don't test my code, other than seeing at run-time if it performs the operations i want it to do |
NA |
Visual Studio |
1-2 hours |
I try to keep to minimum lines using descriptive variables and function names |
When it can not fit in a vertical screen at reading font |
NA |
40 |
10 |
50 |
I like using a keyboard |
there are a lot of things to think about all at once sometimes when looking maintance of code |
This can be extremely important when applying to software that puts people's lives in danger |
Thought this class will be interesting |
Show
|
| 5 |
8 |
C# |
C, C++ |
None. |
I don't like surveys. |
Trial and error. |
What do you want to know? |
Visual Studio |
1-5 minutes |
Work in progress. |
When I get lost scrolling. |
No one wants to do them. |
20 |
0 |
80 |
It pays the bills. |
It never works the first time. |
Nothing. |
42 |
Show
|
| 3 |
2 |
C# |
little bit of C++ and Xaml |
none |
I like playing video games and practice drawing when I have the spare time. |
Running the code |
Windows |
Visual Studios 2022 |
11-30 seconds |
Practice standard coding procedures, such as naming conventions and function separation. |
30-50 lines |
little to none |
40 |
20 |
40 |
The satisfaction of making the code run as intended |
everything |
none |
Forced to learn |
Show
|
| 15 |
30 |
c++ |
na |
none |
i have a dog |
trial and error |
test equipment |
visio |
31-60 seconds |
NA |
performs more than a single function |
pier reviews |
2 |
2 |
8 |
I like to build things and satisfaction when things work well |
documentation |
I dont know what that is |
build better software for maintainability. |
Show
|
| 1 |
20 |
C++ |
Python |
Google Test, Junit (long ago) |
I'm currently working at AMD in diagnostics, where we write test suites to screen chips that just came out from the factory. I use to work at AAA game studio for 10 years and wish there were better testing practices used. |
1) Running real tests that were written
2) Manual execution |
Windows 11 laptop & desktop |
Visual Studio, Linux clang/gcc toolchains, git |
1-5 minutes |
At work we use clang-tidy for linting and clang-format for coding standards |
clang-tidy gives a warning/error |
CR done through Gerrit. Team members provide feedback. An official reviewer has to approve |
50 |
25 |
25 |
Making software which others will use |
Working in big teams with a lot of red tape |
I first read about it in Rob Martin's clean code book. TDD can help accelerate development |
I had read your Embedded TDD book which I enjoy. I'm interested learning from practical examples |
Show
|
| 0 |
4 |
C++ |
Linux and some C |
Google |
Have some experience with Java, Python, HTML, CSS, JavaScript, Scala although do not currently use |
LogEvents, Prints, if reasonable google unit test |
Multiple targets, intel architecture primarily |
VS Code, SmartGit, SmartSVN, Jenkins, GitHub |
31-60 seconds |
Custom Standards that include comments, file names, variable names, class names, structure names,etc |
When the function reaches beyond the screen |
Small groups of Developers review and test before a push to development software is allowed |
10% |
40% |
50% |
Finally fixing a bug, it is like solving a giant puzzle |
When code breaks from something super small and it takes an hour or more to find it |
Focus on developing Test for the code |
Mandatory from company |
Show
|
| 0 |
7 |
C |
C++, qml, python |
VectorCAST |
I'm excited to learn any ways to improve my skills, knowledge, and efficiency. |
Manual testing with hardware on my bench or in a product |
Embedded system of several microcontrollers used to control commercial cooking equipment |
STM32Cube, IAR |
5-30 minutes |
I'm not aware of any formalized coding standard |
-If it could be better represented by smaller functions
-If it takes longer than needed in scope |
Code reviews are done prior to merging any focused branch into the main branch in a repository. |
35% |
45% |
20% |
Bringing something new to life
Solving complex problems
Gaining very specialized knowledge |
Unclear requirements that cause rework
Finding evidence for very elusive bugs |
Not much - except "write test, test should fail. Write code until test passes". |
I've heard lots of good about TDD as a practice. I'd like to learn how it can benefit my daily work. |
Show
|
| 0 |
7 |
C |
C++, qml, python |
VectorCAST |
I'm excited to learn any ways to improve my skills, knowledge, and efficiency. |
Manual testing with hardware on my bench or in a product |
Embedded system of several microcontrollers used to control commercial cooking equipment |
STM32Cube, IAR |
5-30 minutes |
I'm not aware of any formalized coding standard |
-If it could be better represented by smaller functions
-If it takes longer than needed in scope |
Code reviews are done prior to merging any focused branch into the main branch in a repository. |
35% |
45% |
20% |
Bringing something new to life
Solving complex problems
Gaining very specialized knowledge |
Unclear requirements that cause rework
Finding evidence for very elusive bugs |
Not much - except "write test, test should fail. Write code until test passes". |
I've heard lots of good about TDD as a practice. I'd like to learn how it can benefit my daily work. |
Show
|
| 3 |
7 |
Java |
JS/TS, PHP, C++, Python |
JUnit, Jest, Cypress |
Was a hobby programmer before going to school and getting this job. Still a hobby programmer. |
Unit tests, some integration tests, end-to-end |
Secure website. React front-end, Java Spring back-end |
VsCode, Intellij |
31-60 seconds |
Java-style formatting |
When I can't understand it. Name proliferation vs readability. |
Pair programming for real-time review, 1 or 2 person review before merge |
50 |
40 |
10 |
Logic, data structures, problem solving |
Tests take longer to write than code |
Write test first, fail test, pass test |
Never formally trained in TDD |
Show
|
| 5 |
5 |
C# |
C++
Python
C
Java
Visual Basics |
NUnit |
I play video games as a hobby |
Test Classes |
Windows |
Visual Studios Code |
31-60 seconds |
Microsoft C++ Coding Standard |
Typically when it is larger than what my monitor can display |
Our code is goes through a review process through our coding architect |
20% |
20% |
60% |
Writing my own code and getting it to work |
Reading other peoples code |
It helps our coding development cycle |
I was recommended to take this class. |
Show
|
| <1 |
5 |
Python |
C#,C++ |
None |
I like to play video games. |
Basic functionality tests |
Embedded System written mostly in C++ and ADA |
Visual Studio, Windriver Workbench |
30-60 minutes |
None |
If you have to scroll multiple times to read it all. |
Only done for merges into development. Review by at least 1 other person. |
20% |
60% |
20% |
There is always more than one correct way to approach the problem. |
It can be very frustrating when you do not understand why your code is not behaving as expected. |
I had heard of the concept before but never looked into it. |
Suggested to attend by project lead. |
Show
|
| 1 |
4 |
Javascript |
Python,
Java |
Juint for javascript |
I like Anime |
By making test to ensure coverage |
To have full coverage with little to no vulnerabilities |
VSCode |
1-5 minutes |
If it runs and there are no vulnerabilities. Good to go |
by checking the time complexity of the function |
We usually bring in another team member to examine the work as we explain why we implemented it. |
6 |
2 |
2 |
When everything works |
When everything doesnt work |
That you should try and do TDD before programming the function, not after |
My work would like our team members to take the course |
Show
|
| 6 |
11 |
C# |
C,C++ |
NUnit,GoogleTest |
|
NUnit,GoogleTest,Manual |
Embedded C++, Desktop C# |
VSCode |
5-30 minutes |
On wiki, patterns, styles, etc |
It becomes difficult to understand what it is doing and/or requires scrolling to see it all |
Done via Gitlab Merge Requests. Sometimes async via the website. Sometimes sync over Teams |
50 |
25 |
25 |
It is very powerful and flexible |
Constantly wrestling with IT |
Write tests based on behavior before writing implementation. Strong when requirements are known |
Refresher |
Show
|
| 4 |
6 |
Java, React |
C/C++, Python |
JUnit, React Jest |
I moved to California from New Jersey to take this job. |
I run the Java tests on VSCode and I use "npm test" command to run the React tests |
AWS Linux |
VSCode |
Under 10 seconds |
SpringBoot and React standards |
When it does too many things. |
We review code every two weeks |
60 |
20 |
20 |
Working independently and creatively. |
Tracking down bugs. |
You code to pass the test |
My boss suggested it. |
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
I like playing piano |
Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
1-5 minutes |
Follow Microsoft C# coding standards |
Usually if we think the function can be split up to accomplish something |
All code is reviewed by our lead before getting merged in |
25 |
25 |
50 |
Seeing that it works and the product helps people |
When it doesn't work and you can't figure out why |
Not much. |
Haven't learned anything about tdd before. |
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
I like playing piano |
Write unit tests to test for correct method and class functionality |
Not sure |
VSCode and Visual Studio 2019 |
1-5 minutes |
Following Microsoft C# coding standards |
Usually if we think the function does too much and be split up into another function |
All code is reviewed by our lead before getting merged in |
25 |
25 |
50 |
Seeing that it works and the product helps people |
When it doesn't work and are stuck for too long figuring out why |
Not much. |
Haven't learned anything about tdd before. |
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
I like playing piano |
Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
1-5 minutes |
Follow Microsoft C# coding standards |
Usually if we think the function can be split up to accomplish something |
All code is reviewed by our lead before getting merged in |
25 |
25 |
50 |
Seeing that it works and the product helps people |
When it doesn't work and you can't figure out why |
Not much. |
Haven't learned anything about tdd before. |
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
I like playing piano |
Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
1-5 minutes |
Follow Microsoft C# coding standards |
Usually if we think the function can be split up to accomplish something |
All code is reviewed by our lead before getting merged in |
25 |
25 |
50 |
Seeing that it works and the product helps people |
When it doesn't work and you can't figure out why |
Not much. |
Haven't learned anything about tdd before. |
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
I like playing piano |
Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
1-5 minutes |
Follow Microsoft C# coding standards |
Usually if we think the function can be split up to accomplish something |
All code is reviewed by our lead before getting merged in |
25 |
25 |
50 |
Seeing that it works and the product helps people |
When it doesn't work and you can't figure out why |
Not much. |
Haven't learned anything about tdd before. |
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
I like playing piano |
Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
1-5 minutes |
Follow Microsoft C# coding standards |
Usually if we think the function can be split up to accomplish something |
All code is reviewed by our lead before getting merged in |
25 |
25 |
50 |
Seeing that it works and the product helps people |
When it doesn't work and you can't figure out why |
Not much. |
Haven't learned anything about tdd before. |
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
I like playing piano |
Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
1-5 minutes |
Follow Microsoft C# coding standards |
Usually if we think the function can be split up to accomplish something |
All code is reviewed by our lead before getting merged in |
25 |
25 |
50 |
Seeing that it works and the product helps people |
When it doesn't work and you can't figure out why |
Not much. |
Haven't learned anything about tdd before. |
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
I like playing piano |
Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
1-5 minutes |
Follow Microsoft C# coding standards |
Usually if we think the function can be split up to accomplish something |
All code is reviewed by our lead before getting merged in |
25 |
25 |
50 |
Seeing that it works and the product helps people |
When it doesn't work and you can't figure out why |
Not much. |
Haven't learned anything about tdd before. |
Show
|
| 3 |
3 |
Java |
Javascript
C# |
JUnit |
I don't like winter cause it's too cold for me. |
I use TDD. |
Currently using Java |
VS Code, Git |
5-30 minutes |
I follow the team working agreement |
When it's over 10 lines of code |
My code reviews look for any errors in the way the code was written. |
50 |
20 |
30 |
I like how developing software allows me to do almost anything I can put my mind to. |
I don't like how debugging can be difficult at times. |
It's good for making sure requirements are met. |
I'm attending this class in the hopes to learn more about how to use TDD |
Show
|
| 4 |
8 |
C# |
Java, SQL |
NUnit |
I enjoy running and swimming |
NUnit |
Windows |
VSCode, Visual Studios |
31-60 seconds |
We work collectively to maintain an understood standard set by our lead |
When the responsibility of the function has become unclear |
Lead reviews our code |
70 |
15 |
15 |
It is a creative challenge |
Getting stuck on something |
Basic understanding of the concepts |
To improve my knowledge and produce better code |
Show
|
| 5 |
9 |
C# |
Java |
NUnit |
I like sports and video games. |
NUnit |
Windows |
Visual Studio, VS Code, Gitlab |
11-30 seconds |
Microsoft C# coding standard. |
When it'd doing too much. |
A reviewer review our code and provides feedback. I update my code resubmit for another review. |
50 |
25 |
25 |
What you can do with it. |
Running into an issue that takes a long time to resolve. |
It involves making the tests first and then writing the software to pass it. |
To learn more TDD and how we might be able to apply it to our current work. |
Show
|
| 5 |
5 |
C# |
Java, C++, C, Python |
JUnit. PyTest, XUnit, Google Test |
I enjoy model building and gardening in my free time. |
Most recent projects have been completed with Python. Current technique is to describe a class and methods, it's inputs and outputs. Write unit tests for it then write the code blocks. Adjust testing if new methods or functionality are added. |
For our C++ code the target system will be an embedded system. |
VS Code (primarily), Visual Studio, TI Code Composer. |
31-60 seconds |
Have used Google style guide for Java. Have used Microsoft's C# coding conventions. |
When it begins to take on too many responsibilities. |
Currently code review is done by person marked as approver of the open pull request. |
30 |
55 |
15 |
I love problem solving with code. |
Inconsistent failures and edge cases. |
It is a method of writing test cases against requirements first before fully developing code. |
A skill refresher. I find I always learn something new, I am looking for that here. |
Show
|
| 2 |
5 |
C# |
Java, Python |
JUnit, Pytest |
Always looking to continue learning new languages and always eager to be working on a development project to keep my skills fresh. |
N/A |
N/A |
VS Code |
1-5 minutes |
N/A |
Difficult to understand what it's doing |
Pair Programming |
4 |
2 |
4 |
Designing solutions to complex problems and seeing the end product in action. |
Testing |
Red Green Refactor approach |
This course was recommended as good preparation for an upcoming project. |
Show
|
| 19 |
10 |
C# |
C, C++, Java |
GoogleTest, NUnit, JUnit |
I love watching basketball |
NUnit |
Windows and Embedded System |
Visual Studios and Visual Studios Code |
31-60 seconds |
We follow a standard found by our lead architect |
There are code smells such as it is calling multiple functions and too many nested for loops. |
We push onto GitLab and have our main architect review it. |
50 |
40 |
10 |
It is part of the building process |
Trying to figure out how to actually solve a problem |
We use it every day in our work |
To better our process in regards to TDD |
Show
|
| 3 |
3 |
java |
typescript |
junit, jest |
I love to challenge myself, in order to grow professionally. |
unit and e2e tests using jest and junit |
Linux and Window OSs. |
bitbucket, jenkins, AWS, SCA tools |
1-5 minutes |
Add unit and e2e tests to new code, all existing and and new tests should pass. |
When it does more than one thing (when there is part of the code that can be written as a separate) |
Conducted at the end of each sprint, any needed changes made and approve before story marked done. |
60% |
20% |
20% |
Solving problems, always learning new things, logical thinking |
none |
It assures software meets requirements, shortens dev time, |
To learn more about TDD and to be proficient with it, |
Show
|
| 1 |
5 |
C |
Python, Javascript, dabbled in C#, C++, Rust |
None really, have used a simple test harness written by colleague, not strictly for unit tests |
I spent most of my youth playing World of Warcraft. |
Running the code on hardware (or a dev board if no hardware) and observing the behaviour. If I encounter a problem as the device runs I will single out a function or functions and maybe write some code to explicitly test them. Very much test-after. |
STM32 micros, typically for IoT style devices. |
STM32CubeIDE, Git. |
31-60 seconds |
We use a subset of Barr Group embedded C standard. |
Doesn't fit on a page (need to scroll screen to read it all). |
We have a rough procedure for performing code reviews but it isn't really done. |
49 |
2 |
49 |
Creating something,solving a problem.Seeing something you've spent effort on/struggled with working. |
Pain of something not working or breaking intermittently and not knowing why, esp. under time pres. |
It involves writing tests before writing code. |
Write better code; not having obscure bugs pop up late in a project and blow out timeline and stress |
Show
|