| 2 |
5 |
At work C |
At home python and circuitpython |
CPP U-Test |
I took your class last year
|
Show
|
| 3 |
30 |
BASIC |
C, C++, Python, Java, Javascript, GDScript |
VectorCast, Unity |
Almost nothing.
|
Show
|
| 3 |
9 |
C |
Assembly, C++, Python |
cpputest, unity, pytest, custom |
You have unit tests as the first consumer of your code. They sort of work as requirements.
|
Show
|
| 3 |
10 |
C |
Python, basic C++ |
N/A |
I am aware that it is a practice where the test case is written before the code is changed to pass
|
Show
|
| 2 |
20+ |
C |
Objective C |
Unity |
Test Driven Development
|
Show
|
| 2 |
20 |
C |
C++, Python |
Unity |
writing test cases first and then developing software against it to pass the tests.
|
Show
|
| 5 |
30 |
C |
Python, C++ |
Unity, Google Test |
A little exposure in regard to writing negative UT followed by positive UT and, finally, code.
|
Show
|
| 0.125 |
6 |
C |
Java, C++, Python, R |
n/a |
n/a
|
Show
|
| 2 |
12 |
C |
Python |
CppuTest |
I'd say pretty much nothing, bare minimum
|
Show
|
| 1 |
8 |
C |
C++ |
CxxTest |
I took a course on TDD at university.
|
Show
|
| 6 |
20+ |
C |
Python |
CppUTest |
I familiar with the TDD process and have applied it to simple examples.
|
Show
|
| 1 |
15 |
C |
C++, C#, Python, Javascript |
AceUnit, CppUTest, Zephyr's ZTest |
I've taken this course before, about 7 years ago with a different employer. I've practiced it since.
|
Show
|
| <1 |
9 |
C |
Java
C++
C#
Python
VHDL |
None |
I understand its power and utility. I've heard it talked about. I have never seen it executed.
|
Show
|
| 4 |
7 |
C |
Python
JavaScript
C#
CMake and Linux scripts (if they count) |
A little bit of CPPU Test |
I understand the idea of building and testing smaller chunks of code incrementally
|
Show
|
| 3.5 |
15 |
C |
C#, python |
cpputest, nunit |
I've taken your in-person class before (about 8-9 years ago) when I was at Cirque Corporation.
|
Show
|
| 1.5 |
9 |
C |
C++
C#
Python |
Specflow
RobotFramework
GTest |
A little. Write tests before starting, develop, pass tests.
1st module of self-paced
|
Show
|
| 3 |
10 |
C |
Python, C++ |
VectorCast, Unity, Ceedling |
Not so much, I guess it is a methodology to develop software by defining test first.
|
Show
|
| 3 |
30 |
C |
Objective-C, C, C++, C# |
Ceedling, CMock |
We already use TDD but we want to be sure that we use it correctly.
|
Show
|
| 2 |
18 |
C |
Assembly, Python |
Unity |
I read the bee book :-)
|
Show
|
| 8 |
20 |
C |
Python, C++, C# |
Google Test and Unity (Throw the Switch) |
Write test first!
|
Show
|
| 5 |
6 |
C |
Python |
None- brand new to unit testing |
Zero- we talked briefly about the idea of testing in chunks as you code
|
Show
|
| 2 |
15 |
C |
C++, C#, Rust |
gtest |
learning more about testing and changing my coding style
|
Show
|
| 1 |
20+ |
C |
Python
Go
C++
Octave/Matlab
|
Catch
CppUTest
Unity
GoogleTest |
I've been practicing it for many years. I have a copy of your book that I evangelize about.
|
Show
|
| 1 |
12 |
C |
C++
C#
Python |
GTest
Specflow
Robot Framework |
Usually used by Software Engineers, not necessarily firmware due to hardware constraints
|
Show
|
| 3 |
3 |
C |
python |
None! |
TDD will:
make development more systematic.
be less debug time.
tackle problems as they appear.
|
Show
|
| 12 |
40 |
C |
Assembler |
Ceedling |
All I know about TDD is that tests are written before writing any code
|
Show
|
| 1 |
19 |
C |
C++, python, matlab |
Custom, Google Test |
Swap the development flow and write test first, code second. Ensure quality standard designed aside.
|
Show
|
| 2 |
4 |
C |
C, Type Script |
Tried using Unity |
Recently introduced to TDD while working on unit testing
|
Show
|
| 0 |
10 |
C |
C#, C++, Python |
NUnit |
It reduces time finding bugs so we can code more efficiently.
|
Show
|
| 8 |
21 |
C |
python, vb |
none |
some exposure to it, took a small course but don't actually practice it.
|
Show
|
| 7 |
20 |
C |
Qbasic, Megabasic, Rust, C++, Visual C, xaml |
None |
Not much formally but have been doing it informally for years
|
Show
|
| 5 |
12 |
C |
CPP |
None |
Not yet aware
|
Show
|
| 1 |
10+ |
C |
JavaScript, C#, C++, Assembler |
none/unknown |
I read the first few chapters of the Grenning book years ago.
|
Show
|
| 0 |
5 |
C |
None significantly |
None significantly |
Mildly familiar from college education.
|
Show
|
| 1 |
10 |
C |
C++
Python
Powershell
|
pytest
company uses google test |
dipped my toes into it, started using it a little bit
|
Show
|
| 1 |
5 |
C |
C++, matlab, python |
cFS unit test framework
|
it helps in writing code and tests in a more effective way
|
Show
|
| 2 |
10 |
C |
C++, python |
cFS unit tests framework, lcov |
it relates to incrementally build unit tests, extending them while the tested feature advances
|
Show
|
| 7 |
10 |
C |
Fortran, C++, Java |
check, gtest |
I read TDD for C/C++ about one year ago, and It is reducing a lot of uncertainity
|
Show
|
| 6 |
>12 |
C |
Python
C++ (very rarely) |
None |
Writing tests for all code upfront. Testing first and throughout development.
|
Show
|
| 1 |
3 |
C |
C++, Python, Shell/Bash scripting |
C- libcheck
C++ - googletest
Python - pytest |
I've read the Test-Driven Development for Embedded C book and took some university lessons.
|
Show
|
| 2 |
5 |
C |
Only C |
N/A |
There is a book related this book from James Grenning.
|
Show
|
| 0 |
16 |
C |
Python, C++ |
CppUTest, GoogleTest |
I have read your book in the past and have written some unit tests.
|
Show
|
| 3 |
20 |
C |
python, C++, pic basic, vhdl, verilog |
none |
nothing
|
Show
|
| >1 |
8 |
C |
C++
Python
TypeScript
Dart |
Ceedling |
Unit tests are created during planning for new code, and unit tests guide development of code.
|
Show
|
| <1 year |
10 |
C (Embedded) |
Python, C++, Rust, Bash |
CMocka, Twister, Unity, Pytest, and in-house Rust/Bindgen C framework. |
I've learned about it in the past and tried using it on smaller personal projects, not professionall
|
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 know our Embedded/software personnel are adopting it based on wingman training
|
Show
|
| 1 month |
roughly 20 |
C# |
C++, Javascript, Java |
NUnit |
No code written without a test for it. So far love the theory never been able to achieve practically
|
Show
|
| 13 |
25 |
C# / python |
C, php, C++, java, VB.net |
pytest, ceedling, MSTest, phpunit |
It's a great method to delivering good tested code, but is a hard habit to maintain
|
Show
|
| 3.5 |
40 |
C++ |
ASM, C, LUA |
GTest
Many Proprietary |
I have developed TDD culture within new software teams in the past due to project SDLC requirements.
|
Show
|
| 16 |
24 |
C++ |
C, Python, Lua, ASM, JS |
Homespun |
High level concepts, but I've been in Old School games too long to have much experience with it.
|
Show
|
| 4 |
12 |
C++ |
Python, C#, TypeScript |
GoogleTest, PyTest, JUnit |
Red, Green, Refactor
|
Show
|
| 8 |
35 |
C++ |
C#, python |
tcl/tk, gtest, many custom ones |
It should be capitalized :)
I did a course on it a long time ago, but have not used it much.
|
Show
|
| 12 |
40 |
C++ |
For work, SQL |
Nothing extensively |
Just that its test driven development.
|
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 |
Tests first - they are expected to fail, and then write the implementation until the tests pass
|
Show
|
| 3 |
14 |
C++ |
Python
C# |
We have a CID system that runs some basic tests |
You design a test for the thing you want to accomplish, write code to pass the tests, repeat
|
Show
|
| 3 |
8 |
C++ |
Python
C# |
Catch2
Google Test
pytest |
Writing the failing test first and then writing code.
|
Show
|
| 4 months |
3 years |
C++ |
C, Python |
I use CxxTest with custom stubs for unit testing in embedded C++ projects. |
I know TDD means writing tests before code, ensuring requirements are met and reducing defects early
|
Show
|
| 20 |
27 |
C++ |
C, python |
boost.test, catch, catch2, xUnit, pytest, gtest/gmock |
I have been using it for over 15 years, also am aware of ATDD (not using it now)
|
Show
|
| 2 |
10 |
C++ |
Python, MATLAB, C |
None |
The tests come first before the development
|
Show
|
| 0.66 |
3 |
C++ |
C#, Qml |
None |
Very little. Think of what the output should be, write the tests, then the function.
|
Show
|
| 0.24 |
20+ |
C++ |
C, Python regularly
Go occasionally |
CppUnit, GTest, Catch2, doctest, but not extensively or any of them. |
A read James' book many years ago.
|
Show
|
| 11 |
28 |
C++ |
C/C++/Assembly(arm)/Python |
gtest |
nothing
|
Show
|
| N/A |
30 |
C++ |
Python, PowerShell,.NET, bash |
JUnit, Catch, GoogleTest |
Basic level
|
Show
|
| 4 |
15 |
C++ |
Python |
Proprietary tool |
Having unit test cases ready before development itself, so that all the modules can be tested
|
Show
|
| 5 |
9 |
C++ |
C, python |
gtest, Testwell CTC++ |
Have been trying to follow this approach since moving to agile teams
|
Show
|
| 15 |
25 |
C++ |
C
python |
gtest |
tests are done before the code
|
Show
|
| 3 |
6 |
C++ |
Python, Java, C#, qml |
CppUTest |
You write a test and then code to make the test pass
|
Show
|
| 7 |
20+ |
C++ |
Python
former fullstack .net |
GTest
Pytest
xunit
mspec
specflow |
Read several books
|
Show
|
| 1 |
14 |
C++, Java |
C#, Python |
GTest, JUnit |
A lot, worked at EPAM, tried it at workshops.
|
Show
|
| 1 |
25 |
C++, Rust |
Python, shell |
Boost |
It is a methodology to create software where tests are written before the code.
|
Show
|
| 10 |
15 |
C, C++ |
Scripting, Java |
Boost |
It is about as and when coding is done, testing is also done. This avoids iterative process.
|
Show
|
| 7 |
12 |
C, C++ |
Python |
Command line interface is used to execute the SW/APIs added with various arguments. |
TDD is basically writing SW for the already defined test cases.
|
Show
|
| 10 |
15 |
C,C++ |
python |
pytest |
Heard before. But will learn now.
|
Show
|
| 0 |
30+ |
C/C++ |
HLSL, C#, Python, assembly |
Some, I forget the names. |
Quite a bit. I have seen it taken way too far.
|
Show
|
| 5 |
30 |
C/C++ |
Python, Rust, Javascript |
Google test, built in rust test harness, some python ones I don't remember |
I hear a lot of zealotry, but have little real world experience with it.
|
Show
|
| NA |
12 |
C/C++ |
Python, Ruby, Javascript |
Unity, CppUTest |
It's a practice for building software incrementally guided by tests.
|
Show
|
| 2 |
26 |
C/C++ |
C#, python |
cUnity, cpputest, gtest, cxxtest |
I've read a few books, including "Test-Driven Development for Embedded C"
|
Show
|
| 9 |
20 |
C/C++ |
Python, Java |
Google Test |
Test Driven Development, is when you write the tests from the requirements prior to the code.
|
Show
|
| 0 |
40+ |
C/C++ |
Python F# Forth |
CUnit |
Very little
|
Show
|
| 1 |
30 |
Embedded C |
C++ |
none |
Don't know yet, still learning
|
Show
|
| 2 month |
7 years |
Embedded c |
C++ language |
Not yet used my project. |
not more
|
Show
|
| 15 |
28 |
JS |
Python
c++
Actionscript
java
Various embedded |
FlexUnit
JUNIT
Mocha
Puppeteer
Cypress |
Used to teach Flexunit testing with a focus on TDD. Helped write flexunit 4.
|
Show
|
| 3 years |
20 |
Java |
C,C++ Python. |
JUnit |
Using it during my previous projects.This is the reason of introducing it in our development
|
Show
|
| 1 |
17 |
Python |
C, C++ |
CxxTest |
Nothing… my mind is a blank canvas ready to learn!
|
Show
|
| 0.5 |
15 |
Python |
C#, C++, Rust, Java, Fortran |
Rust test, pytest |
-
|
Show
|
| 1 |
4 |
Python |
JavaScript, C, Java, C++ |
Pytest, Unity (C) |
Writing tests as a means to develop code. If the test fails, the code is wrong.
|
Show
|
| 4 |
8 |
Rust |
C++, C, Python |
Rust std, Catch, GoogleTest, nose, pytest |
A fair bit, we use it extensively at PA, I often find the hardest part of TDD is the first test
|
Show
|
| 4 |
12 |
c |
python
java
c++ |
ceedling
unity
pytest |
i learned the process in college. haven't applied it in my career at all. tests first...
|
Show
|
| 5 |
35 |
c |
C++, python, ruby, perl |
Internally developed and the Bluetooth qualification test suites |
Basics
|
Show
|
| 3.5 |
8 |
c |
python |
cpputest |
I believe development and testing goes hand in hand.
|
Show
|
| 3 |
10 |
c |
c++ |
cunit/gtest |
from what I have read on your blogs and few high level trainings attended
|
Show
|
| 1 |
5 |
c |
python, rust, java |
junit |
barely nothing
|
Show
|
| 4 |
46 |
c |
C++, Python |
Vermont Software, (defunt) Nothing modern |
It's a paradigm shift in order of operations to writing software. Test first, then code.
|
Show
|
| 4 |
6 |
c |
python,C# |
None |
I only know that test cases should be written first then code is written to fit those cases.
|
Show
|
| 11 |
25 |
c++ |
c, python, shell script |
google test |
Not much
|
Show
|
| 20 |
25 |
c++ |
c,python,perl |
gtest,cppunit |
I have some notions I did a trainning 15 years ago.
|
Show
|
| 10 months |
20+ |
c/c++ |
Rust, Python, C# |
Nunit, boost test, google test, catch |
I know about testing software but my TDD knowledge is limited. I understand the concept.
|
Show
|
| .6 |
5 |
embedded c |
c
c++
python
java
|
QTP |
TDD IS A USEFUL TOOL CAN BE USED FOR IMPROVING THE FUNCTIONALITY OF FIRMWARE
|
Show
|
| 25 |
58 |
javascript |
SQL, C ,Java |
none |
nothing
|
Show
|
| 1 |
5 |
python |
r, julia, c++ |
unittest, pytest, nose2 |
test driven development is where you write tests before writing the actual code
|
Show
|