| 1 |
15 |
c |
c++ |
google test framework |
I have been coding in c/c++ for few years, but I don't hav idea on TDD. So I need to explore now. |
Using google framework, we write test cases for the code under test. |
Earlier network elements now, data collectors for water meters. |
c cross compiler for nxp platform |
1-5 minutes |
We have certain guidelines to follow. |
If there are more number of test cases pertaining to each function then definitely we know. |
Reviewers follow the review guidelines document and review the code. |
10 |
4 |
3 |
It gives me immense pleasure to see my code is runnung on the systems. |
Bit tedious job to design the software application architecture that gives flexibility to enhance. |
I just know first we need to write test cases before even to start with developing code. |
My organization mandated this course to complete. |
Show
|
| 4 |
13 |
C |
C++, python, Java, C# |
None |
I've been wanting to get some form of testing integrated into my personal Android apps. |
Generally top-level integration testing when changes are made |
Embedded Linux + FPGA w/soft microcontroller |
vim, CMake, Intel Quartus |
5-30 minutes |
Varies from project to project/application to application as-needed. |
When it includes duplicate code that could be made into another shared function elsewhere. |
Very basic reviews on each pull-request |
10 |
5 |
85 |
Making things work, tracking down obscure bugs and fixing them with one line |
Bad tools/vendor support |
Avoiding getting bogged down writing tests when we don't even know what the legacy code is doing. |
I'm open to learning about tdd, but am mostly here due to the company organizing it. |
Show
|
| 1 |
26 |
C |
C++, Python |
CppUnit, QSpy, TSIM (for VxWorks) |
I like walking in the woods with my dog, road biking, mountain biking. I consider myself an advanced C++ designer/developer and am pretty good with Python. |
Run on hardware in the debugger. Hack my code to hardcode values or execution paths. |
STM32 Cube |
STM32 Cube IDE (eclipse), CLion |
1-5 minutes |
I think we have a Confluence page |
Is there such a thing? |
All code must be merged via pull requests. All pull requests must be approved by invited reviewers |
60 |
5 |
35 |
I can create something new and useful from scratch. I like working with hardware. |
We still can't/won't estimate accurately (or truthfully?) |
I worked on a project a couple of years ago which was truly TDD. I loved it. |
Part of the reason I was hired at Inficon is because of my advocacy for TDD during my interview. |
Show
|
| 1 |
6 |
C++ |
Python, CUDA, C |
Catch2 |
Software engineer with Electrical Engineer background in communications and DSP. |
Manually. No unit tests or any automated tested machinery. |
Linux on x86. Basically a mini-desktop platform with a few GB of memory. |
CMake, GCC, Clang format, VS Code, Visual Studio |
11-30 seconds |
No official coding standard. |
When it has more than one purpose. |
All changes to the main dev branch must be submitted as a PR on bitbucket, req. one reviewer. |
5 |
0 |
5 |
Problem solving. |
Working with poorly thought out legacy code. |
Familiar with the concept, but haven't worked on a project that develops strictly by TDD. |
Proximate cause: chosen training by the software manager. Ultimate cause: training has real value. |
Show
|
| 9 months |
21 years |
c/c++ |
angular |
Microsoft Unit testing framework |
NA |
we don't |
embedded device |
stm32cubeide |
1-5 minutes |
Written in a document |
100 lines |
NA |
50 |
0 |
50 |
Feels like play |
can't thinkg of anything. |
Not much |
Mandated by management |
Show
|
| 0.6 |
15 |
C |
Python |
Ceedling |
Not buzzword compliant |
Functional testing |
STM32 Cortex-M7 |
STM32CubeIDE |
31-60 seconds |
MISRA-C |
A good function is to the point and primarily does one core thing. |
Pull requests are reviewed by the team before merging into the main branch. |
7 |
4 |
3 |
The challenge of deconstructing a problem and developing a solution using software. |
Software that's too hardware dependent. Software that's not readily reusable. |
TDD starts with writing a failing test case and then creating just enough code to pass the test. |
To understand and implement test driven development wherever possible. |
Show
|
| 1 |
15 |
C |
C++, Python |
N/A |
N/A |
Manual testing. Very limited automated testing |
Embedded devices |
N/A |
1-5 minutes |
N/A |
If it doesn't fit into my screen. If it has too much complexity |
Peer reviews for all pull requests |
40 |
20 |
40 |
To make computer/microcontroller do what I need it to do |
Debug tools that don't cooperate |
You need to have test in mind and start by thinking how you can test a piece of code before you star |
To learn what TDD really is |
Show
|
| 1 |
4 |
C/C++ |
Python |
CUnit framework |
I am interested to see how classes I took on TDD in college can be applied to real-world application code and how to integrate testing into already existing code bases. |
With log files and debugging statements |
Linux-OS based machine |
Visual Studio Code and GDB |
5-30 minutes |
It differs within my projects codebase as some of the code is acquired code. |
Lately by using the getrusage utility, but eventually would like to use something like gprof. |
Pull requests are created that reviewers can comment on |
20 |
40 |
40 |
Being able to develop applications and systems that power today's innovations |
Tracking down and plugging memory-leaks when they occur |
That writing tests first demonstrates you know the expected/desired requirements of your code |
Automating the testing of code functionality sounds like an incredible way to better allocate time |
Show
|
| 34 |
40 |
c |
.net |
none |
- |
run it |
- |
- |
31-60 seconds |
- |
- |
- |
50 |
10 |
40 |
- |
- |
- |
- |
Show
|
| 4 |
17 |
C |
Python
C++ |
None |
I don't know |
Hardware Debugger, Print Statements, Tracealyzer, GPIO Toggling. |
STM32 Microcontroller with Cortex-M7 core, Free RTOS, GUI UI, pulse real time measurements |
STM32 CubeIDE, Clion |
5-30 minutes |
developed by me, over the years, from what I like, and feel is best practice. |
When it tries to do multiple things. or when it takes up a screen's worth of space. |
I like to pull the code down and go over it in the IDE. |
60 |
10 |
30 |
Controlling the hardware, instant gratification when something works. |
deadlines :) |
Very little. |
I would like to learn how to use it with Embedded C systems. |
Show
|
| 20 |
30 |
C++ |
C, Java, Php |
Junit, Gtest |
. |
unit tests with google test |
pc windows software, android apps |
Qt Creator, android studio |
31-60 seconds |
internal |
when it's more than, say, 200 lines |
too few developers |
70 |
15 |
15 |
it's a creative process |
I did it for decades |
I use it regularly |
I'd like to figure out how to do TDD on MICROs |
Show
|
| 34 |
25 |
C |
Python |
nothing |
I develop small application for production equipments |
debug and functional tests |
embedded devices |
Platformio for Arduino |
11-30 seconds |
Not following a specific coding standard |
2 editor pages |
no code review |
33 |
33 |
33 |
Make automation applications |
debug |
nothing at the moment |
To reduce debugging time |
Show
|
| 2 months |
10 years |
Embedded C |
I was using Python & VB.net in my previous job |
Nothing |
I have worked in various domains like Railway displays, automotive & Electrical domains. I used multiple programming languages during my previous experience like Embedded C, Python & VB.Net. |
Currently I am writing testcases using utest, and ensure that all test cases are passed. |
Right now I'm working on a cellular module for water meters. |
IAR Embedded workbench, Visual studio, GIT |
1-5 minutes |
I follow barr & misra C coding standards |
If it has too many statements and too many function calls |
Before merging the code into remote branch, my code will be reviewed by all other team members |
5 |
3 |
2 |
We can find various solutions for a problem statement, and implement new tools/functionalities |
Sometimes with oversight we take more time for small issues in the code. |
Its Test Driven Development where a unit test will be written along with the regular functional code |
I thought it will be very helpful for my day to day work also to my future |
Show
|
| 3 |
10 |
C |
Assembler |
none |
I studied electronic. At home I try to repair any sort of electronic device. In my free time I like running. |
I normally test the code on the target using a programmer/debugger tool. |
The target is an embedded system based on 16bit or Arm microcontroller |
I usually use the IDE supported by the microcontroller manufacturer. |
1-5 minutes |
We follow few coding rules defined with my colleagues (e.g: variable/function naming, comments etc. |
I don't have a specific rule. |
It's usually done by myself in order to find mistakes or improve code, sometimes I ask to colleagues |
30 |
20 |
50 |
I like to see how a raw schematic become a working object which I can control with my code |
When the complexity of the code increases, it becomes difficult and time consuming to resolve bugs |
It is a way to design code in order to increase testability and maintenance in the time |
To learn this programming approach and start to apply unit tests either on new project and old ones |
Show
|
| 1.5 |
5 |
C++ |
C, Python |
CppuTest |
I have a golden retriever named after the Archer cartoon's main character, Archer |
As a developer write and test against unit tests. Commits are tested by an automated build system. |
Thermal printers controlled by an embedded Arm system. |
Qnx Momentics, PCLint, CppuTest |
5-30 minutes |
N/a |
When it gets difficult to tell what's happening in it. |
N/a |
60 |
10 |
30 |
Finding challenging problems and creative solutions |
N/a |
Not much, but I've heard good things about it. |
It was assigned to me, but always enjoy learning new techniques and adding a tool to my belt. |
Show
|
| 1 |
5 |
C/C++ |
Python, Rust, Javascript. |
CppUTest, Python unittests. |
I am an early career firmware engineer. I am at my first first job, and am trying to develop good habits early. |
Code first, run existing tests, and create a new test if necessary. |
Target system is either an x86 VM, or an ARM chip. |
Eclipse |
11-30 seconds |
Internal standard. |
When it becomes hard to read and I see repeated sections of code. |
Done with either a review software, or pair programming. |
30 |
30 |
40 |
I enjoy the problem solving aspect of development! |
Dealing with intermittent issues/bugs in code. |
Write a test first, then develop for that test. |
I want to write better quality code faster. |
Show
|
| 18 |
20 |
C++ |
Python, Matlab |
Python Unittest |
|
Python UnitTest framework unsing the web interface of our device (kind of system test) |
ARM Cortex A based embedded device running on Linux |
Eclipse, GCC/GDB, PyCharm, GitLab, Teamcity |
31-60 seconds |
|
|
|
10 |
40 |
50 |
|
|
|
unhappy with the test coverage of the current project, starting a new project soon |
Show
|
| 4 |
10 |
Python |
C, C++, Javascript, Matlab |
Python unit tests and teamcity CD/CI |
Brazilian, Electrical engineer, Curious, Lazy sometimes |
Python unit tests and teamcity CD/CI |
Embedded linux and rtos |
Pycharm, Visual Studio Code, Virtual Box |
31-60 seconds |
Try to make as modular and agnostic as possible |
If it's replicating code of other functions or making more stuff than what the function name defines |
I often make silly mistakes |
5 |
2 |
3 |
Solving complex problems |
Debugging |
Only that you create tests before you code |
To increase development speed and decrease debugging time |
Show
|
| 14 |
30 |
c# |
Long time ago: java, c, c++, fortran, lisp |
Resharper Unit testing
Testing tools in Visual Studio |
I like software development |
Unit testing, acceptance testing, manual testing for the GUI |
PC |
Visual Studio |
11-30 seconds |
Whatever Visual Studio/Resharper suggest |
When it does more than one thing |
We are a team of two: we review each other |
60 |
20 |
20 |
Everything:building, breaking, fixing...but most of all to help people save time when thy use our sw |
When people who don't know the sw, make decisions about it :-) |
Did a stint some years ago. Not doing tdd anymore, but would love to do it again |
Not doing tdd anymore, but would love to do it again |
Show
|
| 1.5 |
4 |
C# |
Currently just C# |
GitLab CI |
Im fairly new so I do not have that much experience with test harnesses or testing in general. What I see is that tests tend to be down in the priority list for most people.
So I look forward to learn a lot about TDD. |
We currently have a few MSTests. Everytime we commit something these tests are executed.
Also before committing we execute the tests manually. |
Windows PC |
GitLab
Visual Studio
Confluence
ReSharper |
11-30 seconds |
I try to use the C# coding convention by microsoft. |
If inside the function there are parts which are meaningful enough to require a function on its own |
We have a small team (2 people). So usually before committing we look at the code together. |
50 |
20 |
30 |
I like the always learning aspect of it. There is almost no day where you don't learn something new. |
Unrealistic deadlines |
Create a test first. Build logic later. Continuous growth of complexity, refactoring and testing. |
I want to learn about TDD. How to use it, its benefits, how to implement it on a real environment |
Show
|
| 1.5 |
5 |
It was Java |
Chora (Embedded Wizard), Python, C, a little Cpp |
GitLab CI |
Since I joined the current company I am coding the UI 95% of the time. In a few weeks, I am going to start coding again in C/Cpp or Java for a new project. |
Mostly manual testing |
Embedded devices (cortex A with Linux or M architectures with RTOS) |
Eclipse, Embedded Wizard IDE, |
31-60 seconds |
Not following one in particular, I try to apply the SOLID principles whenever I can |
When it does more than a function or when a portion of this function could be useful somewhere else |
I've never had, except for small parts of code when they were needed by one of my colleagues |
50 |
40 |
10 |
solving problems and finding efficient solutions |
testing when there's UX or hardware involved |
just basic theory, I tried in the previous company for embedded stm32 boards but it didn't last long |
To learn more properly so I could apply for embedded development and the new coming project |
Show
|
| 14 |
35 |
C/C++ |
Python, C#, PHP, Matlab, Javascript, Bash, Assembly |
Google Test |
An old dog eager to learn new tricks |
Mostly with automated scripts for unit, integration and regression test. Some unit tests (not driving the development), some debugging.
|
Portable audio analyzer, dual ARMv7 running Debian 10 on Linux kernel 4.9.11 with RT patch |
Eclipse CDT, Visual Studio, VS Code, PyCharm, Git/GitExtensions, TeamCity |
31-60 seconds |
We have some guidelines for indenting and identifier naming, not always consistently followed. |
More than 2 screens long, more than 5 nesting levels. Limits may vary to facilitate comprehension. |
Only occasional. Some pair programming. |
50 |
25 |
25 |
You always learn something new with every project. |
Menial and repetitive tasks that can be hardly automated. |
You iterate writing tests first that capture the requirements, then the code that makes tests pass. |
Not my idea, but TDD makes sense and is worth a try. |
Show
|
| 1 |
25 |
C++ |
Python, C, Matlab |
-none- |
I believe that writing software is engineering and not art, so let's apply all the tools available to make it better! |
Some unit tests written after the code is "ready", plus integration/system tests. A a lot of manual testing... |
Hand-held device: MCU running RTOS, display, keys input, storage, USB, cloud connectivity |
-- |
31-60 seconds |
Don't have one at the moment, but planning to introduce one |
If it doesn't fit in one screen |
Don't have code reviews at the moment, but planning to start doing it |
30% |
15% |
55% |
Thinking about architecture, define how each module should work, interfaces and algorithms. |
Debugging! |
Read your book, informed myself through podcasts, internet. Big fan of it - that's the way to go! |
I want to be able to support the developers in embracing and practicing TDD. |
Show
|
| 8.5 |
15 |
python, c |
java, c++ (little), shell scripting |
plain asserts inc, unittest (python), junit |
Currently working as R&D manager in IOT space mainly (smart metering) following project activities and supporting colleagues, sometimes I do programming (software and firmware) and electronics design |
sometime asserts or googletest |
Ultra low power embedded systems (bare metal without OS) on 16 or 32 bits (ARM) MCUS |
Mostly eclipse based tools, sometimes VSCODE |
1-5 minutes |
We have an internal not really formalized standard at the moment, followed Linux in the past |
When I have to scroll the window to see the whole function |
Not yet really doing those unless a colleagues asks to do them |
33% |
33% |
33% |
Creating things that work ! |
Solving bugs, understanding other people's code |
Shortly a methodology where you first write a test for you code and then the code itself |
The aim is to improve quality of code/products of the team (including myself) |
Show
|
| 1 |
12 |
c++ |
c, python, rust, bash |
Cpputest |
i have a degree in electrical engineering from the University of Tennessee |
write and run automated unit and integration tests |
we develop for an ARMv7 CPU in printers |
Momentics, svn, git, vim |
1-5 minutes |
maintain the style of the codebase while not (re)introducing code smells |
when i need to use the scrollwheel to read it all, and there isn't just a huge switch statement |
we have a remote, asynchronous code review process, allowing experts in any time zone to give input |
30 |
30 |
40 |
integrating and interfacing with various hardware components |
debugging for hours, only to find a simple logic error |
i've read the book, and worked in a test-driven environment for over a year |
manager suggested it, and i don't have to pay for it myself :D |
Show
|
| 1 |
10 |
C |
C++, Python |
static analysis |
I'm Fernando from Milan. I've worked in the embedded system field for 5 years.
|
debugging mode,
non regression test on target side |
embedded system |
vendor IDE |
1-5 minutes |
|
I don't know how to rename it. |
no code review |
40 |
30 |
30 |
there is no line, It's all up to you |
repetitive task |
It's an alternative to the waterfall design. It moves the key pint on the test side in someway. |
I want to improve my test and design skills, therefore I chose this training. |
Show
|
| 3 |
4 |
C |
Python |
Unity |
I have worked as an embedded software engineer for 3 years in the automotive industry. Looking to expand my knowledge in this field. |
Unit tests |
Currently our target system is SPC58NH92C5 (CHorus10M) - triple core, PowerArchitecture CPU
|
CMake
Greenhills compiler
other inhouse tools
|
1-2 hours |
MISRA |
More then 20 lines of code |
Walkthrough the changes |
2 |
2 |
6 |
Solving challenging problems, Constantly learning, seeing software run correctly :) |
Looking at the monitor for too long, hurts my eyes. :( |
Read the book Test Driven Development for Embedded C |
Expand my knowledge |
Show
|
| <1 |
5 |
C |
Python
Java
HDL |
N/A |
I like to learn |
By debugging and stepping through code to ensure proper execution |
A test instrument that contains a handful of separate boards controlled by one central processor |
IAR EW
Visual Studio
|
31-60 seconds |
N/a |
Hard to explain what it does succinctly |
Loose peer review |
4 |
3 |
3 |
It's interesting to be able to control and use electronics |
Tool chain bringup and quirks |
Just a cursory overview. |
To learn how to implement TDD in our context to make our code more efficient and easier to maintain. |
Show
|
| 5 |
5 |
c |
Python |
Not sure |
Hardware developer that helps out with firmware development. |
Manual hands-on testing of product. |
Embedded system running Android OS |
IAR Workbench |
31-60 seconds |
Not sure |
Not sure. |
Lead SW developer checks over code before it is committed. |
6 |
3 |
1 |
I only develop firmware but I enjoy it because I can test hardware very efficiently. |
Not sure |
Nothing |
Trying to get better at product development |
Show
|
| 10 |
20 |
C |
C++, PHP |
Unity, PHPUnit |
Originally electronical engineer. Ended up in developing embedded software. |
- |
Mostly STM32 |
An IDE, development board and a logic analyzer. |
5-30 minutes |
- |
- |
- |
40 |
10 |
50 |
The puzzeling and the unforgivingness (how your mistake always shows up) |
- Testing
- Always strugling how/where to start |
In short: Develop to make your tests pass. Work in small steps. Run tests continuously. |
I am not sure how/where to start with TDD. I hope this training gets me up to speed. |
Show
|
| 5+ |
few months |
C |
Python |
none |
I am Hardware Development Engineer and code occasionally for prototyping the hardware. |
Manually |
Its a motor tester (Test and measurement equipment) |
IAR Embedded workbench. |
31-60 seconds |
none. |
If the parts of the function can be reused then the function is too long and can be reduced in size. |
Colleagues. |
10 |
5 |
5 |
Helps me in realizing the hardware I build. |
Nothing. |
not much. |
I want to be able to do better coding as a Hardware Engineer I would like to contribute more. |
Show
|
| 3 |
20+ |
C |
Bit of C++, C# and Python |
None |
Software Supervisor for software team in Valley Forge looking after both NPD and Sustaining activities. Work varies but averages 20-30% software design/coding. |
Mostly functional/manual level testing. |
Various embedded processors, incl Renesas, Arm & PiC |
VS Code, VS Studio, MPLab, IAR compilers/debuggers |
11-30 seconds |
No specific standard at VF and not previously enforced. |
If it's longer than I can see on a page at once. |
Not normally done in past at VF, if done then informal/ad-hoc when needed. |
20 |
40 |
40 |
I like the challenges in solving problems and learning new things. Also being able to be creative. |
Dealing with poorly written legacy code, missing documentations. |
Very little, some of my team use it and we discuss it, but I haven't actively used it |
My team are starting to use TDD so I wish/need to understand it more |
Show
|
| 9.7 |
42 |
C# |
C, C++, Java, Perl, PowerShell, bash, Javascript/Typescript |
NUnit, VisualStudio built-in stuff |
I took a great TDD course over a decade ago, used to do TDD, now occasionally almost do TDD, but not regularly. |
With great difficulty. Unit testing not included in the code base, mostly; impractical to retrofit. I often change some small piece of complex calculations, validating results is hard. For more re-usable, general, new components, I unit test. |
Windows (desktop, some embedded stuff), and other embedded platforms (with no OS). |
mostly Visual Studio, some IaR embedded workbench, some Android Studio. |
31-60 seconds |
Follow existing conventions and/or do what makes sense. |
I notice that a section in a function forms a logical step that could be separated out. |
I asked once for a code review here, got nothing. No one has ever asked me to do code review here. |
6 |
2 |
2 |
Creativity: I enjoy being responsible for good ideas that bless others in appreciable ways. |
Those intractable portions of frameworks that are ill-documented and/or do not work as they should. |
Code a test that fails, write the code it tests so that it passes, then refactor, move on. |
I might learn some helpful tips/tools for being able to do more TDD, or possible DI/IoC for apps. |
Show
|
| 11 |
10 |
C# |
C, C++, Java, Matlab, LabView, VHDL/Verilog |
None |
Originally a test engineer, then design engineer working with hardware, then joined this company and programmed in C#, then C and then Java and finally on Android for a year before becoming a manager type. |
We have application and test engineer run validation tests on the product. |
Our products from bare metal C, windows embedded using C++ to Windows running hybrid C++/C#, Android |
IAR compiler, Visual studio, Android studio, Borland C++ |
11-30 seconds |
Non-existent or changes depending on lead software developer |
Functions are too long when an entry level programmer cannot understand them by inspection. |
Lead software developer would review my subversion check-ins and send back code review comments. |
5 |
2 |
3 |
Cool things can be made to happen if you have the right hardware! |
Waiting for hardware. |
Nothing |
I can let go of being an individual contributor even though I'm a manager... |
Show
|
| 12 |
20 |
C++ |
C Java C# |
None |
My current position is the first one that had an official build machine. In my previous positions release builds were made on developer's machines. |
It is tested manually by others by following test plans. Prior to others testing it, I perform manual tests of my own to verify functionality. |
We have multiple target systems but my current system is Android on top of Linux. |
Android Studio |
Under 10 seconds |
We don't have any formalized coding standards. I have expectations that are generally followed. |
If I have to scroll or the functionality is not immediately clear to me. |
I perform code reviews on each check in and provide guidance for improvements. |
70 |
15 |
15 |
Designing eloquent solutions that are efficient and easy to understand by the next developer. |
Making significant changes to existing code that is not clear and understandable. |
I understand the overall concept of writing tests first followed by the code to make them pass. |
I want to understand in depth how TDD works and if it makes sense for our team. |
Show
|
| 14 |
3 |
Java |
Python, C++, C, Prolog, Scala |
Maven |
I am currently an Application Engineer with my company 10 credits away from my CS degree. I will be transitioning into the Software Dev team next year. |
I had a SW dev course that used Maven as a testing platform for all our Java and JS code for a web app project. Test functions were written for each new code piece prior to development. |
Not sure. |
Not sure what the team is currently using. |
5-30 minutes |
Not currently on the team. |
When it performs more than one function. |
Not currently on the team. |
70 |
0 |
30 |
The creative problem solving process. Seeing your work functioning is very rewarding. |
The tedious nature of cryptic syntax and deciphering convoluted or ambiguous code. |
A software development methodology that puts functional expectations first through testing. |
Learn about TDD to ensure I am on board w/ expectations. Taking SW Testing @CSU this Spring. |
Show
|
| 1 |
8 |
Java |
c#, c++, python |
None |
I like board games. |
Manually by hand or by giving the code to others in the company. |
Unsure as well. |
Android studio |
Under 10 seconds |
It must build and we try to make changes function as the should. |
When it becomes confusing. |
Minimum and stylistic. We have pretty large and infrequent commits. |
30% |
20% |
50% |
I get to create something at the end of the day. Solving problems efficiently is really pleasing. |
It can become frustrating to deal with code that is convoluted. |
It is a methodology to program more effectively and efficiently. |
It would save us a lot of time and effort to put this process in place. |
Show
|
| 1 |
4 |
Java |
C#, C/C++, Python |
none |
I'm from Texas and went to Colorado for school. I have two cats and they are my pride and joy. I like to play video games, hang out with friends, and do crafts. |
I test code manually by running the program and performing different behaviors. |
unsure |
Android Studio, Visual Studio, SVN |
11-30 seconds |
unsure |
When it can't fit in the window. |
They are informal comments made after code is submitted |
50 |
25 |
25 |
It's like a puzzle. There is also some creativity in how to approach a problem. |
I don't like manually testing code. |
It makes testing less painful and tedious in the long run. |
My company is encouraging this class but I'm also looking forward to having better testing practices |
Show
|
| 1 |
20 |
C |
C++, C#, assembly |
Ceedling, NUnit |
Most experience in programming in C/C++ for Embedded systems. Started programming in C# about 1 year ago. |
Test cases are written in Ceedling for an Embedded C project, and NUnit for a C# project. Note that sometimes the test cases are written "after the fact".
Additional tests done by QA after a release candidate is ready. |
It is a two Embedded processor system, one runs code written in C, the other in C# running on WinCE. |
Debugger, simulator, demo code, test harnesses, lab tools. |
Under 10 seconds |
This is a legacy product which unfortunately does not follow a specific coding standard. |
Usually when it goes beyond 150 lines; when there is repeated code that can be grouped. |
If code reviews are done (if at all) they are informal. |
50 |
25 |
25 |
I believe developing software is actually really fun. |
Legacy code touched by many engineers who btw no longer work at the company... |
Been using it for about 1 year. It is great to give confidence when something has changed or added. |
Never had a formal training. I do believe it is very helpful to prevent bugs to be found late. |
Show
|
| 2 |
11 |
C |
Python |
Google Test |
Strorage Domain Experience 8 years. |
Unit Testing, CI pipeline |
SSD contollers. |
GNU GCC tool chain, JTAG debuggers, SIMICS enviourment. |
1-5 minutes |
MISRA |
when it difficult to understand the code directly.. when there are many loops... |
we use the code review system that comes with gerit. |
10 |
40 |
50 |
The thinking process imagining about the possible scenarios. the smart chooses(I think) I make.. |
To work on poorly designed code and you realize it's too late to redesign every thing. |
not much. |
to learn some methods to make my life easy. |
Show
|
| 3 months |
8 |
C |
C++ |
Visual studio |
I am working as a firmware developer in storage industry from past 7+ years. Mainly worked in C language. |
Writing Unit tests. On actual H/W sometimes |
storage Controller |
Visual studio code, Source Insight |
1-5 minutes |
C coding standard |
When function includes more than one logical functionality |
None started in current company |
40 |
40 |
20 |
Implementing solutions to problems in code is fun loving. |
Debugging critical bugs |
In TDD software requirements being converted to test cases before software is fully developed |
To reduce time on debugging bugs after firmware release |
Show
|
| 3 Months |
7 yerars |
C |
C++, Python |
Jenkins |
I hold a B. Tech degree in computer science. I have been embedded programming for almost 7 years as a professional. |
PC Simulator |
Arm based controller |
gcc, gdb, VS Code, Source Insight |
31-60 seconds |
- |
When its more than 100 lines and does more than one task |
- |
40 |
30 |
30 |
Designing, organizing code and testing it to see it works as visualized. |
documentation of code |
Software requirements being converted to test cases before software is fully developed. |
Would get to learn more about TDD. My team is thinking of adopting this strategy. |
Show
|
| 10 |
10 |
C And C++ |
Java,C# |
I have a Test application which calls specific function of interest. Also code coverage tools |
The Application is supported for Multiple Operating systems like Windows,Linux,ESX . Same Code base. |
I have test application which call the functions in a required flow. The Test APP has the added functionality to test all the interfaces for user. |
Multiple OS Like Windows,Linux,ESXi. The system should satisfy the pre-requisites SW and HW
|
Microsoft Visual studio
Linux GCC Compiler
Cross Platform Toolchain
|
30-60 minutes |
We follow general C and C++ guidelines in addition with custom rules |
With Lines of Code. Loops and conditional statements used inside. |
The Code is reviewed by Self and Team with tools |
20 |
60 |
20 |
Designing and creating the stubs. Making them actually work. |
Testing the stuff which cannot be unit tested unless specific HW or SW requirements met. |
Nothing. |
To explore and learn better method for Unit testing and detecting the bugs early in hand. |
Show
|
| 2.5 |
3 |
c |
c++ |
- |
I love listening songs |
We have testing environment and CI pipeline. |
lenovo laptop with 16GB RAM and window10 OS |
vim or visual studio code |
1-5 minutes |
- |
By the number of lines |
we use gerrit for code review |
20% |
20% |
60% |
coding and debugging |
long duration of unit testing |
Nothing |
- |
Show
|
| 0 |
10 |
C |
Python |
None |
NA |
Code development yet to start |
SOC firmware |
NA |
31-60 seconds |
NA |
NA |
NA |
70 |
10 |
20 |
NA |
NA |
Nothing |
To produce code/firmware with minimum bugs. |
Show
|
| 0 |
15 |
C |
C++,python |
Dont know |
I have been coding, debugging firmware for over 10 years.Before that i worked on UEFI drivers, and a linux drivers. |
I am new to Marvell.Previously we have used Unit tests written in C and ran over visual studio |
It is a SoC with 12 ARM R8 and 2 ARM M7 |
Visual studio code |
1-5 minutes |
I am new to Marvell and I dont know the answer to this. |
If we need to scroll the function on the screen. |
I am new to Marvell and I dont know the answer to this. |
40 |
20 |
40 |
developing software helps to sharpen my problem solving skills. |
The long debug sessions :) |
Test cases are written before developing any features. |
TO know more about Tdd and use it in our framework. |
Show
|
| 15 |
16 |
C |
Python |
Automation |
- |
We do manual and Automation testing.
In Manual testing, we test for particular fix/functions by running specific test.
In automation testing, we test complete code by running different test cases, which covers maximum code. |
OEM Servers with Marvell Products |
Microsft Visual Studio
Linux
Perforce
Git |
1-5 minutes |
use Standard C style
|
Number of line of code and if there is too many task done in single functions. |
Code review is done among different team members, where code changes and unit test result shared. |
40 |
30 |
30 |
Implementing logic in coding |
Debugging corner case issues which are not seen during complete test cycle. |
Have basic knowledge about TDD. |
To know more about Software development process,As I have not gone through any such training before. |
Show
|
| 0 |
5 |
C |
C++, Python |
Jenkins automation testing |
Having 5+ years of experience in embedded firmware/software development and debugging over Linux, RTOS or bare metal based platform for different microcontrollers. Always curious about solving problems using coding, its fun. |
PC simulation environment using python |
ARM based controllers (SoC) |
VS Code, Source Insight, GCC Toolchains, WSL |
1-5 minutes |
Internally defined coding standards (Naming conventions, MISRA, indentation, Reliable, portable etc) |
Function not doing one specific operation rather delivering more than one functionality & more lines |
Peers review using gerrit |
40% |
30% |
30% |
Coding, debugging and most important challenging problems
|
Documentation |
TDD is test first development process where test case is first written before you write enough code |
To gain the knowledge to write test driven software to faster the overall development process |
Show
|
| 1.7 |
8 |
C++ |
C, Python |
None |
I enjoy learning new things. |
Either on Simulator or EVB. |
I use a Windows Host. |
ARM Compiler 6, VSCODE |
5-30 minutes |
Im a at intermediate level in coding standards. |
if that function is not fitting on the screen. |
I review the code changes thoroughly. |
50 |
30 |
20 |
The real world usecases can be easily achieved with software development/ |
The amount of time it takes to write a complex code. |
Not sure about TDD |
I would like to know the smart ways of coding for lesser code size and better efficiency. |
Show
|
| 0 |
14 |
C / C++ |
Python |
GMock |
I like to solve Puzzles. |
I have not tested the code yet |
I dont know about the Target System. |
SourceInsight, VScode, Vim etc |
2-4 hours |
I usually adhere to the Standard C Style coding but it depends on the project too. |
When a function can be broken into subroutines but isnt. |
I am a new Joinee and I have not created any code reviews yet |
30% |
30% |
40% |
I like solving problems/puzzles and learning new things. |
Debugging someone else's code which is not very well documented |
It means:
1) understand the req
2) define a test
3) code
4) use #2 to confirm soln
|
I like to learn new things and also it was a pre-requisite. |
Show
|
| 0 |
17 |
C |
C++, Python |
gtest |
Mostly working on firmware development but did some object storage software development too. |
PC Simulator written in Python |
SOC |
Arm compiler/debugger |
5-30 minutes |
Internal |
When it does many things, difficult to understand and maintain. |
Internal |
50 |
30 |
20 |
The whole process especially the testing. |
Nothing |
I think TDD is a practice that software developers should follow to identify bugs at early stage. |
I wanted to learn and apply TDD practice to our daily software development work. |
Show
|
| 0.2 |
11 |
C |
C++ |
randomizing the UT and configuring jenkins to run it |
|
UT in visual studio |
Windows, Linux |
VS Code, Git, Jira |
1-5 minutes |
|
when code is of too many lines |
peer reviews, SME reviews |
60 |
30 |
10 |
problem solving |
The bugs |
adding scope or hooks so that the feature can be tested independently |
To enhance unit testing skills which developing various modules. |
Show
|
| 2 |
11 |
C |
C++, Python |
Visual studio |
I like FW development. |
On Simulation, Emulation, Evaluation board and form factor board. |
SOCs |
Arm compiler, SOC boards, custom simulators and boards, HW debuggers, protocol analyzers |
31-60 seconds |
Mostly I follow MISRA coding guideline but it changes from project to project and company to company |
By code inspection |
It is a good practice to get it reviewed by experienced person |
30 |
30 |
40 |
Designing, coding and debugging |
Less efficient tools for editing and debugging. Language selection also matters. |
Not much. |
Company policy. |
Show
|
| 14 |
16 |
C |
C++
Python |
None |
Device driver programmer for most my career. |
Design unit tests around the feature that I am working on and try to test it.
|
1. Various HBA solution FW interfaces and OS interfaces
2. HW blocks |
gcc, vim, ctags, cscope, gdb, git |
1-5 minutes |
Mostly follow Linux kernel coding standards |
When parts of the functions are duplicated somewhere else in the code. |
1. Check functionality
2. Security checks e.g., memory leak, dead lock
3. Tests performed |
3 |
3 |
4 |
Quick turnaround time.
Can try out things quickly. |
- |
Nothing much |
Will be working on Embedded system after long time. Good way to refresh things
|
Show
|
| 1 |
10 |
C and C# |
Python, C++, PHP, HTML5, CSS3, javascript, MYSQL, SQL |
I never use unit test harnesses |
currently i am working at TK Engineering as software engineer. |
Unit test using NUnit testing framework. |
I want to write a code in efficient way and delivers within a short period of time. |
- Visual studio community
- stm32CubeIDE |
30-60 minutes |
Camel Case and pascal case |
When i am debugging and testing. |
I use a checklists |
4 |
2 |
4 |
Aways learning something new and innovative new things. |
N/A |
Before writing new code to write correct the failed tests
|
When I am developing took long hours and my colleague was recommend me. |
Show
|
| 7 |
11 |
C |
C++, C# |
Ceedling, CppUTest |
I'm a self taught programmer |
Legacy products are tested with a handful of unit test and some system tests. No test harness is used. With new products I use Ceedling and cmock. |
Some legacy 16-bit Freescale and newer 32-bit Cortex-M based products |
STM32CubeIDE, LCPXpresso, MCUXpresso, CodeWarrior |
31-60 seconds |
K&R style braces and indentation. No automated and/or enforced coding style. |
When it's too long to keep in your head |
Git pull requests |
33 |
33 |
33 |
Getting to work on greenfield projects based on some innovative idea |
Having to use legacy IDEs such as CodeWarrior 5.1 |
I've read the TDD for Embedded C book |
I need a refresher on TDD. Not enough practice. |
Show
|
| 5 |
20 |
c++ |
c
python
lua |
cpputest |
- learned c++ at age 15
- studied software engineering at university |
- some unittests written after the fact
- some feature tests (python / behave, on a pi that talks to the test setup) |
microcontroller (mostly stm32, esp32) with freertos |
- iar for arm and stm8 projects
- vscode for esp32 projects |
31-60 seconds |
- MISRA (I disagree, since not required by industry)
- Agreement about formatting and naming |
- function does more than one thing
- many / nested branches
- a lot of lines of code |
- gitlab merge requests
- one or two team members review code
- usually takes a few days |
45 |
20 |
35 |
Working together on a problem |
Working individually |
- Write failing test
- Write mimimum code to make test pass
- Refactor
- Repeat |
I have known about TDD for a long time, but never had the opportunity to properly learn to use it. |
Show
|
| 5 |
12 |
C |
Python, C++ |
Cpputest, GTest |
Fan of your work! |
Unittest (Cpputest in target Simulator), Feature test (BDD/Gherkin/Python behave), Manual exploratory testing |
Typically custom electronics based around various types of STM32. |
IAR, VSCode |
11-30 seconds |
MISRA2012 + inhouse coding style guide (with clang-format). |
I and some colleagues use Lizard to check for length. |
Development is done in branches, other team member review code through gitlab before merging. |
20 |
70 |
10 |
Solving customer problems. |
Paper work, and customer moving the goal posts. |
I've read your book multiple times and try to apply it in my work. |
I'm convinced TDD would help me, but still find it hard to have the discipline to use it always. |
Show
|
| 20 |
5 |
C# |
PHP |
none |
Tester with basic knowledge about programming |
no testing of code |
industry software |
MS Visual Studio |
5-30 minutes |
just the simple ones - do not invent the wheel, use comments and document everything |
when I need to scroll to read the whole function |
none |
40 |
20 |
40 |
creativeness |
time consumption |
test first, then develop |
they told to do so, but I'm also interested in new things |
Show
|
| 4 |
6 |
C |
Python |
Not entirely sure |
I’m a former electrician that has re-educated myself as a software engineer. |
Unit tests, system tests, babblesim |
nRF series |
VsCode |
1-5 minutes |
Zephyr coding guidelines. |
When it is hard to comprehend what is happening inside it. |
We do the majority of our reviews on Github with a minimum requirement of two approving reviews. |
60 |
20 |
20 |
It is interesting to see a new concept or idea become reality within a short amount of time. |
Documentation. |
Not much. |
I would like to explore an alternative way of developing software. |
Show
|
| 4 |
5 |
C |
Python |
I have briefly looked at ztest in Zephyr |
I am also a certified electrician, and I play in a rock band |
We have separate developers that make tests in the Jenkins framework |
We use NCS, which is based on Zephyr RTOS |
VS Code, SEGGER Ozone |
31-60 seconds |
I think it follows many/most of the Linux guidelines |
When it takes more than a couple of minutes to understand what it does |
We use Github, need 2 approvals from code owners to merge a PR |
45% |
10% |
45% |
Can use creativity, can work from anywhere |
Today it is so complex that it is impossible to understand/wrap your head around everythig |
Nothing mutch. Unit tests are often created? |
I want to understand how to implement testing under development so that we can make sure things work |
Show
|
| 4 |
17 |
C |
C++, C#, Java |
Unity, GoogleTest, NUnit, MSTest |
I discovered your book back in 2015. Since then I've been trying to improve myself, my colleagues and other companies, pushing towards better development processes by adopting TDD and other XP practices |
I do TDD by default. But I have also some part of our legacy code base still covered by black box characterization tests (Approvals) |
Any embedded, but also some backend processing intensive related software |
Visual Studio Professional and Eclipse |
Under 10 seconds |
We do not have an enforced coding standard. We try to express intent and we refactor it mercilessly |
When it has different levels of abstractions or responsibilities inside of it |
We don't do code reviews. When there are complex things to develop or refactor, we usually pair |
45 |
50 |
5 |
Problem solving and improving things |
As usual, chasing bugs and debugging |
I think I know much more about it than the mean of devs out there, but still lot of room to improve |
Willing to improve my skills from the best teacher out there ;) |
Show
|
| 4 |
10 |
Python |
C
Linux Shell
|
Python Unittest |
I'm an |
CI using GitHub actions, Python Unittest, Actual Hardware, Zephyr shell |
Production Test Environment for development kits, shields etc. |
VSCode
West
GCC
|
1-5 minutes |
Keep the code DRY, readable and well documented. |
When it does more than what can be explained by the function name. |
We're a small team mostly doing reviews of eachother's code. |
35 |
25 |
40 |
I like the challenge of always creating something new and trying to be inventive. |
Having to fix other people's mistakes in code. |
I'm trying to practice it as much as I can in Python but I have little to no experience with it in C |
I want to brush up on my C-skills and learn how to properly do TDD in C at the same time. |
Show
|
| <1 |
9 |
C |
C++, python (I know others but don't use them often) |
none |
I've primarily worked in contract engineering and everything was "due yesterday," so I feel like testing was never prioritized. |
manual |
STM32 variants running bare metal or freertos |
IAR workbench, gitlab, github, gcc, make |
11-30 seconds |
Barr C coding standard |
when it's difficult to name it based on it's functionality. |
minimal if people have time. |
50 |
20 |
30 |
there's always a solution, you just need to figure it out. |
there are so many different ways to do a task. Decision paralysis is a real thing! |
that I should be using it, that it minimizes development and debug time. |
I don't get it. I know I need to do it, but I can't wrap my brain around "how" I use TDD. |
Show
|
| 0 |
2 (+5) |
C |
Python, C++ |
- |
- |
Unit testing |
Zephyr |
VS Code |
31-60 seconds |
- |
The function is too long if it does more than what can be described in the function name. |
- |
50 |
20 |
30 |
It combines logical thinking with creativity. |
Solitary work |
TDD focuses on writing unit tests before or alongside coding the functionality. |
I want to be able to create reliable software more efficiently. |
Show
|
| 1.5 |
14 |
C |
Python, bash |
ceedling, google test |
i have been doing embedded firmware for over 10 years, primarily for low power wireless systems. |
unit testing, on-target tests, integration tests. |
embedded wireless system. |
gcc |
1-5 minutes |
coding standard covers basics, is not burdensome. |
> 100-200 lines. |
reviews are productive, much less wasted time on nits than previous jobs. |
50 |
25 |
25 |
problem solving challenges |
getting caught up in legacy bugs. |
I have used tdd on and off throughout my career, I find it is a useful to drive modular designs. |
partially driven by management but also to refresh my skills. |
Show
|
| 6 |
11 |
C |
Python |
CppUnit |
I've lived in NY for most all of my life. I enjoy playing sports - soccer, softball. |
One of our codebases uses CppUnit for our higher level software modules. Legacy repositories we rely purely on functional testing driven from our serial interface, IoT communication, Mobile Apps, etc. |
Few different MCUs used in our products. They are all Cortex-M (M0, M3, M4). ~1MB flash/100s KB RAM. |
GNU toolchain, J-Link, VS code, RS-232, |
1-5 minutes |
We do have a coding standard defined for C/C++ and Python. |
We do leverage a cyclomatic complexity tooling. Otherwise, I use 100 lines as rule of thumb. |
Use GitHub for source control and require a PR for merging all code. |
60 |
25 |
15 |
Very interesting that there are so many ways to solve a problem - love finding an optimal solution |
Writing unit tests |
Not too much honestly |
Better my development approach. Also, bring effective strategies to the team. |
Show
|
| 3 |
12 |
C |
Python
Groovy
|
CppUTest
|
. |
On-target |
A cortex-m4 based board running FreeRTOS |
J-Link
GDB
Saleae
|
11-30 seconds |
Largely based on CERT C standards, focused on safety, correctness, and clarity. |
If you have to ask, it's too long |
Done online, 2 approvals required |
50 |
20 |
30 |
Problem solving |
Testing |
It takes the fun out of programming |
My boss told me to. |
Show
|
| 10 |
25 |
C |
C++
Python
Rust |
CppUTest |
Embedded Software Consultant |
Unit testing with a test harness and then system level testing using a custom Python test harness that interacts with the hardware system. |
varies based on the project |
A wide range. Visual Studio Code, Eclipse, CppUTest, Metrix++, Understand, etc |
Under 10 seconds |
Generally adhere to directives in MISRA-C. Style standard is custom for C/C++. |
when it starts to have multiple conditionals. |
usually done with customers |
70 |
20 |
10 |
The usefulness of writing software that controls electronic systems. |
Delivery time pressures and the lack of budgets to get things done. |
Fair amount. Have read several books. Used it on several projects. |
To evaluate the self paced course and fill in knowledge gaps to improve my development activities. |
Show
|
| 0.4 |
6 |
C++ |
C, Python, R, JavaScript, MIPS and 80x86 assembly, bash, SQLite |
CppUTest, Python unit tests |
I love living in the PNW, and will be in the mountains any chance I get |
CppUTest |
Glass panel displays for experimental planes & other light aircraft. |
Docker, VSCode (including VSCode debugger), GDB |
5-30 minutes |
My company doesn't have one. Follow your heart and whatever's in the file you are working on |
If it's longer than 1-2 screens, or is trying to do too many separatable things |
We use Crucible and GitHub pull requests |
3 |
3 |
4 |
Problem solving/finding bugs is the best. During design, I love planning for each scenario |
When I'm stalled out by problems with my tools |
You plan what/how you're going to test, and use that to drive design (like how to split functions) |
It's required, but I am excited to learn more about TDD |
Show
|
| 24 |
28 |
C# |
C++ |
VS Unit tests |
|
Test apps, unit tests |
Windows |
Visual studio 2019, 2022 |
31-60 seconds |
readable and maintainable code |
- contains more than one if, cycle, switch statements
- doing more than it was designed for |
- critical parts reviewed in pairs |
90 |
5 |
5 |
- design phase, putting things together |
- fixing anomalies on customer systems |
almost nothing |
organized by company, I would like to know more about TDD to be able to use it |
Show
|
| 16 |
25 |
C# |
C++ |
MSTest |
I like getting my job right. |
Stepping through code during a debug session
Debug.Assert
reading through the code and double-checking
unit tests (both written in advance and after the code) |
MS Windows |
Visual Studio |
11-30 seconds |
I don't think I am using a formalized coding standard |
probably when it exceeds two pages |
none |
50 |
30 |
20 |
The feeling when it all fits and is useful for somebody else. |
Struggling with the tooling to even more forward. |
I think I heard it a few times defined. |
I was asked to. |
Show
|
| 26 |
35 |
C# |
C/C++, PHP |
Unit tests in Visual Studio |
I am mostly working on server-side and communications. |
Something with unit tests, but most just by running it in the test lab. Note that the communication requires testing many simultaneous connections, testing connection failures etc. and this may not be feasible with the unit tests. |
Not sure what the question means. |
Visual Studio 2022 |
5-30 minutes |
Not sure what 'coding standard' means. |
It does not fit on one screen (there are exceptions though) |
We don't do code reviews too often. Usually only when fixing an already reported critical issue. |
40 |
10 |
50 |
Creating new stuff - when it starts working for the first time. |
Maintaining old code, repeated work. |
Unit tests running during the build, which should guarantee that code did not get broken. |
We want to spend less time on maintenance. |
Show
|
| 19 |
33 |
C# |
JavaScript (Node.js) |
Unit tests in Visual Studio |
experienced C#/.NET developer, less experienced in JavaScript/Node.js, experienced with deployment of .NET apps in Linux based Docker containers |
running the application in various use cases, checking the code and its behavior/results in debug mode |
Microsoft Windows, Docker containers based on Linux (Ubuntu, Alpine) |
Visual Studio 2022 |
1-5 minutes |
naming conventions, short functions, using indentation, using comments, not using globals |
if it does not fit on the screen |
not using code reviews, just rarely |
50 |
30 |
20 |
it is a creative work |
it is sometimes stressful, e.g. when finalizing the code close to release date. |
not much |
want to learn something to be more efficient, training arranged by managers |
Show
|
| 10 |
18 |
C# |
JS, C++, TSQL, C, HTML |
MSTest in Visual Studio |
I'm a senior software developer. In ICONICS I'm working on both front end and back end projects in .NET (C#). I'm mainly focused on the configurator tool of our product and in some server side tools (e.g. to generate reports). |
In the last couple of years I started using unit tests. So in general I write the code and in parallel I create unit tests on the code I'm writing. When I don't have unit tests, I test it in debug mode. |
I usually work on Windows and I develop .NET projects. |
I use Visual Studio 2022 and MSTest to generate the unit tests. |
31-60 seconds |
I try following the C# Coding Standard Best Practices provided by Microsoft |
When it does too many things and I cannot give it an auto explicative name. |
I don't have a specific check list. I check complexity, readability, error handling, functionality. |
50 |
25 |
25 |
I like solving problems. I like writing clean and readable code. |
Usually I don't like writing code when it's too much repetitive and hard to maintain and understand. |
I read some books when I was at the University. Unfortunately I never used it when working. |
Because I'm really interested to understand how I can improve the way I write and test my code. |
Show
|
| 20 |
25 |
c# |
js, c++ |
ms unit tests, jest |
- 1 year as net supervisor, 2 years in QA, 3 years as sw dev, 15 years as sw architect/team lead
- front-end, back-end, communication, tools
- prev 10 years in c++/VBA, now 12 years in c# and 1 year js/react
- indie game developer (ue, monogame) |
old ms unit tests, custom testing tools |
web, desktop, mobile |
vs 2022, vs code |
2-4 hours |
company freestyle, but everyone eventually and naturally synced with others |
it's hard to read/understand or has some flaws (side effects etc.) |
we do code reviews for critical pieces/when doing changes in someone else's code |
5% |
10% |
10% |
cooperation with customers, feedback, visiting customer sites to see it all in action |
"management", competitive instead of collaborative environment, lack of long term vision |
we are only experimenting with tdd due to lack of time |
proposing agile since 2008, practicing some agile techniques unofficially for several years in team |
Show
|
| 2 |
9 |
C# |
I've used some python and java during my university years |
junit, xunit |
I'm a relatively new software developer in the company, this is my first job after university |
To be honest i don't for the most part - when I do I write unit tests in xunit but I never used a formal TDD approach |
We target .NET systems |
Visual Studio |
11-30 seconds |
I try to keep it consistent with code written by others in terms of formatting, names, comments, etc |
Usually when I have to use the mouse wheel to read it all |
We don't really do code reviews, except after I've deeply changed code written by somebody else |
50 |
10 |
40 |
When the code I've written is helping solve a problem. It helps if it does so in an elegant way. |
I don't really enjoy having to spend much time figuring out what code written by somebody else does. |
I understand the idea behind it and the overall process |
To improve my coding habits |
Show
|
| 11 |
17 |
C# |
javascript
typescript |
jest |
|
Manual testing, screen capture testing |
Web, Mobile, Windows |
Microsoft Visual Studio
Microsoft TFS |
2-4 hours |
Focus on readable code |
If it doesn't fit to one screen |
Only if requested |
60 |
10 |
30 |
Creating new stuff |
Fixing bugs |
First write the test than the code |
Company iniciative |
Show
|
| 10 |
25 |
C |
Python, ASM |
N/A |
I started coding because the teacher in 4th grade told us we could each play a computer game until we ran out of lives. I modified the program to have unlimited lives when I played. |
Black Box/White Box/Use Case/Boundary Condition/Code Review driven scenarios/Regression |
Small scale embedded systems |
Device specific development environments, MP Lab, Code Composer, Atmel Studio, Segger, VS Code |
1-5 minutes |
We have a development standard in our group that I helped develop. |
Length, when I can't quickly articulate or name what it does. |
Small group, 1-3 people, criticality driven level of rigor. |
40 |
30 |
30 |
The challenge, problem solving, the act of making something. |
Feature creep, the idea that 'software is cheap/free' |
Admittedly not a lot. |
To learn and get better! You can't test everything, make it count! |
Show
|
| 11 |
15 |
C |
Python, LabVIEW |
None |
I had a difficult time with C++ in university. |
Functional validation, black box, white box, error path validation |
Embedded systems, now mostly ARM targets, multiple processors |
MPLAB, Segger, GCC, Eclipse |
30-60 minutes |
Internally developed, includes MISRA-C compliance. Systems comply with MIL-STD-882 System Safety. |
When I struggle to hold it in my mind. |
Nonstructured |
40 |
20 |
40 |
Putting the magic into systems |
The suspicion that the whole codebase is a sandcastle. |
It is an imposed discipline, somewhat monk-like, that purports to keep the demon dogs at bay. |
TDD has been on my radar for a long time, but I haven't dedicated the time to investigate. |
Show
|
| 4 |
17 |
C |
C++, C#, Java |
Unity, GoogleTest, NUnit, MSTest |
I discovered your book back in 2015. Since then I've been trying to improve myself, my colleagues and other companies, pushing towards better development processes by adopting TDD and other XP practices |
I do TDD by default. But I have also some part of our legacy code base still covered by black box characterization tests (Approvals) |
Any embedded, but also some backend processing intensive related software |
Visual Studio Professional and Eclipse |
Under 10 seconds |
We do not have an enforced coding standard. We try to express intent and we refactor it mercilessly |
When it has different levels of abstractions or responsibilities inside of it |
We don't do code reviews. When there are complex things to develop or refactor, we usually pair |
45 |
50 |
5 |
Problem solving and improving things |
As usual, chasing bugs and debugging |
I think I know much more about it than the mean of devs out there, but still lot of room to improve |
Willing to improve my skills from the best teacher out there ;) |
Show
|
| 4 |
17 |
C |
C++, C#, Java |
Unity, GoogleTest, NUnit, MSTest |
I discovered your book back in 2015. Since then I've been trying to improve myself, my colleagues and other companies, pushing towards better development processes by adopting TDD and other XP practices |
I do TDD by default. But I have also some part of our legacy code base still covered by black box characterization tests (Approvals) |
Any embedded, but also some backend processing intensive related software |
Visual Studio Professional and Eclipse |
Under 10 seconds |
We do not have an enforced coding standard. We try to express intent and we refactor it mercilessly |
When it has different levels of abstractions or responsibilities inside of it |
We don't do code reviews. When there are complex things to develop or refactor, we usually pair |
45 |
50 |
5 |
Problem solving and improving things |
As usual, chasing bugs and debugging |
I think I know much more about it than the mean of devs out there, but still lot of room to improve |
Willing to improve my skills from the best teacher out there ;) |
Show
|
| 1 |
15 |
C |
C++, Python |
cpputest |
I am a strong believer in embedded unit testing, but rarely been a priority at my previous companies. I'm excited that Latch is prioritizing it for current and upcoming products and really hope this course helps me to take full advantage of it. |
Limited unit testing, mostly scripts that regression test the code running live on the end product. |
Variety, but the current product is using a Cypress PSOC 6. |
GNU, clang, visual studio code, python for scripting, etc. |
31-60 seconds |
The firmware team coding standard here at latch is fairly comprehensive but focused on readability. |
Good question, its really just been gut feel so far. |
Every PR require's at least 2 sign offs and we have several static analyzers running. |
50 |
25 |
25 |
I like to get the most out the available HW particularly taking advantage of custom HW blocks. |
I hate having to worry about formatting. I love code beautifiers for that so i dont have to worry. |
I dont know enough and need to know more. |
I want to take advantage of unit testing more, but my background base is not strong enough. |
Show
|
| 1 |
7 |
C |
C |
No |
Interested in embedded software development |
Unit test |
Microcontroller |
Keil |
1-5 minutes |
No std |
More than 300 lines of code implementation |
No review |
7 |
2 |
1 |
It’s complexity |
Debugging |
Nothing |
Want learn new methodology. |
Show
|
| 1 |
10 |
C |
Python
YAML
MATLAB/Octave
C++ |
cpputest |
I am also an ultra-endurance athlete |
cpputest, docker, pmccabe, cppcheck, GitLab CI |
We program for ARM 32 bits chips, mainly NXP |
Visual Studio Code
NXP S32 Design Studio
Segger tools
Busmaster |
11-30 seconds |
ALL warnings, Internal naming conventions, No globals |
When it doesn't fit in a single page |
None at the moment |
20 |
30 |
50 |
Making electronics do stuff and the endless search for better methods or solutions. |
The ease of not being rigourous and the multitude of tools/methods applicable. |
Tried on my own based on articles and workshop. Used cpputest starter project. |
See how TDD is done properly and in depth. How to apply it efficiently to firmware developement |
Show
|
| 9 |
29 |
C |
I have used Java and C for other outside jobs and hobby, but pretty well my livelihood is C |
None, but after taking EOC courses, it looked like something my company could use |
I started designing h/w and s/w, as a jr engineer for a sr EE, I loved it. I took time off as an FAE for electronic distributors(~13 year). I went back to design with my current company and have migrated to almost 100% software. |
Burn and churn :-) That's why we are taking the course. We have went through many of the TDD solutions/warnings given - Fix Code breaks other code, invalid one-off inputs are not seen until the code is in the field........ |
Migrated from PIC32 to STM32F |
Mfr's IDE, have started to dabble with MS Visual Studio Code, but in the past I edited with Sublime |
31-60 seconds |
Still working on that, we only have 2 firmware coders and could use one. |
We don't |
2 embedded coders, sometimes working the same project, and we use github code review's to merge. |
45 |
10 |
45 |
It's the challenge of making s/w and then improving it, and learning from others. |
Nothing |
Not much |
To implement s/w development improvements that will make our code better |
Show
|
| 3 months |
10 years |
Embedded C, C |
C++ |
CPPUNIT |
Firmware Engineer in proficient with C, Embedded C nd C++ languages.
Also use of scripting languages like shell and python |
Yes |
MSP430 and Silabs MCU |
IAR Embedded Workbench |
1-5 minutes |
Misra C and BARC |
Too many tatements, unnecessary dependency on other functions, extra work not relsated to arguments |
coding standards, Completion of logic and for better logic and any performance issues |
1 hr |
2 hr |
2 hr |
debugging and trying to failure system |
unnecessary adding and testing |
Where , when and how to test |
To make use of TDD in our projects |
Show
|
| 1 |
4 |
Python |
Matlab |
pytest |
Robotics researcher |
run against data locally |
Nvidia Jetson |
VS Code, Git |
11-30 seconds |
Pep-8 |
Put time statements |
Few to none, small team |
33 |
33 |
33 |
The flow |
Reading API docs |
It reduces pain |
Want to learn embedded |
Show
|
| 1 |
38 |
Rust |
C, C++, Clojure, Lua |
Rust Test, Demonstrate, GoogleTest, CPPUnit, Catch, LuaTest, Clojure.test, Gerkhin |
One of my hobbies is producing a table-top air combat wargame called "Birds of Prey - Air Combat in the Jet Age"... check it out at www.airbattle.com |
Requirements tests in Gerkhin, Integration tests in Rust Test with wrappers for target external interfaces, Unit tests in Rust Test on workstation. Test driven all the way down. |
Mix of ARM M7 with RTOS and ARM A-series with RT-Linux or RTOS. (Large-ish memory embedded systems.) |
Git, VS Code, rust-analyzer, clippy, cargo, probe-rs, lldb |
31-60 seconds |
All clippy checks, style: "rust fmt", nostd, no dynamic memory, ANSSI Guide for secure app in Rust |
Prefer to end up at ten lines or less.
Algebraic type match statements may create an exception. |
Primarily continuous with mob programming. There is a formal process for addressing certain risks. |
40 |
45 |
15 |
Creating tests and making them pass. Delivering products that help people. |
Being stuck doing leadership stuff that keep me from writing code... |
I've been using TDD since early XP days (~1999) |
To have my team hear about TDD from another voice. |
Show
|
| 0 |
18 |
Java |
JavaScript
C#
Rust |
JUnit
NUnit
xUnit
Mocha
Jasmine |
I started with Bionaut July 5th. I'm learning Rust and embedded programming. My role is accountable for the test automation of Verification tests. |
Using TDD for writing code. A mix of unit, integration and verification tests will be written around requirements. |
Embedded Rust on a safety critical system. |
Rust in VSCode |
Under 10 seconds |
Iterative development using TDD. |
When it does more than one thing outside it's level of abstraction. |
Unstructured as the team primarily mobs. Code created outside the mob will be reviewed ad hoc. |
100 |
100 |
0 |
It's a philosophy in there is no one way to solve a problem |
The (capitol A) Agile dogma.
Story Points
|
TDD is used to drive out code design. The byproduct is an automated regression test suite. |
Phil made me. |
Show
|
| .1 |
5 |
C |
Rust
C++
Python
Bash |
unittest (Python)
the standard Rust unit tests thing |
I love operating systems. I've bricked more linux installs than I can remember, and I'm fairly comfortable with the Linux manpages. |
We use TDD with the built-in Rust tests. We set up cargo-watch to run the tests on save |
Initially, it's two NVidia Jetson boards and a PC (not sure if it will be Windows or Linux) |
VSCode
Vim |
Under 10 seconds |
We don't really have one for Rust, our main language. Our C++ standard for vendors is in-progress. |
"when it does more than one thing" - Bob Martin
Sometimes you have to compromise on this though. |
Don't do 'em because we're always mobbing. |
38 |
60 |
2 |
I get to constantly learn new things. |
How much time I have to sit in front of a computer. |
Mainly just the red-green-black cycle. |
I hope it'll help solve issues I've had doing embedded TDD, like step one of serial port comms. |
Show
|
| 1 |
10 |
Rust |
C,C++,Python |
A few random |
I'm pretty good at baking. |
Unit tests, HIL tests, integration tests |
Multi-processor safety critical |
Rust tool-chain
|
1-5 minutes |
Coming soon! |
I get super annoyed if I have to scroll through files. The shorter the better. |
Mob/Collaborative review. Real-time full-team |
40 |
40 |
10 |
Building interesting things at minimal personal expense.
|
pre-processor macro magic. spending a day debugging because I failed to test fully. |
Class alumni! |
It's a great class |
Show
|
| 0 |
10 |
C |
Java
Scala
Python
C++ |
JUnit |
I really enjoy going on hikes in my free time |
Manually |
Linux embedded system |
SVN, GitHub, VS Code |
5-30 minutes |
I clean and readable. |
I would say once it starts getting around 100 lines. |
I need to learn some of the things. |
5 |
1 |
4 |
Debugging and learning where I could have done better and seeing the constant improvement. |
Coming up with ideas for side projects |
I know it is something I need to do more of. |
Work offered it and I know I need to get better at it. |
Show
|
| < 1 |
3 |
C++ |
Python and Rust |
Pytest |
Senior level CS major at UCR. |
Code is tested using our unit tests within our source code and our integration test which are written as cucumber tests. |
Target system is an Nvidia Jetson Nano. |
Github, vscode |
11-30 seconds |
Descriptive code with minimal comments. Camel case for var names. |
When it has more than one task. |
We do not have standard code reviews. |
30 |
50 |
20 |
Creating something useful that automates a certain task. |
Solving a bug that creates a new list of bugs |
TDD is a software development process where tests are created before production code. |
To learn better TDD test practices. |
Show
|
| 0 |
3 |
Python |
Rust, C, Java |
PyUnit,
np.testing,
JUnit |
I just graduated from Georgia Tech this past may |
TDD, unit tests + integration tesets |
tbd |
VS Code, github |
Under 10 seconds |
tbd |
If another function can be extracted from it, its too long |
tbd |
40 |
20 |
40 |
Creating something useful and reliable |
Having to be responsible for all the tiny nitty-gritty details |
It can be a really effective method many applications (I struggle using it for algorithm dev) |
To stop spending so much time thinking how to write a test first using TDD |
Show
|
| 0 |
10 |
Rust |
C, C++, Python, JavaScript, Java |
Googletest, JUnit, Jasmine, Rust's test framework |
I enjoy testing and embedded software development. |
Unit tests, integration tests (including hardware in the loop) |
Target system is a multi-processor system with several ARM boards. |
VSCode, WSL, Rust Analyzer |
11-30 seconds |
Rust - mostly use rust's built in tools
C++ - mostly based on MISRA standards (I think) |
When it does more than one thing or is more than a few lines long. |
Continuous reviews as part of mob programming practice |
15 |
35 |
50 |
I like the creativity and problem solving that it requires. And I like building cool things! |
Most of the overhead such as meetings and planning (although I know they're important) |
Ideally the process is write a test that fails and then update the code to get it to pass. |
My whole team was signed up for it. |
Show
|
| 0 |
10 |
C++ |
C++/C, python, rust |
C++unit, Qunit, google test, boost unit test, pytest |
I have a variety of hobbies which range from outdoors to on computers. |
Test in layers starting with unit tests. Then go up to from component test, integration tests, system, and release tests. |
Embedded system communicating with PC. |
VS code and rust. |
1-5 minutes |
Pretty standard |
I get lost in the length. |
What reviews? |
50 |
40 |
10 |
The ability to take useless HW and make it do something. |
It can be frustrating to get things to work properly. |
Make sure you have well defined tests before trying to solve the problem. |
The company signed me up. |
Show
|
| 0 |
2 |
Rust |
C/C++, Python |
None |
I am a Biomedical engineering major who graduated June 2021. Though I have taken CSE classes, I am still relatively new to programming and embedded systems. With my limited experience, I look forward to learning from this training. |
Applying test driven development, we first write a failing unit test to drive writing production code features until the unit test passes. We refactor or repeat the process and write HIL integration and verification tests using Gherkin and Cucumber. |
The current target is a 2 GB NVIDIA Jetson Nano. |
VSCode, Github |
Under 10 seconds |
Currently our team does not have an official Rust coding standard. |
A function is too long when it encapsulates multiple processes and purposes for the system. |
Following mob programming software development, our team has real time code review. |
35 |
60 |
5 |
Problem solving and ability to create new possibilities and capabilities that seem like "magic". |
Sometimes to be better at SW dev, you must sacrifice your time to enjoy other aspects of life. |
I understand and try to apply the general concepts of TDD. I'd like to improve my TDD abilities. |
I'm new to embedded systems and programming. I'd like to improve my ability to write quality tests. |
Show
|
| 1 |
5 |
C |
C++, Python |
BoostTest |
Embedded engineer from Ireland who is tired of using compilers from 1989 |
Mainly using end-to-end and functional tests |
Battery management system |
Clion, vim, gdb, openocd, git, compiler explorer |
11-30 seconds |
No official standard |
When it becomes unclear what the function does. |
Pull requests are made per feature change. One approver actively working on the project is required |
60 |
20 |
20 |
Getting to architect+implement+maintain systems. I feel few other engineering disciplines do all 3 |
Embedded Software Development feels years behind in terms of tools, testing, process quality,etc |
Write the test first |
Won a competition and I think tdd could be a more enjoyable way to write software |
Show
|
| 5 |
6 |
c |
c++, python |
not sure what harnesses mean |
I am EPM in Marvell, so not programming anymore |
I am EPM in Marvell, so not programming anymore |
I am EPM in Marvell, so not programming anymore |
I am EPM in Marvell, so not programming anymore |
5-30 minutes |
I am EPM in Marvell, so not programming anymore |
I am EPM in Marvell, so not programming anymore |
I am EPM in Marvell, so not programming anymore |
0 |
0 |
0 |
I am EPM in Marvell, so not programming anymore |
I am EPM in Marvell, so not programming anymore |
I am EPM in Marvell, so not programming anymore |
I am EPM in Marvell, so not programming anymore |
Show
|