| 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
|
| 4 |
14 |
C |
c++, python, Go |
Gtest |
better practice
|
Show
|
| 4 |
14 |
C |
c++, python, Go |
Gtest |
better practice
|
Show
|
| 30 |
5 |
C |
Python |
none |
Not much
|
Show
|
| 1 |
3 |
C |
Python |
Pytest |
Not much
|
Show
|
| 4 |
19 |
C |
C,C++ |
GTEST |
NULL
|
Show
|
| 4 |
10 |
C |
C++, Java, PL/X, HLASM |
Jenkins test harness |
that is stands for Test Driven Development!
|
Show
|
| 3.5 |
7 |
C |
Python, C++ |
gtest |
Writing tests before developing to gain confidence that changes truly work.
|
Show
|
| 2 |
2 |
C |
Python |
Unity |
Minimal as I am early in my SW career.
|
Show
|
| 3 |
3 |
C |
C# |
Unity |
n/a
|
Show
|
| <1 |
5 |
C |
C++, Python |
I worked on module-level testing, writing unit tests for individual components in isolation. |
TDD means writing test cases before development to guide and verify the code
|
Show
|
| 7 |
35 |
C |
Python |
Robot Framework |
Very little
|
Show
|
| 5 |
10 |
C |
JS |
custom Unit Test framework developed in the company.
Automation framework
IAR
|
Have had an introduction to TDD basics. have not practiced it extensive.ly
|
Show
|
| 7 |
10 |
C |
Python
Javascript
Go
|
internal
jest |
I have done some sessions with our manager Phil and have enjoyed it
|
Show
|
| 4 |
4 |
C |
Python |
Custom in-house harness for embedded C |
I don't know much except it's a type of development where we write tests first.
|
Show
|
| 1 |
10 |
C |
Python
Java Script |
n/a |
It's a strategy for development by first defining the test cases necessary for successful design.
|
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
|
| <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
|
| 6 |
19 |
C++ |
C, Python |
gtest/gmock |
Used in previous job fir 2 years
|
Show
|
| .4 |
5 |
C++ |
C
Java
Python |
CTest
GTest
JUnit |
Write tests describing intended behaviors and failures first, then craft solution
|
Show
|
| 18 |
24 |
C++ |
C,python,Java |
JUnit |
Use fakes/stubs to reduce/remove dependencies and speed up test and iteration cycles.
|
Show
|
| 1 |
7 |
C++ |
Python, C, Rust, Go, SML |
Pytest |
I have touched on TDD in school.
|
Show
|
| 1.5 |
27 |
C++ |
C, Python, Java, *nix Shell |
Python built-in |
It's a great idea. "Thank you, Zebra!" for prioritizing it enough to sponsor.
|
Show
|
| 3 |
3 |
C++ |
C#
Python |
I have not really used any test harnesses. I have seen some CppUTest and done manual testing. |
Write a test first, then develop a piece of code that passes that test.
|
Show
|
| 0 |
25 |
C++ |
Python
C |
Some experience of Google Test, but very limited |
I am aware of the concepts having Googled it, but have no experience of it all.
|
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
|
| 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
|
| 4 |
9 |
C, C++ |
python, rust(just started) |
vectorcast, internally developed test suites |
Write the tests first, then write the code for that test.
|
Show
|
| 1 |
11 |
C, Python |
C++, Bash |
CppUtest |
You develop tests before writing code and then write your application code after.
|
Show
|
| 2 |
7 |
C/C++ |
Python, Java, Some Javascript and its framework |
CPPUTEST |
my architects told me to use it
|
Show
|
| 0 |
4 |
C/C++ |
Python |
JUnit, Pytest |
we create standards that can be tested then write the code to meet them
|
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
|
| 14 months |
20 years |
Embedded C |
- python
- java script |
- unity |
writing the test code iteratively with the production code until we can't think of a test to write.
|
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
|
| 1 |
3 |
Java |
Javascript
Python
C# |
NA |
reassurance that my code is still working with new features
|
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
|
| 20 |
30 |
Python |
Java, C/C++, PLX |
PyUnit, JUnit |
Officially not much, but I've been pushing developers to write tests.
|
Show
|
| 4 |
10 |
Python |
C++ |
None |
None
|
Show
|
| 0.5 |
10 |
Python |
C, C++, C#, Java, Scala, x86 Assembly, RISCV Assembly, Go, Dart, Javascript, Ocaml |
CUnit, JUnit, pytest, scalatest |
Only by name, test driven development.
|
Show
|
| 0.5 |
10 off&on |
Python |
Embedded C (it's been a while) |
Pytest |
You write tests for expected outcomes, then write/adjust the function until the test passes.
|
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
|
| 2 |
11 |
Rust |
C++, Python |
Catch2, Rust |
Doing it daily for six months, nobody has explained it to me with words yet.
|
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
|
| 6 |
8 |
c |
JavaScript |
Only used in-house tools - behavior driven testing and code coverage |
It's a development strategy where tests are written before code.
|
Show
|
| 4 |
8 |
c |
Javascript, Python, C++ |
Custom |
Testing, requirements written before development starts to ensure implementation follows design
|
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
|
| 1 |
20 |
c++ |
python
java
rust
|
catch
gtest
pytest
jtest |
Ideally, write tests before the code.
|
Show
|
| 11 |
25 |
c++ |
c, python, shell script |
google test |
Not much
|
Show
|
| 1 |
12 |
now C |
I mostly used ST (CODESYS)
I mostly learned C++ in my studies |
none |
write test first
make test fail
write code only to pass the test
clean up code
|
Show
|
| 30 |
30 |
pls |
rex |
unsure |
Heard about it in years past
|
Show
|
| 0 |
4 |
python |
c++ |
test, cmake |
from what I can see, it seems like you should have test cases before you even write code
|
Show
|
| 0.8 |
1 |
python |
SQL, RUST |
none |
feels tedious as a concept but makes things easier in the long run.
|
Show
|
| 1 |
5 |
python |
r, julia, c++ |
unittest, pytest, nose2 |
test driven development is where you write tests before writing the actual code
|
Show
|