| 3 |
9 |
C |
Assembly, C++, Python |
cpputest, unity, pytest, custom |
I like rock climbing and electronic music. |
As ASPICE mandates (3 layers) |
It's a Bluetooth SOC. |
cmake, clang goodies, CPU supplier toolchain, IBM DOORS, Azure devops, etc. |
Under 10 seconds |
MISRA 2012 |
When our HIS metrics tell us so |
Formally, there is a checklist. Practically, we use our engineering judgement. |
2 |
7 |
1 |
Doing actual development and solving engineering problems |
Paperwork, wrangling infrastructure, strict processes |
You have unit tests as the first consumer of your code. They sort of work as requirements. |
We are adapting TDD on the company level. Always nice to learn something new. |
Show
|
| 3 |
10 |
C |
Python, basic C++ |
N/A |
I hope this training goes well |
using the bluetooth qualification tests and verifying manually in specific instances |
an embedded firmware system written in C running on target |
visual studio code as an IDE, cmake to build the firmware, ninja as a compiler |
Under 10 seconds |
loose, I am not sure we have a formal document at least that I have seen. But generally consistent |
when a function generally does more than one large task, or can't be described succinctly |
code reviews happen in PRs by the people reviewing the change, rather informally done asynchronously |
50 |
20 |
30 |
I like the "puzzle solving" aspect, as well as knowing that everything happens for a reason |
wasted development and broken code as a result of not understanding the whole complicated system |
I am aware that it is a practice where the test case is written before the code is changed to pass |
Because I was invited mostly. I would like to learn about TDD, but unsure how I will actually use it |
Show
|
| 4 |
12 |
c |
python
java
c++ |
ceedling
unity
pytest |
I don't really know if I want to do TDD. |
depends on the project.
- on target with unity
- off target with ceedling
- system level integration tests |
it varies
- arc core (ASICS and general SoC)
- risc V core (ASICS)
- some assembly (custom ISA) |
ci/cd pipelines
clang format/tidy
code coverage tools
MISRA etc...
requirement management |
31-60 seconds |
allman style. strict naming scheme for everything. enforced automatically somewhat. |
cyclomatic complexity is above threshold. Also gut feeling. |
lacking. It seems we never have enough time for good reviews. |
5 |
3 |
2 |
solving hard problems and making hardware do stuff. |
tedious stuff and busywork sometimes. AI has been helping with this. |
i learned the process in college. haven't applied it in my career at all. tests first... |
we are trying TDD with latest development effort. |
Show
|
| 2 |
20+ |
C |
Objective C |
Unity |
I actually enjoy writing tests! |
Manually
Unity |
ARC MCU |
vscode
clang-format
|
Under 10 seconds |
Company defined |
When it tries to do more than 1 thing |
PRs must have 2 approvals |
20 |
40 |
40 |
Solving puzzles. Learning new stuff. |
Pretty much like it all |
Test Driven Development |
To learn TDD. |
Show
|
| 5 |
35 |
c |
C++, python, ruby, perl |
Internally developed and the Bluetooth qualification test suites |
I like challenging technical problems and enjoy hardware and software development. I'm interested in this topic look forward to learning more about it. I think these courses often add too many exercises mostly to fill the allotted time. |
Unit testing, integration testing, qualification tests, and with an internally development test system. |
Embedded ARC |
VS Code, Metaware development environment, python |
31-60 seconds |
Coding standard is documented and generally followed. |
There are many factors, does more than a primary task, multiple screens of text |
Code reviews are preformed on an informal basis, but are required. |
25 |
40 |
35 |
The creative process, seeing the successful outcome, and challenging problems. |
Testing |
Basics |
I was signed up for this training class. |
Show
|
| 2 |
20 |
C |
C++, Python |
Unity |
Working on different protocols and embedded systems. |
Unit testing, functional testing, manual testing, regression testing |
wireless embedded systems |
VSCode, Linux, IDEs |
11-30 seconds |
Clang and standard agreed with the team |
multiple functionalities happening |
peer reviews and SME approval |
5 |
6 |
8 |
Get to develop and see new features working. |
manual testing of the same features when the testing should have been automated. |
writing test cases first and then developing software against it to pass the tests. |
company organized it |
Show
|
| <1 year |
10 |
C (Embedded) |
Python, C++, Rust, Bash |
CMocka, Twister, Unity, Pytest, and in-house Rust/Bindgen C framework. |
I'm a big sci-fi/fantasy reader, love Sanderson books. Also big into video games and going to concerts! |
Ideally, unit-testing off target HW, if "required", on HW. Integration testing using our QA team's harness, then any BLE SIG tests. I also will do some basic personal smoke testing of my features iteratively. |
ARCv2 ASIC running BLE stack. |
VS Code, GDB, gcc toolchain when building on Linux, Docker, Metaware toolchain when built on target. |
5-30 minutes |
I try to prioritize readability and testability over any arbitrary cleanliness/conciseness. |
If a function can be broken into multiple logical chunks or operate on semi-independent data. |
First, I review over the intent of the change, then I go over other things like readability, tests. |
40% |
30% |
30% |
Just a fun way to solve problems, feels very math-y to me which is a passion of mine. |
Resolving/investigating extremely long linker dependency chains. |
I've learned about it in the past and tried using it on smaller personal projects, not professionall |
Generally our FW team could attain a higher degree of testing discipline. |
Show
|
| 5 |
30 |
C |
Python, C++ |
Unity, Google Test |
I'm a beginner photographer, mostly landscapes. And I have an interest in learning the Rust programming language. |
Bluetooth Protocol-level test suites |
System-On-Chip with Bluetooth stack |
CMake, cross-compilers, debugger, protocol analyzers, conformance testers |
11-30 seconds |
C99 compliant with an increasing interest in Automotive Quality initiatives (MISRA, code coverage) |
No company mandated directive here, however, it should perform a narrowly-defined single output |
Reviews performed thru Azure DevOps with two reviewers required to push a PR. |
20 |
50 |
30 |
Solving problems and delivering robust solutions for our customers |
Ambiguous requirements and unrealistic expectations |
A little exposure in regard to writing negative UT followed by positive UT and, finally, code. |
Training was recommended by the Swiss team and a desire to improve product quality |
Show
|
| 0.125 |
6 |
C |
Java, C++, Python, R |
n/a |
I am an intern, currently attending UT-Austin CS. |
Test cases |
EM made SoC |
VS Code, WSL2, Confluence |
1-5 minutes |
Consistent variable names, enough comments modular code. |
More than 30 lines around. |
n/a |
8 |
8 |
10 |
I like implementing different features given constraints and considering tradeoffs |
Build times and having to wait between testing. |
n/a |
Required by company. |
Show
|
| 3.5 |
40 |
C++ |
ASM, C, LUA |
GTest
Many Proprietary |
I have worked in games and defense - simulation for 30+ years. |
Combination of unit and functional tests |
Game Engine |
Visual Studio
VS Code
Visual Assist
Perforce
Proprietary |
11-30 seconds |
Not sure what you want to know? |
When I have to scroll back up to the top of the function |
We have them for every checking from a selection of SME's team members |
60 |
30 |
10 |
Solving problems |
typing |
I have developed TDD culture within new software teams in the past due to project SDLC requirements. |
To see if this kind of training is useful for my teams |
Show
|
| 0 |
30+ |
C/C++ |
HLSL, C#, Python, assembly |
Some, I forget the names. |
I seem to believe in (and have had great success doing) a rather different version of agile development to most people. |
Ah-hoc playthroughs. |
PC games, typically low-end machines e.g. older laptops. |
VisualStudio + in-house tools. |
11-30 seconds |
Thorough - half of C++ is disallowed, strong typing heavily encouraged. |
No such thing. |
2-4 people review with discussions. |
30 |
30 |
40 |
Shipping to people. |
Not much. |
Quite a bit. I have seen it taken way too far. |
Because I was asked to. |
Show
|
| 15 |
28 |
JS |
Python
c++
Actionscript
java
Various embedded |
FlexUnit
JUNIT
Mocha
Puppeteer
Cypress |
I run/design/play tabletops and LARPs |
Mostly manual with occasional integration/unit testing |
Internal Engine Tooling |
VS, VSCode, Intellij |
Under 10 seconds |
Strict coding standard defined by riot. Otherwise community standards for the language. |
Preferred is 20 lines max, 1 screen as an extreme. Anything over is too long |
Custom tool for code reviewws |
2 |
3 |
5 |
Discovery and deep learning |
Inconsistent standards |
Used to teach Flexunit testing with a focus on TDD. Helped write flexunit 4. |
Understand c++ testing space better |
Show
|
| 7 |
20+ |
C++ |
Python
former fullstack .net |
GTest
Pytest
xunit
mspec
specflow |
I'm looking forward to this class |
n/a |
PC |
Jetbrains
Visual Studio |
1-5 minutes |
internal standard that documented and shared |
the length of it. Should be ~30 lines or less |
All check ins require a code review |
6 |
1 |
3 |
Writing code |
stepping through code to troubleshoot |
Read several books |
I put it all together and I'm a big believer. |
Show
|
| 16 |
24 |
C++ |
C, Python, Lua, ASM, JS |
Homespun |
I've never made anything but games since the Playstation 2 era. |
Mix of manual and unit tests |
PC |
Visual Studio |
11-30 seconds |
We have a strong coding standard focused on consistency and readibility. |
When it does 2 or more unrelated tasks, or requires a sitemap to keep track of. |
Mostly used to spot architectural inconsistencies and standards deviations. |
60 |
10 |
30 |
Helping artists and designers make cool shit. I like building things in general (physical as well) |
Nothing glaring stands out in particular. |
High level concepts, but I've been in Old School games too long to have much experience with it. |
Boss thinks it's a good idea. (I don't particularly disagree, but I wouldn't have prioritized it). |
Show
|
| 5 |
30 |
C/C++ |
Python, Rust, Javascript |
Google test, built in rust test harness, some python ones I don't remember |
I do HDL verilog development as a side project which in professional settings is heavy focused on TDD. |
Usually running in a debugger. |
Windows and Mac PCs |
Visual studio, neovim, vscode, xcode. |
1-5 minutes |
I pay attention to the parts that focus on safety, clarity and debuggability. |
Length doesn't matter, complexity is what is important. |
When reviewing I focus on potential issues/bugs and maintainability. |
20 |
30 |
50 |
Challenging, problem solving. |
Not making progress. Boilerplate. |
I hear a lot of zealotry, but have little real world experience with it. |
A bunch of engineers from a central team that I depend on are doing it so I wanted the context. |
Show
|
| 4 |
12 |
C++ |
Python, C#, TypeScript |
GoogleTest, PyTest, JUnit |
I'm a big fan of ducks and can make a decent quacking sound |
Primarily manually with some unit tests |
Cross-platform for Windows and macOS |
Visual Studio |
11-30 seconds |
Standard heavily opinionated C++ |
Too many responsibilities or raw lines of code |
Often asynchronous, sometimes used for spotting bugs as opposed to purely for alignment/sharing |
5 |
2 |
3 |
Instant feedback, much lower risk of breaking something physical or expensive while iterating |
Setting up a new dev environment and forgetting all your macros, keybinds, etc. |
Red, Green, Refactor |
Want to learn how to adapt a legacy codebase to make software dev easier, too many regressions now |
Show
|
| 8 |
35 |
C++ |
C#, python |
tcl/tk, gtest, many custom ones |
I lived on a sailboat for half of my childhood. |
gtest |
windows/linux/osx/ios/android |
Visual Studio |
11-30 seconds |
It is quite extensive, but does allow for exceptions where pragmatic. We automate many checks. |
When it's not easy to understand. |
Every change is reviewed, but not blocking. |
7 |
1 |
2 |
Understanding a system and creating it, adding to it, fixing it, making it faster, or deleting it. |
Hype cycles. |
It should be capitalized :)
I did a course on it a long time ago, but have not used it much. |
My manager suggested it, and I haven't done a course for a while, so why not? |
Show
|
| 12 |
40 |
C++ |
For work, SQL |
Nothing extensively |
|
Initially, personally against requirements. Then some basic CID tests, then via games played on internal regions, then more extensively via Public Beta games. |
All flavours of PC/Mac and mobile. |
Visual Studio |
31-60 seconds |
Extensively documented and mandatory. |
If its a page long, its probably getting too long. Depends on functionality. |
1 - 4 reviewers required per change. Reviews via Swarm |
50 |
10 |
40 |
Getting code working |
Code not working due to opaque infrastructure bugs |
Just that its test driven development. |
Because I was enrolled in it. |
Show
|
| 12 |
40 |
C++ |
Pretty much anything but I have a soft spot for Perl |
gtest but there was probably some Java ones I forget about |
I have a rabiit |
Unit tests, functional tests, manual QA |
Desktop and mobile devices |
Visual Studio
Qt Creator
Emacs
Renderdoc |
Under 10 seconds |
Well documented on the internal wiki |
when it does more than you can describe in one sentence |
Perforce Swarm |
5 |
1 |
4 |
Solving problems - every new task is a puzzle that needs to be solved with efficiency and elegance |
Short term thinking, fragility, and recently the "AI" push |
Tests first - they are expected to fail, and then write the implementation until the tests pass |
My manager signed me up |
Show
|
| 3 |
14 |
C++ |
Python
C# |
We have a CID system that runs some basic tests |
I like the P-38 on your Logo, just made it out to Oshkosh airshow last year for the first time. Used to fix avionics on the A-10, and would love to get my pilot license some day. |
Run through a series of test in editor and game to confirm expected behavior, and identify any edge cases |
We develop for PC, Mac, Android, and IOS, but primarily target PCs. The codebase is > 18 years old |
Visual Studio, RenderDoc, Sublime Text, |
1-5 minutes |
We've got a pretty lengthy doc covering everything from syntax to use cases |
Gut instinct, or when it gets frustrating to work on |
We use Swarm, and Peer review our code, requiring at least one SME sign off |
3 |
1 |
6 |
Solving problems and exposing new functionality for artists and designers. |
Managing constantly shifting priorities while trying to debug a bunch of loosely documented code |
You design a test for the thing you want to accomplish, write code to pass the tests, repeat |
Our manager scheduled it labeled as Unit testing. I'm interested in how to better test our code. |
Show
|
| 3 |
8 |
C++ |
Python
C# |
Catch2
Google Test
pytest |
I like playing League of Legends. |
Scenario testing with scripted events, verfying certain outcomes.
Automated testing with mouse / keyboard interactions. |
We test video game functionality and windows programs. |
Visual Studio |
5-30 minutes |
We have a shared standard for C++. For smaller utils there isn't a qualified standard. |
It's usually done via best judgement. |
We have SMEs look at code as well as TLs. We have a system for people to become reviewers. |
60 |
15 |
25 |
Empowering users with the tools they need to improve the content within our game. |
The finnicky moment of turning an idea you know should work into paper. Reproducing complex bugs. |
Writing the failing test first and then writing code. |
A requirement from my initiative. I'm looking for ways to apply methodologies in hard to test areas. |
Show
|
| 2 |
12 |
C |
Python |
CppuTest |
Got into embedded software developemtn when doing my bachelor studies; fell in love with it and been doing that ever since. I like when things interact with real world and you can see the outcome.
Love to read books |
Static analysis, system test, integration test |
Low power MCU, modem, RF chip |
Cmake, gcc compiler, vs code, st-link, cubemx programmer |
1-5 minutes |
I mostly follow coding standard released by Michael Barr, Embeded C coding standard |
It is longer than 100 lines |
It is mostly to check if changes are made in line with acceptance criteria |
30 |
20 |
50 |
Solving problems and seeing their solutions in real world environment |
Probably mostly the documentation part |
I'd say pretty much nothing, bare minimum |
I believe TDD is the future where most of the code will be generated by AI |
Show
|
| NA |
12 |
C/C++ |
Python, Ruby, Javascript |
Unity, CppUTest |
I'm an electronics engineer and a musician, interested in embedded systems and real-time applications. |
Running it on the target machine and exercising it manually or hard coding stuff to test corner cases.
I've written some developer tests using CppUTest and Ceedling on different projects, but they are very immature and there are too few of them. |
Main project is 32-bit arm embedded linux device and there is a side project based on a dsPIC device |
CMake, GCC, XC-DSC, VSCode |
1-5 minutes |
Undefined |
When it does more than its name says. |
Just quick looks at PRs. |
30 |
35 |
35 |
The satisfaction of seeing that I can tell a computer with some precision what to do. |
It's difficult to find a job in an area you really love. |
It's a practice for building software incrementally guided by tests. |
Personal interest. |
Show
|
| 1 |
17 |
Python |
C, C++ |
CxxTest |
I’ve been programming for a long time, but never specialized in one language. I’d love to focus more on writing clean, functional code and planning for potential issues before coding. |
Using test suites with CxxTest |
I don't understand the question |
Microsoft Visual Studio Code
Microsoft Visual Studio |
1-2 hours |
MISRA C++ with IEC 61508 SIL2/4 safety standards |
"Intuition" (no more than 50-80 lines) |
Tools: QAC++ static analysis, CxxTest framework, Make build system, integrated regression testing |
60 |
10 |
30 |
I love the feeling of building something from scratch and seeing it come to life |
Spending hours debugging just to find the error was a tiny typo—so frustrating! |
Nothing… my mind is a blank canvas ready to learn! |
I’d like to be more efficient and have a more preventive attitude rather than a corrective one |
Show
|
| 4 months |
3 years |
C++ |
C, Python |
I use CxxTest with custom stubs for unit testing in embedded C++ projects. |
I work on embedded C/C++ development for safety-critical railway systems.I enjoy learning new practices to improve reliability. |
I run automated unit tests using CxxTest and stubs. |
We develop the ERTMS on-board system for railway applications. |
I use Visual Studio Code and Visual Studio 2022. |
1-5 minutes |
We follow MISRA C/C++ guidelines and internal rules and use tools like QAC++ to enforce compliance. |
If QAC reports an error (e.g., excessive length or complexity), the function is considered too long. |
We make peer reviews for every change |
50 |
30 |
20 |
I enjoy solving complex problems, creating reliable solutions, and seeing code work in real systems. |
I don't like managing complex dependencies and debugging issues or waiting for long build times. |
I know TDD means writing tests before code, ensuring requirements are met and reducing defects early |
My company proposed this training to improve testing practices and adopt TDD for our system. |
Show
|
| 2 |
26 |
C/C++ |
C#, python |
cUnity, cpputest, gtest, cxxtest |
I've been working for 20 years with embedded systems in risk-oriented developments. Unit Testing was a game changer for me. I do not fully agree with everything TDD proposes, but I successfully integrated several approaches into my development cycle. |
First unit testing, then integration tests (automatic when possible), and finally manual system level partial testing (full system level verification and validation is done by other departments). |
Usually embedded systems (RTOS or linux), but sometimes PC |
Visual Code, makefile, cmake, propietary compilers, git, QAC static analyser |
1-5 minutes |
Primarily MISRA-C/C++, plus in-house rules for defensive programming |
It does too many things or you have to scroll to see all of it |
Our processes include peer reviews before the feature branch is merged. |
30 |
30 |
40 |
it is fun!! |
When you spend days and days looking for a bug you could have avoided |
I've read a few books, including "Test-Driven Development for Embedded C"
|
I am not fully convinced with the TDD approach. Looking for more in deep learning. |
Show
|
| 1 |
8 |
C |
C++ |
CxxTest |
|
Using unit test and developer tests. |
|
Programming using Visual studio code and compiling debug code with MSVC/MSVC++ |
31-60 seconds |
|
We have a QAC program that sets a limit on the maximum number of lines that a function may have. |
|
5 |
2 |
3 |
|
|
I took a course on TDD at university. |
I feel that I can improve my testing skills |
Show
|
| 20 |
27 |
C++ |
C, python |
boost.test, catch, catch2, xUnit, pytest, gtest/gmock |
I work remote, somewhere in the middle of the Atlantic. |
- Primarily unit tests (in gtest)
- Secondary: system tests using a python based framework (built on top of pytest).
- Manual tests on running system |
Distributed embedded system (but no real limitations to memory allocation or exceptions). |
IDE (Clion+IDE), sourcetrail, main project toolchain (debian12 gcc).
Codescene, Coverity, copilot |
1-5 minutes |
C++17 |
Starts to feel too complex (over a screen, too many control-flow branches). Codescene also warns. |
Our agile team is heavily invested in code reviews. |
60% |
30% |
10% |
Allows me to express my creativity, feels like LEGO for adults (it we get the modularity right). |
Lagging tools (C++ was stale for too long), debugging, memory corruption ... |
I have been using it for over 15 years, also am aware of ATDD (not using it now) |
Got asked by management, personally hoping to learn (or refresh) my knowledge as well. |
Show
|
| 11 |
25 |
c++ |
c, python, shell script |
google test |
I'm looking forward to this training. But I'm not much of a morning person, please bear with me :) |
unit test, integration tests, system tests |
Card Application SW running on zync ultrascale arm cortex core processor |
bitbucket, eclipse, ms code, various plugins |
1-5 minutes |
company specific |
does too many things |
in bitbucket. Required review and approval for all PRs |
30 |
40 |
30 |
The challenge and collaboration involved |
too many bugs |
Not much |
Company enrolled me but I am looking forward to learning something new |
Show
|
| 9 |
20 |
C/C++ |
Python, Java |
Google Test |
Married, two kids. Recently started to run. Benfica supporter. |
Management Framework Integration Tests (MFIT), python scripting end2end tests.
Unit Tests (Gtest) |
Debian OS for Telecommunications |
VSCode, with some extensions |
1-5 minutes |
Format is enforced by AStyle.
Should have comments, Doxygen compatible.
Code coverage test 75% |
It is bigger than my editor in VS code :) |
At least one reviewers must approve before delivery, and none can disapprove. |
20 |
60 |
20 |
See the things I created come to life. |
When it starts to be mechanical work. No thinking. |
Test Driven Development, is when you write the tests from the requirements prior to the code. |
Check if I can get some tools to (change/bring some insight) to my team. |
Show
|
| 6 |
20+ |
C |
Python |
CppUTest |
I dislike answering survey questions. |
Unit tests and manual testing. |
A55 and Nordic processors running Zephyr. |
VS Code, gcc, git. |
11-30 seconds |
https://barrgroup.com/embedded-c-coding-standard with some modifications. |
If the function name can't capture all of what the function does, the function is probably too long. |
All pull requests are reviewed by another person to check basic functionality and completion of DoD. |
60% |
20% |
20% |
Solving problems. Writing code that is clear, easy to use, and easy to change. |
Shifting priorities caused by poor planning or lack of focus/commitment from the business. |
I familiar with the TDD process and have applied it to simple examples. |
I want to learn how to write good unit tests and see if TDD will work for me. |
Show
|
| 1 |
15 |
C |
C++, C#, Python, Javascript |
AceUnit, CppUTest, Zephyr's ZTest |
I like hiking outdoors. |
TDD |
Battery-powered, embedded ARM A-core device |
VSCode and open-source compilers |
Under 10 seconds |
Pulled from some standard somewhere. Seems pretty typical. |
When I can't see everything it is doing in one screen. |
Quick checks of functionality and making sure the objectives of the task/story were accomplished. |
40 |
40 |
20 |
It is fun to see the realization of objectives come into being. |
Nonsensical directives being forced on a design, without justification. |
I've taken this course before, about 7 years ago with a different employer. I've practiced it since. |
Refreshing TDD. Hoping to get co-workers on-board with it too. |
Show
|
| <1 |
9 |
C |
Java
C++
C#
Python
VHDL |
None |
I come from the defense side of embedded systems, so I've had a lot of experience with waterfall development. I am overwhelmed by the speed and complexity of the private sector, but am excited to become better under the pressure. |
Build it and run it. |
nRF54 and nRF52 devices and iMX93 devices. |
vsCode
Zephyr
West
|
11-30 seconds |
We have a coding standard that we follow pretty well |
Typically if a function goes longer than a page, I take a second look to see if it can be "helpered" |
We have a pull-request system and reviews must be done. |
3 |
2 |
5 |
Making things work and building cool embedded projects. |
Build issues. Getting stuck debugging when no solution can be found. |
I understand its power and utility. I've heard it talked about. I have never seen it executed. |
My team is doing the class together to hopefully start doing TDD for all of our projects. |
Show
|
| 4 |
7 |
C |
Python
JavaScript
C#
CMake and Linux scripts (if they count) |
A little bit of CPPU Test |
I'm always happy to learn new ways to improve my processes and write better code |
Using prints and testing behavior |
Embedded system running Zephyr |
VScode
JLink
StateSmith |
Under 10 seconds |
Largely based on https://barrgroup.com/embedded-systems/books/embedded-c-coding-standard1 |
I don't like when a function gets longer than the vertical space on my screen with some exceptions. |
All code is reviewed before merging to master. Code is reviewed and tested |
50% |
25% |
25% |
I like seeing things come together and work. Writing code I'm proud of is also a big plus |
Trying to get 3rd party things working and fighting with their documentation or code. |
I understand the idea of building and testing smaller chunks of code incrementally |
I think TDD will be useful. Slowing down progress at work to learn it hasn't felt feasible until now |
Show
|
| 3.5 |
8 |
c |
python |
cpputest |
I am a hard worker. I would love like to take up more challenges at work. |
using shell on zephyr |
imx93 platform running Zephyr RTOS |
VSCode, GIT and bitbucket |
11-30 seconds |
C11 |
When no. of lines are more than 100 |
Average 50 hours we spend for every sprint of 2 weeks length. |
10 |
5 |
5 |
The joy of solving problems using coding. |
Testing |
I believe development and testing goes hand in hand. |
catch the bugs earlier so that our customers will be satisfied about our product quality. |
Show
|
| 3.5 |
15 |
C |
C#, python |
cpputest, nunit |
I care a great deal about the quality of my work. |
manually |
ARM Cortex-A55 running Zephyr RTOS, and an ARM Cortex-M device (BLE radio) also running Zephyr. |
VSCode, gcc, git/bitbucket |
11-30 seconds |
Based on Barr Group's Embedded C Coding Standard, with a few modifications. |
Coding standard says "maximum of 100 lines" with exceptions. |
Code reviews are done manually for every pull request. |
25 |
50 |
25 |
Problem solving is deeply fulfilling. Continuous learning. Pay. |
Code reviews, waiting for builds, vague/misleading build errors. |
I've taken your in-person class before (about 8-9 years ago) when I was at Cirque Corporation. |
Someone mandated that we all use TDD, but they don't want to teach it. |
Show
|
| 3 years |
20 |
Java |
C,C++ Python. |
JUnit |
Despite my role as Sr SW PO,I continue to try involving myself in development. With the training it is an opportunity to change our work of developing by adopting TDD |
Iam not doing currently heavy programming. But I did test using automated unit tests with JUnit |
TDD as mindset to develop embedded app. |
Visual Code,
Unity... |
1-5 minutes |
we defined internally coding standard that every developer should follow.. automatic checks. |
function that is doing more than what is expected. |
using primarily Pull request. |
XX |
XX |
XX |
Use of design Pattern to model a use case. |
Lack of flexibility. Lack of separation of concerns. |
Using it during my previous projects.This is the reason of introducing it in our development |
TDD for embedded system. |
Show
|
| 1.5 |
9 |
C |
C++
C#
Python |
Specflow
RobotFramework
GTest |
Got into programming due to robotics. Making something in the real world move was incredible, led to embedded systems, LEDs are almost as good :) |
Blackbox System Level Test |
Multiple Cortex-MX devices |
VS Code + extensions
Salea |
31-60 seconds |
Try to adhere to Google C++ Style Guide, but as far as standard I would call it.... loose. |
It depends on the context but generally for me its when there are too many exit points. |
I am the only Embedded Developer on my team currently. I need better tools for test/etc |
50 |
10 |
40 |
Solving puzzles and interacting with the real world. |
Unclear legacy code, Bad Debug tools, Environment setup/issues
Really debugging unexpected issues |
A little. Write tests before starting, develop, pass tests.
1st module of self-paced |
To make my own coding more reliable and have something to hold up for checking my own work |
Show
|
| 3 |
30 |
BASIC |
C, C++, Python, Java, Javascript, GDScript |
VectorCast, Unity |
Used to work in SW dev in aeronautic and space fields of application with highly constrained standards. |
Printf statement to follow-up code execution, toggling GPIOs when performances are requested.
Used VectorCast for unit and integration testing (long time ago). |
ARC CPU with few KBytes of memory. |
Synopsys ARC toolchain and debugger.
Git for source code management.
Digilent Digital Discovery |
11-30 seconds |
MISRA C 2012 along with custom internal coding rules. |
Cyclomatic complexity, and personal feeling. |
Pull requests done when a branch has to be merged within the develop main branch. |
30 |
30 |
40 |
Innovative tasks, algorithm elaboration.
|
Experiencing non deterministic bug that arise very seldom after quite a very long time to reproduce. |
Almost nothing. |
To foresee how TDD can help reducing test and debug time, or if we can be more efficient. |
Show
|
| 3 |
10 |
C |
Python, C++ |
VectorCast, Unity, Ceedling |
I like playing tennis and mountain biking |
We can execute unit tests on the target or without the target.
|
Bluetooth SOC using ARC CPU and our custom IPs.
We write all the drivers and integrate a BLE stack. |
Metaware compiler/debuguer with Visual Studio Code |
30-60 minutes |
A coding standard is defined for all the developers in our team |
No detection for that in our development environment |
Using Azure Devops pull request to make the code review |
40 |
40 |
20 |
Designing, Coding and Testing software are interesting part in software development |
Making the documentation for a user level and managing requirement could be difficult to handled. |
Not so much, I guess it is a methodology to develop software by defining test first. |
To learn methodology to improve the development of software |
Show
|
| 3 |
30 |
C |
Objective-C, C, C++, C# |
Ceedling, CMock |
I like traveling and discovering the world. |
Unit Tests, we are able to run them on the target or without the target.
Regression (Integration) tests.
We write python tests which send HCI commands over SPI to the target. |
Bluetooth SOC using ARC CPU and our custom IPs.
We write all the drivers and integrate a BLE stack. |
Metaware compiler/debuguer with Visual Studio Code. |
31-60 seconds |
We have our custom rules that each developer shall use. |
We use LDRA, but in general it's up to the developer to try to write not complex functions. |
We use Azure DevOps and git for pull requests. |
30 |
50 |
20 |
Writing clean code, easy to understand and working well without any major trouble to make it working |
Using debuguer to understand the issue. |
We already use TDD but we want to be sure that we use it correctly. |
Increase my knowledges and use TDD correctly. |
Show
|
| 2 |
18 |
C |
Assembly, Python |
Unity |
I like assembly :-) |
Unity test on target.
We are slowly shifting to the Ceedling framework to run unit tests on PC. |
RISC microcontroller. ARC EM7D CPU. |
CMake, Synopsys ARC toolchain, VS code. |
5-30 minutes |
Not sure to understand this one. |
>80 lines |
Pull request reviews within Azure Dev Ops.
At least 2 approvals, resolve comments, test passing. |
45 |
10 |
45 |
Deliver robust and reliable software.
Enable the client to make great products. |
Dependencies between software modules. |
I read the bee book :-) |
I asked for it. I want our software to be better tested. |
Show
|
| 8 |
20 |
C |
Python, C++, C# |
Google Test and Unity (Throw the Switch) |
I'm not coding on a daily basis... mostly doing proof of concept. Some given answers might not reflect the team |
Unit Test (unity), integration tests (Python), code coverage currently performed on FPGA with LDRA, moving to GCOV and CMock. |
Embedded system based on ARC CPU for Bluetooth LE SoC. |
Metaware C Compiler/Debugger.
Python |
31-60 seconds |
Misra |
Cannot be read on a single screen (in landscape mode!) |
Done via Azure DevOps during Pull Request integration. |
30 |
40 |
30 |
It's creative! |
bad architecture might have a cost during the development or in project (e.g., limited reusability) |
Write test first! |
Proposal from a team mate. This seems fantastic to strengthen our team for better code quality. |
Show
|
| 5 |
6 |
C |
Python |
None- brand new to unit testing |
I have a computer engineering degree. Then, I moved into analog EE world. Now, I’m a mix between the two. |
C: flash it onto an MCU , step thru with debugger until something goes wrong. In RTOS, hopefully with logging messages |
CC2340, MSP430, python is for automating my lab |
Visual studio + copilot
CCstudio |
11-30 seconds |
Unsure what this means, so I don’t have one |
Never considered this before; perhaps when too long to understand |
None, solo |
40 |
10 |
50 |
Pays the bills ;) , plus automating my lab makes life easier |
In an RTOS environment, I struggle to debug where specifically a race condition / fatal error begins |
Zero- we talked briefly about the idea of testing in chunks as you code |
Met you in a bar, I am very curious. I am young and new, and hoping to launch my first product |
Show
|
| 2 |
15 |
C |
C++, C#, Rust |
gtest |
Been coding for a long time in C, but only done TDD (self imposed) once. Keen to do it more often |
function and some gtest |
Embedded STM32's, esp's and nordic series of ICs. Bare metal, idf or Zephyr RTOS |
Jlink ultra, salea, scope, multimeter, SCA tools, lizard cognitive load |
11-30 seconds |
c11, MISRA |
lizard/sonarqube cognitive load review |
Mob review, AI supported and PR with context |
50 |
40 |
10 |
problem solving and new stuff |
difficult bugs and customers |
learning more about testing and changing my coding style |
Keen to try and change the way I code to enable TDD and general unit testing. |
Show
|
| 1 |
5 |
python |
r, julia, c++ |
unittest, pytest, nose2 |
not much to say, i just gym, surf and do exercise besides work, i do alot of research into ml as its my academic focus |
mainly ml code, so includes validating data pipelines, model performance, and reproducibility using the unit tests, integration tests, and metric based evaluations |
microcontrollers, embedded devices, edge ai accelerators and npus |
pytorch / tensorflow, huggingface, scikit, xgboost, mlflow, onnx, nvidia |
1-5 minutes |
clean, modular, pep-8 compliant, type hint, config driven designs, and seperation of concerns |
too long when it tries to do more than one logical task, over 40-50 lines approx |
focus on code clarity, reproducibility, data handling, evaluation logic. mix of software and ml |
50 |
30 |
20 |
the freedom, and creativity you can explore with code, ml a mix of machine learning and standrd code |
sitting on my chair too long, back posture issues mainly |
test driven development is where you write tests before writing the actual code |
want to expand c++ testing as i dont do any, just python |
Show
|
| 2 |
10 |
C++ |
Python, MATLAB, C |
None |
I like robots |
Manual, SITL, HITL |
Embedded linux or embedded |
VSCode |
5-30 minutes |
We have a coding style guide for C++ |
It becomes too confusing to interact with |
We have peer reviews by a senior person |
40 |
40 |
20 |
Iteration and problem solving |
Can be a bit tedious at times |
The tests come first before the development |
Was offered by company and sounded interesting |
Show
|
| 1 |
14 |
C++, Java |
C#, Python |
GTest, JUnit |
My favorite color is blue. I like space exploration. I'm introverted. I wish I did more AI projects like reinforcement learning. |
Manually... I wish we had a pipeline |
X86 laptop, or x86 NUC on a UxV |
Clion, VSCode |
1-5 minutes |
Clean code, very close to Google style guide |
Has more than one responsibility, or does not fix 1-2 screen worth of space. |
1 in process review at 50% completion, 1 at pull request with run testing |
50 |
30 |
20 |
Complex problems, lot of different solutions, making intelligent and automated things. |
Management over-promising then pushing us to the brink, not consulting us on time needed to deliver. |
A lot, worked at EPAM, tried it at workshops. |
I want to make a pipeline with tests at work, but the legacy project is huge and need best practices |
Show
|
| 0.66 |
3 |
C++ |
C#, Qml |
None |
I enjoy philosophy. |
Manual |
Platform? Windows/GNU+Linux |
IDE, clang-tidy |
Under 10 seconds |
No formal standard. Whatever looks robust, clean, elegant, with sufficient compromise to the ideal. |
Doing too many things at once. |
Good. Learning a lot from them. |
5 |
2 |
3 |
Art form of making things beautiful, elegant, robust, and clean. Seeing the fruits of your labor. |
The occasional bureaucracy. I enjoy being solo, breaking things to find the best way. |
Very little. Think of what the output should be, write the tests, then the function. |
Team lead/manager signed many of us up. |
Show
|
| 1 month |
roughly 20 |
C# |
C++, Javascript, Java |
NUnit |
I prefer design and collaboration to coding. |
I haven't really done much development work at my new company yet, so I'm not sure... |
Software running on a laptop, sometimes in areas where internet is spotty or non existent |
CLion |
11-30 seconds |
I haven't had much time to familiarise myself with it much yet |
Rule of thumb - if I have to scroll, it's too long. If it does more than one thing, it's too long. |
At least two people must review the code. The reviewer should test the code to ensure it works. |
40 |
40 |
20 |
The planning and problem solving. Finding an elegant solution to a problem. |
The grind - looking for hours to try to find a problem in code that is needlessly complicated. |
No code written without a test for it. So far love the theory never been able to achieve practically |
I like learning new stuff, and I was asked to. |
Show
|
| 0.24 |
20+ |
C++ |
C, Python regularly
Go occasionally |
CppUnit, GTest, Catch2, doctest, but not extensively or any of them. |
Most of my career has been in small companies and I'm usually drawn into leadership/manager roles. |
Occasional unit tests. By running the code. |
Mostly STM32 based boards. PX4 Autopilot. |
VSCode, Emacs occasionally. GDB, some of the simple SWD probes, STLink. |
11-30 seconds |
Still under development for the company, follow conventions/standards in frameworks we use. |
Personal preference. |
A team member or lead reviews a pull request. Not done as a group. |
80% |
5% |
15% |
It's the power to make machines do amazing things
It's satisfying to create solutions to problems |
Deadline pressure, poor documentation, and people who don't care. |
A read James' book many years ago. |
I want to have confidence that what I am creating will work. |
Show
|
| 2 |
5 |
At work C |
At home python and circuitpython |
CPP U-Test |
Love doing robotics |
I run it on the hardware and test for functionality |
Mostly STM32 |
Mostly STM32 |
Under 10 seconds |
None |
? |
Done more senior coders |
30% |
20% |
50% |
NA |
STM IDE bugs |
I took your class last year |
My boss signed me up |
Show
|
| 5 |
8 |
C and C++ |
Python, Visual Basic, PLCs(Siemens, GE, etc.), HTML/CSS/Java, C# |
Only self constructed so far with unity, started using c unit testing framework based on this class |
I have way to many hobbies and am constantly shifting gears. Right now I'm writing a Lovecraftian horror novel using Scrivener for my character write ups. |
Mostly through firmware level verifications with hardware to sus out edge cases. Core functions are identified and individual development tests laid out. This often happens after much of the code is written though. |
Low level firmware in microcontrollers (AVR,ARM, PIC), but also GUI dev, webservers, embedded |
STM32 IDE, Microchip Studio, Visual Studio, Espressif IDE, Arduino IDE, MPLabs |
5-30 minutes |
None for formatting, but we follow an Azure DevOps layout using GIT |
When it doesn't compile in my 2KB Atmel chip |
Code reviews are organic and change from project to project based on available senior developers |
50 |
10 |
40 |
Every puzzle is unique, but they get easier and more complex solutions present themselves over time |
Getting stuck in a bubble alone while the team is testing |
I know our Embedded/software personnel are adopting it based on wingman training |
I am an electrical engineer with a hodge podge of code background. I want to become professional |
Show
|
| 0.5 |
15 |
Python |
C#, C++, Rust, Java, Fortran |
Rust test, pytest |
- |
A mix of unit tests and manual testing |
- |
VSCode, Visual Studio |
11-30 seconds |
- |
- |
- |
4 |
2 |
4 |
- |
- |
- |
- |
Show
|
| 1 |
4 |
Python |
JavaScript, C, Java, C++ |
Pytest, Unity (C) |
I just graduated from university |
Writing unit tests, integration tests and end-to-end tests |
N/A |
VSCode |
11-30 seconds |
Good naming conventions, modular programming |
When it becomes too difficult to understand/maintain/debug |
Talking through with another developer |
7 |
1 |
2 |
Seeing the good flow/structure/design in action. I like object-oriented programming. |
Errors |
Writing tests as a means to develop code. If the test fails, the code is wrong. |
I want to learn more about C++ as I am a young developer looking to broaden my skillset |
Show
|
| 1 |
20+ |
C |
Python
Go
C++
Octave/Matlab
|
Catch
CppUTest
Unity
GoogleTest |
I have an above-average number of legs for a living human. |
Off-target unit-testing, on-target HIL tests. |
Distributed system with internal interfaces (UART), external Debug CLI. hard realtime. |
IDE
Code coverage
Lint
|
30-60 minutes |
Non-existent. I'm trying to show best practice. |
It doesn't fit in my head. |
Ad-hoc and retrospective. |
40 |
10 |
50 |
Interacting with the physical world |
Poorly scoped definition of done. |
I've been practicing it for many years. I have a copy of your book that I evangelize about. |
I want to know what the baseline level of competence is in my team. |
Show
|
| 4 |
8 |
Rust |
C++, C, Python |
Rust std, Catch, GoogleTest, nose, pytest |
I have made a handy tool in Rust for building test spies from injected traits! Check it out on crates.io - autospy |
unit tests, integration tests, e2e tests, performance tests |
N/A |
Git, Jenkins, just, GitHub Actions |
Under 10 seconds |
Company quality standard, TDD, pair programming, trunk based development, CI |
When the name is vague, or it does more things than is easily conveyed by the function name |
We do not often have code reviews, we use pair programming |
20 |
60 |
20 |
Solving problems, making code neat, following best practice, learning new techniques |
Nothing off the top of my head! I don't like writing bad code, or not knowing what best practice is |
A fair bit, we use it extensively at PA, I often find the hardest part of TDD is the first test |
I want to be better at knowing that first test |
Show
|
| 0 |
40+ |
C/C++ |
Python F# Forth |
CUnit |
First PL was Fortran, most used C, best F#. |
Unit, integration & end-to-end tests, CI & manual |
Various embedded systems |
Various: VSCode, functional safety compilers, CI |
11-30 seconds |
In-house |
1. when the name no longer describes the behaviour, 2. when the code isn't readily intelligible |
Scrum |
25 |
10 |
25 |
Puzzle solving, learning |
Poor tooling, cargo culting, fanboyism, unrealistic deadlines, ship it anyway, obsession |
Very little |
Find out if it's worth anything - TD development OK, TD design ehhhh. |
Show
|
| 1 |
12 |
C |
C++
C#
Python |
GTest
Specflow
Robot Framework |
My first foray into programming was FIRST robotics where I learned about PWM controls and simple code. Fell in love with code that moves the world. Avid gamer, New 40k player, and read more fiction novels than i should :) |
On Device Black box testing |
Multiple ARM 32-bit systems. One multi core WiFi/BLE, one BLE, one low level hardware driver. |
VS Code
GDB
Various hardware debug tools
|
31-60 seconds |
Nothing Concrete. Loosely following misra, loose linux style, support doxygen with function comments |
When its doing more than the function name describes |
One Person Firmware team. Self Review and sometimes AI tools |
75 |
10 |
15 |
Evolving Challenges, learning new things, and seeing hardware do something with my code |
Legacy Code without comments or documentation. Maintaining Libraries for Legacy Hardware |
Usually used by Software Engineers, not necessarily firmware due to hardware constraints |
I want to learn TDD for better code practices and deliver coverage to gain trust outside my team |
Show
|
| 3 |
3 |
C |
python |
None! |
Hardware engineer that currently work as firmware/embedded engineer. |
build then test on target *_*, if it fails debug then repeat |
MCU based target |
IDE provided by MCU manufacturer |
5-30 minutes |
make the code modular.
readable.
follow best practices. |
It depends. but mostly if it does a lot of things |
there are almost no peer review, if I found something that may cause a problem I will fix it. |
30% |
10% |
60% |
Solving problems, the feelings if something works and fast development cycle unlike hardware. |
- Hardware dependence.
- If software was tightly coupled. makes refactoring a nightmare. |
TDD will:
make development more systematic.
be less debug time.
tackle problems as they appear. |
To get solid understanding of TDD, code refactoring and Enhance the design process |
Show
|
| 12 |
40 |
C |
Assembler |
Ceedling |
Most of my background is with "bare metal" programming. When I started programming in the mid 80's, MCU's were small and development tools were sparse. I coded only in assembler, and still find it hard to not worry about wasting bytes when I code. |
Always test behavior in system after code is written. Varies depending on function, but may include using printf statements or debugger breakpoints. |
Asset tracking device using ARM Cortex MCU |
GNU C Compiler, GDB debugger |
1-5 minutes |
We develop an agreed-upon coding standard before starting a project, but it is not enforced |
Probably when it contains elements that can be easily broken down into other smaller functions |
We use a web-based code reviewer to perform peer reviews before every commit to our trunk. |
60 |
25 |
15 |
Finding creative ways to solve problems |
Unrealistic deadlines, unstable requirements, and having too many constraints on how I code |
All I know about TDD is that tests are written before writing any code |
My boss signed me up |
Show
|
| 11 |
28 |
C++ |
C/C++/Assembly(arm)/Python |
gtest |
:) |
unit test (gtest), top level tests (system integratoin tests) |
huge legacy model (several million lines) that has existed over a decade, maintained by many teams |
c/c++/python/assembly |
5-30 minutes |
stringent C/C++ coding standards tailored by our team leads. |
more than a 'page' |
insanely strict; including a must-add test case |
25 |
35 |
40 |
problem solving and delivering value. |
digging through legacy code not undertstood by many |
nothing |
because I think i need to be good at appreciating testing and doing 'real and useful testing'. |
Show
|
| 1 |
19 |
C |
C++, python, matlab |
Custom, Google Test |
NTR |
Unit test, Integration Test, System Test, Regression Test |
x86, arm |
gcc, vscode, make, cmake |
31-60 seconds |
Readable, compact, Simple, Modular |
number of lines, number of goals, number of indents |
NTR |
40 |
20 |
40 |
Create |
The non linearity between the time spent and the impact. |
Swap the development flow and write test first, code second. Ensure quality standard designed aside. |
Explore the benefit for my team |
Show
|
| 2 |
4 |
C |
C, Type Script |
Tried using Unity |
nil |
Legacy code. Only perform UAT for any custom changes made to the code. Tried to implement Unit testing framework unity to the legacy code but didn't go well. |
We use 8bit Pic Microcontroller |
MPLAB X |
30-60 minutes |
I keep my code clean and descriptive by adding comments and using meaningful var and func names. |
When it is hard to understand at first look or when it is performing multiple functionalities |
nil |
5/10 |
3/10 |
2/10 |
I enjoy writing code that is later used in real world environment or that solves a real-life problem |
When the legacy code is hard to understand and has a lot of redundant stuff that can't be removed |
Recently introduced to TDD while working on unit testing |
To increase my skills and to use it in our legacy code as well as to implement it in new development |
Show
|
| N/A |
30 |
C++ |
Python, PowerShell,.NET, bash |
JUnit, Catch, GoogleTest |
Life-long learner. |
Unit testing, Integration Testing, End-to-End Testing |
Windows/AMD64 |
VS Code, CMake, MSVC BuildTools, GoogleTest, Git, OpenCppCoverage, BitBucket |
1-5 minutes |
C++ Core Guidelines |
When it does multiple tasks |
2-person review on pull-requests |
40 |
20 |
10 |
Creating |
Tooling issues in build and CI/CD |
Basic level |
Establish good practices for Embedded Development |
Show
|
| 13 |
25 |
C# / python |
C, php, C++, java, VB.net |
pytest, ceedling, MSTest, phpunit |
I don't write code as my job, but I manage teams that write code. This will be good for me to dive into development practices again. |
I attempt to do TDD, but sometimes revert back to not writing tests (particularly when I'm rushing) |
Desktop, Web, and Embedded Cortex M processor for an IoT application |
Simplicity Studio |
1-5 minutes |
Not officially enforced. |
If it is cumbersome to understand |
Every feature change goes through code reviews before merging with the main code branch |
50 |
20 |
30 |
I've always enjoyed problem solving, and i continue to learn new techniques to solve problems |
It seems too hard. I don't like repeating previous work that I've already done multiple times. |
It's a great method to delivering good tested code, but is a hard habit to maintain |
I signed up our team to try to improve our code delivery by finding bugs early in the dev cycle. |
Show
|
| 0 |
10 |
C |
C#, C++, Python |
NUnit |
I'm a USAF veteran and last week leg pressed 1027lbs for 3 reps |
NUnit |
WINCE, moving to Linux later this year
ARM based |
VS, VScode, Resharper |
11-30 seconds |
This company doesn't have a written coding standard. |
When I have to scroll to read (sometimes unavoidable) |
Jira ticket -> Dev-branch -> PR -> CodeReview |
40 |
50 |
10 |
Making things happen in the real world with lines of code. |
OOP obfuscation |
It reduces time finding bugs so we can code more efficiently. |
Suggested by manager, and maybe I can learn more OOP concepts too |
Show
|
| 10 months |
20+ |
c/c++ |
Rust, Python, C# |
Nunit, boost test, google test, catch |
I like sports, especially english premiership. Family man, love to BBQ and travel if I can. |
Rust unit test, Boost Test |
Linux based embedded system |
Rust standard tools, c/c++ linter etc |
5-30 minutes |
Company laid out standard for C++, Rust follow standard guide and guided by clippy. |
When stays from its purpose, get unreadable or hard to understand |
1) Does it follow the standard 2) Understand the problem 3) Evaluate the proposed solution |
40 |
20 |
40 |
I like creating and gives me satisfaction. I always learn and try to improve |
Standards for C++ changing constantly |
I know about testing software but my TDD knowledge is limited. I understand the concept. |
I really like improving and learning. We as a team suggested doing this |
Show
|
| 8 |
21 |
C |
python, vb |
none |
I'm more of a HW guy then a SW guy but like doing SW. |
in system testing |
various, mostly embedded MIPs |
various |
1-5 minutes |
standard practices |
good question, for me it would be nice if you didn't have to use the vertical scroll bar. |
use codecollaborator |
40 |
10 |
50 |
the ability to see changes and make devices do what you want them to do. |
hard to solve bugs or when the code does not do what you expect it to do |
some exposure to it, took a small course but don't actually practice it. |
I can see where it would be benefical, but I would need to be more efficient at it. |
Show
|
| 1 |
25 |
C++, Rust |
Python, shell |
Boost |
I love guitars. |
Unit tests and integration tests run in CI/CD pipeline |
Linux, running as a controller for attached devices |
VS code |
30-60 minutes |
Not sure what this is asking. |
It's not necessarily the length. A combination of length and complexity would be better. |
Reviews are done by team members before any code is merged into the development branch. |
4 |
2 |
4 |
Creating new things, and solving problems. |
Time wasted trying to debug issues. |
It is a methodology to create software where tests are written before the code. |
I want to learn how to effectively test code and have more confidence in my code changes. |
Show
|
| 7 |
20 |
C |
Qbasic, Megabasic, Rust, C++, Visual C, xaml |
None |
I play any instrument with a string on it. |
Sandbox functions - test functions by writing my own unit tests |
IoT systems |
MPLabX, Cypress Creator (PSOC), Simplicity Studio, Source meters, DMM, |
Under 10 seconds |
MISRA |
5 to 8 lines - give it a name |
Review changes with other programmers. Categorize into low, med & high risk changes |
30 |
40 |
30 |
Debugging/Problem solving. Making the electronics do something constructive. |
Working with previous, ill structured code |
Not much formally but have been doing it informally for years |
To improve my coding and unit test skills. also my supervisor signed me up for it. |
Show
|
| 3 |
10 |
c |
c++ |
cunit/gtest |
I am the agile transformation coach of this R and D org |
I am the coach and faciliator I am not actively programming :) |
x86 |
VScode |
1-2 hours |
there is one for Infinera based on Safe C |
> 1 screen |
we used to 2 level code reviews and prefer code |
5 |
5 |
5 |
building stuff that works |
that AI can do it now |
from what I have read on your blogs and few high level trainings attended |
because I am wanting everyone in my team to develop this best practice and culture |
Show
|
| 20 |
25 |
c++ |
c,python,perl |
gtest,cppunit |
I like to work with wood |
unit tests or python scripts |
embeeded device, with multiple applications mainly coded in c++ |
gcc, gdb, coverity, ctc, valgrind, visualcode, vim, libasan, cppcheck, codescene |
31-60 seconds |
we have some guidelines that everyone needs to follow. |
we have tools that give us warnings about it, but e,g if it does more then it says it does. |
we have code reviews for each pull request |
60 |
30 |
10 |
probelm solving, seeing something working at the end, doing solutions that are future proof |
having to solve other people bugs |
I have some notions I did a trainning 15 years ago. |
I was asked to :) |
Show
|
| 10 |
15 |
C, C++ |
Scripting, Java |
Boost |
I like to learn and use newer tools to ease the software development. |
In simulator with JSON based inputs. |
Embedded system running embedded software. |
VS Code, Git etc. |
5-30 minutes |
I try to follow company coding standards. |
Function is exceeding LoC threshold. |
Code is thoroughly tested and reviewed. |
45% |
40% |
15% |
I like to consider all the scenarios/use cases while designing and code accordingly. |
Hacks, hardcoding, temporary throwable code etc. |
It is about as and when coding is done, testing is also done. This avoids iterative process. |
To understand how to code and test simultaneously and deliver the code with high quality. |
Show
|
| 10 |
15 |
C,C++ |
python |
pytest |
Like to explore new languages and platform for coding. |
json based test input and manual verification of output |
optical embedded system |
visual studio
git
bitbucket |
2-4 hours |
professional |
When I stop following it. Mostly upto 2-3 levels of logic or flow or sequence is acceptable. |
good. |
5 |
5 |
3 |
It feels good when system behaves as its coded.
The user requirements are met. |
Long hours spent in debugging issues some time. |
Heard before. But will learn now. |
Nominated by my Organization |
Show
|
| 7 |
12 |
C, C++ |
Python |
Command line interface is used to execute the SW/APIs added with various arguments. |
I am a SW developer who likes to keep the SW design as simple as possible which helps in debugging issues. |
Yes |
Embedded Linux |
VSCode |
Under 10 seconds |
We follow the coding standards preferred by the organization.
Camel case used for methods, etc. |
Based on the no. of line and the no. of branching conditions used. |
Bitbucket is used for code reviews. |
6 |
2 |
2 |
The automation that SW provides which makes things simple and quick. |
Complex design which involves too much time to debug if its not self written. |
TDD is basically writing SW for the already defined test cases. |
To know more about TDD and how to accommodate it in my SW development process. |
Show
|
| 4 |
15 |
C++ |
Python |
Proprietary tool |
Passionate engineer, part of a team which develops complex SW which wants to be a world class R&D team |
Automated test cases |
Telecom optical equipment |
VSCode, Vim |
1-5 minutes |
C++ 11 |
By number of lines |
Constructive feedback will be provided and most of the corner cases will be evaluated |
60 |
25 |
15 |
Would love to write complex logic and debugging all corner cases |
To debug issues which are hard to reproduce |
Having unit test cases ready before development itself, so that all the modules can be tested |
To know more about TDD and to develop SW with great quality before test cycle |
Show
|
| 5 |
12 |
C |
CPP |
None |
Little busy with office work. Will be giving short answers to completes these tasks. |
UT |
Yet to explore |
normal |
30-60 minutes |
company standards |
By counting lines :) |
Team reviews |
3 |
3 |
4 |
Satisfying |
Tricky at times |
Not yet aware |
NA |
Show
|
| 5 |
9 |
C++ |
C, python |
gtest, Testwell CTC++ |
Passionate about network security |
Most of the times it is manual test. We build and replace the modified binary/library in target system and check. |
SW applications running on Debian |
vscode, tabnine |
1-5 minutes |
C++11 |
We use a tool called codescene which is available as plug-in in vscode |
Bitbucket PR review |
2 |
5 |
8 |
Be thorough with design before starting implementation |
Changing legacy code |
Have been trying to follow this approach since moving to agile teams |
Have been struggling to develop unit test cases in embedded software |
Show
|
| 15 |
25 |
C++ |
C
python |
gtest |
I'm in scrum master role. I like sports. I have a son. I live in Lisbon, Portugal. |
unit tests, script/automation tests and manual tests |
embedded systems running Linux |
VS Code, Pycharm
Colaboration tools: Confluence, Jira, Bitbucket, Jenkins |
30-60 minutes |
following the company guidelines |
when it doesn't fit within the screen |
mandatory in Bitbucket pull-requests |
50% |
30% |
20% |
interaction with the system and HW; finding the best way to implmnt a feature and doing future proof |
complexity that sometimes people do SW, that us caused by a gap in the design and solution grow |
tests are done before the code |
TDD is great approach.I want to learn it, so I can help my teams to implement it and improve quality |
Show
|
| 2 month |
7 years |
Embedded c |
C++ language |
Not yet used my project. |
no |
TDD frame work |
stm32f427 |
STM32CUBEIDE |
5-30 minutes |
MISRA C |
while development |
no |
50 |
30 |
20 |
expected solution when facing some problem. |
Documentation process |
not more |
understanding the test driving code for quality development. |
Show
|
| 1 |
5 |
c |
python, rust, java |
junit |
I like programming for a living but I like also to see the Sun sometimes :) |
manual testing in real products |
linux and freertos environment |
visual studio, logic analyzer, oscilloscope, jtag |
31-60 seconds |
none |
divide in some functions |
none |
50 |
10 |
40 |
transform and control reality, make things easier and more confortable, automatings things |
getting stuck in the same step for long time. In one word, debugging. |
barely nothing |
I want, and in extension my company, to start testing our products before QA team gets involved. |
Show
|
| 1 |
10+ |
C |
JavaScript, C#, C++, Assembler |
none/unknown |
I've spent years doing end user support for nationally distributed products that run software I wrote. If they're gonna hot plug it you should try hot plugging it at least once before it leaves the building... |
some of the legacy code here is tested using tools developed after Grenning training (10+ years ago?). I know zero details beyond: "the tests run at build time" |
various embedded systems, more towards the 32 bit microcontroller |
eclipse, xdc tools |
11-30 seconds |
there is a modified Embedded C Coding Standard (Barr) applied to some legacy code |
too many arguments... runs off the screen in both x and y
directions |
informal if existent |
3 |
3 |
3 |
seeing intuitive, useful electronic hardware work with high performance, despite the complexity |
legacy code mess. lack of documentation. overly complex solutions to simple problems. |
I read the first few chapters of the Grenning book years ago. |
I want to see generic TDD before figuring out how it was implemented here in legacy code |
Show
|
| 0 |
5 |
C |
None significantly |
None significantly |
I enjoy going to concerts and playing sports. |
Creating test procedures based on code features and validating against. |
Embedded devices, iot. |
ide, repository control, text editors, ai, debuggers. |
11-30 seconds |
Follow standard naming and organization practices, attempt to keep code highly modular and readable. |
When the purpose of the function becomes convoluted or easily separatable. |
Have not had any yet with current company. |
33 |
33 |
33 |
Seeing words become functioning products. |
Tedious work like documentation. |
Mildly familiar from college education. |
Company requirement |
Show
|
| 1 |
10 |
C |
C++
Python
Powershell
|
pytest
company uses google test |
no |
pytest + python + powershell |
Arm Cortex M7, comms mostly via CAN |
VS Code
MCUXpresso
Segger J-Link
Picoscope
|
31-60 seconds |
self-defined |
when it scope stops being easily understood |
non exist |
30 |
40 |
30 |
When it finally works |
When it doesn't work + all the legacy crap |
dipped my toes into it, started using it a little bit |
Want to go from using it a little bit to using the correctly, especially with legacy code |
Show
|
| 1 |
5 |
C |
C++, matlab, python |
cFS unit test framework
|
I am a telecommunication engineer, but I work as a software engineer, and I would like to improve my developer skills with this course! |
unit test with cFS, system test with robot framework, "manual" functional test |
spacecraft on-board computer |
git, cmake build system, vscode |
1-2 hours |
none |
when it has more than 3 nested branches and too many lines (>80) |
code reviews are requested by developers when they finish a task, they are mainly based on design |
30% |
30% |
40% |
seeing that my script is running and working in the real word is satisfying |
doing unit tests, sometimes we write tests that are not useful, and we do it only for the coverage |
it helps in writing code and tests in a more effective way |
to learn a new method to develop software and try to apply it in our project |
Show
|
| 2 |
10 |
C |
C++, python |
cFS unit tests framework, lcov |
i really like embedded system, especially if made for the space sector, and critical or real-time system, hope this course may help me to develop a methodology to realese higher quality and more reliable software |
unit tests up to a minimum coverage, robot framework for system level tests, "manual" functional tests |
satellites on-board computer |
git, cmake as a build system, vscode, self-hosted LLM |
1-2 hours |
unfortunately nothing strict, based on most known misra C guidelines |
when it takes more than 70/80 lines or has too many nested branches (> 3/4) |
code reviews are requested by developers when they think they need it, focused on design |
40 |
30 |
30 |
seeing the software execution effects in the real world (e.g. actuators, sensors reading, etc) |
unpredictability, it's frustrating when behavior differs from what you imagined while programming |
it relates to incrementally build unit tests, extending them while the tested feature advances |
explore different methodologies, understand if this would fit well in our development process |
Show
|
| 7 |
10 |
C |
Fortran, C++, Java |
check, gtest |
When I'm neither with my family nor programming, I love riding on bike. |
Tdd mostly since last year, mncks, DLP |
Embedded Xilinx devices |
Qemu, libcheck, mocks |
Under 10 seconds |
Misra C 2012 |
When I'm getting confused about what it was doing since its starting sentence |
Deep code review, understanding of requirements |
50 |
40 |
10 |
Easy to learn every day |
Not understanding what Javier wanted to do some time ago |
I read TDD for C/C++ about one year ago, and It is reducing a lot of uncertainity |
I wanted more exercises after reading the book |
Show
|
| 6 |
>12 |
C |
Python
C++ (very rarely) |
None |
From South Africa, live in Berlin, have 2 cats, still love the Commodore 64. |
Manual tests, custom python scripts, ci-fuzz, cpp-check |
ARM processors (STM32, nRF52) with Ethernet/Wi-Fi and various radios. RTOS or bare metal. |
makefiles, cmake, arm gcc, vim, github |
11-30 seconds |
I like Henning Schulzrinne's style. Tabs to 4 spaces. Consistency with existing code. |
Too complex to easily follow. |
Each PR is reviewed by another developer. |
30 |
40 |
30 |
Solving problems |
Chasing difficult to reproduce bugs. |
Writing tests for all code upfront. Testing first and throughout development. |
I want to better test my code. To create reliable code. |
Show
|
| 25 |
58 |
javascript |
SQL, C ,Java |
none |
most of the time I am a sloppy programmer, but I can prototype like crazy. |
manually |
NetSuite customization and scripting |
gitlab, notepad++ |
31-60 seconds |
an agreed upon set of conventions for naming and structuring code. |
gut feel. |
all code and code changes gets reviewed by at least one person. Code reviewers rotate. |
30 |
40 |
30 |
its like solving puzzles |
gathering requirements |
nothing |
desire to learn |
Show
|
| 1 |
3 |
C |
C++, Python, Shell/Bash scripting |
C- libcheck
C++ - googletest
Python - pytest |
I'm a Telecommunications Engineer, specialized in Electronic Systems, who likes the embedded software.
I work in the Space sector, developing software for GNSS (GPS or Galileo specifically) receivers. |
Unitary tests, corner tests, functional tests and (if applicable) performance tests. |
Embedded Linux-based systems. GNSS receivers. System on chips. |
Visual Studio Code IDE (previously Eclipse).
gcov/lcov, cppcheck, Valgrind, clang-tidy/format |
Under 10 seconds |
Coding, testing, debugging, CI checking, consistency, errorhandling, compliance, cross code-reviews. |
It is not fully shown in a 24'' screen. For sure operations can be moved to functionality groups. |
Deep code reviews about the functionality of the code, and docs, convention, etc done by CI |
4 |
4 |
2 |
I enjoy the creativity and problem-solving involved in developing software. |
Sometimes not trivial at all. Embedded systems present Operating System and hardware dependencies. |
I've read the Test-Driven Development for Embedded C book and took some university lessons. |
To deep into the knowledges from the TDD book. |
Show
|
| 3 |
6 |
C++ |
Python, Java, C#, qml |
CppUTest |
Interested in design, architecting the software in a way that is easily adaptable to change |
Unit testing with CppUTest before merging and periodically performing integration tests |
Testing features of medical devices |
VSCode, IAR, QtCreator, Bitbucket |
1-5 minutes |
MISRA and IEC 62304 |
If the function is doing a lot more than what the name of the function suggests |
Reviews completed before merging code |
35% |
25% |
40% |
You can be somewhat creative with it and I like seeing the impact |
Sometimes it is difficult to jump into a project that has legacy code |
You write a test and then code to make the test pass |
Slow on work and a good intro to the concept to integrate TDD at company |
Show
|
| 4 |
46 |
c |
C++, Python |
Vermont Software, (defunt) Nothing modern |
I have a heavy Database background and like riding a bicycle. |
QA Feature regession testing for functionality. Firmware engineer edgecase testing. |
ESP32 WROOM 32E SoC |
VSCode with extensions for C and python |
1-5 minutes |
I have one, I just can't describe it. Which is not a good sign. |
When it has nested returns. |
Currently we have 1 other FW engineer to a Pull Request |
30 |
50 |
20 |
Getting a piece of refined sand to think it endlessly funny to me. |
dealing with requirements from people that don't fully know what they want. |
It's a paradigm shift in order of operations to writing software. Test first, then code. |
Hoping to gain insight in to faster code development by having some structure in place |
Show
|
| 2 |
5 |
C |
Only C |
N/A |
I love to design on my own embedded system including PCB design and firmware development. But I need definitely learn how I should do it systematically. |
With IDE. |
STM32 Microcontroller. |
STM32CubeIDE |
1 day or more |
C99 |
Number of lines |
I don't have a code review experience. |
10 |
10 |
80 |
Nice to see for controlling designed hardware. |
No one can help me to debug the issue due confidentially of my projects. |
There is a book related this book from James Grenning. |
Developing firmware smoothly and teach to students or any learners how they develop firmware. |
Show
|
| 4 |
6 |
c |
python,C# |
None |
I am active in jiu jitsu outside of work. |
Debugging tools |
STM32 and ESP32, we will have some other chips in the future. |
STM32CubeIDE
Visual Studio Code and a variety of plugins |
31-60 seconds |
Clean, concise and simple. |
the whole function should be seen an editor view that has a console at the bottom. ~40 lines or less |
At work they have been minimal I hope this course helps us establish better practices. |
20 |
40 |
40 |
I like the ability to program hardware to do real world data acquisition or actions. |
I don't like full ownership of large projects by a single dev. |
I only know that test cases should be written first then code is written to fit those cases. |
My team enrolled as a group learning project to help our company establish a standard. |
Show
|
| 1 |
30 |
Embedded C |
C++ |
none |
I don't have all the answers, but I can find them! |
Unit and integration |
Embedded PIC16,PIC32 and ESP32 |
Notepad++ |
1-5 minutes |
No business coding standard. Personally I use Michael Barr's Embedded Coding Standard |
When it has too many branches |
What code review? |
80 |
10 |
10 |
Able to find creative solutions to a problem/task. Control of robots. |
Never an expert |
Don't know yet, still learning |
Required |
Show
|
| 0 |
16 |
C |
Python, C++ |
CppUTest, GoogleTest |
I am learning all the best firmware practices by reading your book, following Elecia White's podcast and memfault interrupt blog. |
Manual testing |
STM32 |
STMCube IDE |
31-60 seconds |
K&R style |
When its doing too many things than the desired functionality. |
We dont have that process setup yet |
4 |
2 |
4 |
Solving problems at low level |
Working with tightly coupled code and code generated by the IDE. |
I have read your book in the past and have written some unit tests. |
To actually deliver high quality firmware. |
Show
|
| .6 |
5 |
embedded c |
c
c++
python
java
|
QTP |
WORKING ON MICROCONTROLLER FOR THE INDUSTRIAL APPLICATION. |
unit test |
Multiple peripheral system |
STM32 CUBE IDE |
Under 10 seconds |
MISRA |
TAKING TOO MUCH TIME FOR DEBUG |
2 CYCLE REVIEW |
30 |
30 |
40 |
CODE DEVELOPMENT AND TESTING |
DEBUG |
TDD IS A USEFUL TOOL CAN BE USED FOR IMPROVING THE FUNCTIONALITY OF FIRMWARE |
TO IMPROVE MYSELF AND TEAM |
Show
|
| 3 |
20 |
C |
python, C++, pic basic, vhdl, verilog |
none |
I like biking, running, and climbing, dnd, and Pokemon go |
I test edge cases and then come up with a test plan for a technician to run. |
embedded devices |
VScode, eclipse based IDEs |
1-5 minutes |
I have mostly written prototype/proof of concept code, but I have also done some production code |
Uh… I don’t think that is necessarily a thing, especially if you are trying to squeeze processing ti |
I have never done one |
3 |
3 |
4 |
bringing machines/code to life |
useless meetings |
nothing |
my boss said to |
Show
|
| >1 |
8 |
C |
C++
Python
TypeScript
Dart |
Ceedling |
n/a |
Manual functional / behavioral test suite
I started at Whisker as a FW QA Engineer in July, I have become familiar with Ceedling and am in process of adding unit test capabilities to FW team. |
Main MCU is PIC but is being phased out with STM32, all targets have companion ESP32 for Wi-Fi. |
VSCode
Espressif's ESP-IDF
STM32CubeIDE |
1-5 minutes |
Not established |
When it can become modular or easily separated into discrete steps. |
Have not participated in one, but have recently set forth a plan to make this a regular occurance. |
n/a |
n/a |
n/a |
Solving problems, Exercising creativity, |
Firmware can be frustrating because of non-intuitive SDKs, clunkiness of building, flashing/debug |
Unit tests are created during planning for new code, and unit tests guide development of code. |
Our firmware group at Whisker plans on adopting TDD to consistently deliver quality firmware. |
Show
|