| 3 |
7 |
Java |
JS/TS, PHP, C++, Python |
JUnit, Jest, Cypress |
Write test first, fail test, pass test
|
Show
|
| 5 |
5 |
C# |
C++
Python
C
Java
Visual Basics |
NUnit |
It helps our coding development cycle
|
Show
|
| <1 |
5 |
Python |
C#,C++ |
None |
I had heard of the concept before but never looked into it.
|
Show
|
| 1 |
4 |
Javascript |
Python,
Java |
Juint for javascript |
That you should try and do TDD before programming the function, not after
|
Show
|
| 6 |
11 |
C# |
C,C++ |
NUnit,GoogleTest |
Write tests based on behavior before writing implementation. Strong when requirements are known
|
Show
|
| 4 |
6 |
Java, React |
C/C++, Python |
JUnit, React Jest |
You code to pass the test
|
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
Not much.
|
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
Not much.
|
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
Not much.
|
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
Not much.
|
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
Not much.
|
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
Not much.
|
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
Not much.
|
Show
|
| 4 |
8 |
C# |
Only C# in my project |
NUNIT |
Not much.
|
Show
|
| 3 |
3 |
Java |
Javascript
C# |
JUnit |
It's good for making sure requirements are met.
|
Show
|
| 4 |
8 |
C# |
Java, SQL |
NUnit |
Basic understanding of the concepts
|
Show
|
| 5 |
9 |
C# |
Java |
NUnit |
It involves making the tests first and then writing the software to pass it.
|
Show
|
| 5 |
5 |
C# |
Java, C++, C, Python |
JUnit. PyTest, XUnit, Google Test |
It is a method of writing test cases against requirements first before fully developing code.
|
Show
|
| 2 |
5 |
C# |
Java, Python |
JUnit, Pytest |
Red Green Refactor approach
|
Show
|
| 19 |
10 |
C# |
C, C++, Java |
GoogleTest, NUnit, JUnit |
We use it every day in our work
|
Show
|
| 3 |
3 |
java |
typescript |
junit, jest |
It assures software meets requirements, shortens dev time,
|
Show
|
| 1 |
5 |
C |
Python, Javascript, dabbled in C#, C++, Rust |
None really, have used a simple test harness written by colleague, not strictly for unit tests |
It involves writing tests before writing code.
|
Show
|
| 1.5 |
8 |
C/C++ |
Python, Java |
Google Test |
Build tests to fail first, then write the function to pass the test.
|
Show
|
| 2 |
0 |
Matlab |
C, C++ |
N/A |
None
|
Show
|
| 1 |
33 |
C |
C#
WPF
C++
FreeRTOS, SafeRTOS and RTXC RTOS |
None |
just cursory knowledge from talking about it and a couple YouTube videos.
|
Show
|
| 0.25 |
0 |
N/A |
N/A |
N/A |
Heard the terminology and have seen what I feel is similar at a different company. happy to learn
|
Show
|
| 20 |
32 |
C |
MATLAB
Assembly (rarely!) |
Limited experience with CppUnit.
Some experience with Model-Based testing using Simulink tools. |
Develop automated tests based on specifications BEFORE developing code. Helps verify requirements.
|
Show
|
| 34 |
44 |
C |
none |
none |
Very little -- watched a training video, read a few articles.
|
Show
|
| 2 |
20 |
C++ |
VHDL
Typescript
Node.js
Python |
Junit |
I know some. I have written unit tests in the past but I havent done tdd, I have encouraged adoption
|
Show
|
| 0.75 |
4 |
Java |
Go, MATLAB,
Recently started C and C++ |
None |
It shortens feedback time, you catch more bugs sooner
|
Show
|
| 2 |
Off/On 15Y |
C |
C++
|
None |
The basics: you write a test, you fail the test, you write/update code until it passes the test.
|
Show
|
| 7 |
7 |
C |
Python |
Ceedling |
I understand the development cycle and its potential.
|
Show
|
| 0.4 |
6 |
C++ |
Python, Node.js, C, C#, Go, JavaScript, Typescript, Java |
Cypress, Selenium, GTest, Cpputest |
Not too much
|
Show
|
| 2 |
10 |
C |
C++
Python
JavaScript |
ceedling - not much experience though |
The basic philosophy, but not too much honestly.
|
Show
|
| 2 |
10 |
C |
C++
Python
JavaScript |
ceedling - not much experience though |
The basic philosophy, but not too much honestly.
|
Show
|
| 1 |
4 |
C |
python |
unity cppucheck google test |
it is about writing test before writing relevant functions
|
Show
|
| 2.5 |
8 inc uni |
C (embedded) |
Python (data)
Javascript (cloud) |
None. Mostly integration tests controlled using a CLI and not at all automated. |
A methodology which improves code reliability, maintainability and extensibility through testing.
|
Show
|
| 2 |
6 |
C |
C++, Python |
Googletest, Unity, VectorCAST |
Not much, haven't done TDD before.
|
Show
|
| 6 |
6 |
C |
C++, python |
None |
I read Test-Driven Development for Embedded C, but I couldn't use it on a daily basis.
|
Show
|
| 1 |
23 |
C++ |
C# |
gtest |
some basic online training.
|
Show
|
| 13 |
24 |
C |
x86 assembly |
Visual Sutdio, Windbg, protocol analyzers/jammers |
Just learning about this
|
Show
|
| 2 |
3 |
C |
C++, python |
I haven't done any unit tests. |
It's a good platform to develop necessary embedded skills for engineers.
|
Show
|
| 4 |
25 |
C, C++ |
Java, Assembly |
implement my own |
none
|
Show
|
| 3 |
5 |
C |
C++, Python |
pytest |
Unit-level testing by mocking a hardware behavior to validate all the possible use cases.
|
Show
|
| 3 |
20 |
C/C++ |
Java, C#, Python |
Google Test, CppUnit |
I have done TDD with C++ before
|
Show
|
| 2 |
5 |
C |
Python, C++, java |
We currently use googletest, but are likely going to switch to unity test. |
From what I understand, you write unit tests based on required functionality, and then code after.
|
Show
|
| 2 |
10 |
C++ |
Python |
Gtest, Gmock |
I know the high level concepts.
|
Show
|
| 0.5 |
4 |
C |
None |
None |
Not a lot.
|
Show
|
| 1 |
15 |
c |
c++ |
google test framework |
I just know first we need to write test cases before even to start with developing code.
|
Show
|
| 4 |
13 |
C |
C++, python, Java, C# |
None |
Avoiding getting bogged down writing tests when we don't even know what the legacy code is doing.
|
Show
|
| 1 |
26 |
C |
C++, Python |
CppUnit, QSpy, TSIM (for VxWorks) |
I worked on a project a couple of years ago which was truly TDD. I loved it.
|
Show
|
| 1 |
6 |
C++ |
Python, CUDA, C |
Catch2 |
Familiar with the concept, but haven't worked on a project that develops strictly by TDD.
|
Show
|
| 9 months |
21 years |
c/c++ |
angular |
Microsoft Unit testing framework |
Not much
|
Show
|
| 0.6 |
15 |
C |
Python |
Ceedling |
TDD starts with writing a failing test case and then creating just enough code to pass the test.
|
Show
|
| 1 |
15 |
C |
C++, Python |
N/A |
You need to have test in mind and start by thinking how you can test a piece of code before you star
|
Show
|
| 1 |
4 |
C/C++ |
Python |
CUnit framework |
That writing tests first demonstrates you know the expected/desired requirements of your code
|
Show
|
| 34 |
40 |
c |
.net |
none |
-
|
Show
|
| 4 |
17 |
C |
Python
C++ |
None |
Very little.
|
Show
|
| 20 |
30 |
C++ |
C, Java, Php |
Junit, Gtest |
I use it regularly
|
Show
|
| 34 |
25 |
C |
Python |
nothing |
nothing at the moment
|
Show
|
| 2 months |
10 years |
Embedded C |
I was using Python & VB.net in my previous job |
Nothing |
Its Test Driven Development where a unit test will be written along with the regular functional code
|
Show
|
| 3 |
10 |
C |
Assembler |
none |
It is a way to design code in order to increase testability and maintenance in the time
|
Show
|
| 1.5 |
5 |
C++ |
C, Python |
CppuTest |
Not much, but I've heard good things about it.
|
Show
|
| 1 |
5 |
C/C++ |
Python, Rust, Javascript. |
CppUTest, Python unittests. |
Write a test first, then develop for that test.
|
Show
|
| 18 |
20 |
C++ |
Python, Matlab |
Python Unittest |
|
Show
|
| 4 |
10 |
Python |
C, C++, Javascript, Matlab |
Python unit tests and teamcity CD/CI |
Only that you create tests before you code
|
Show
|
| 14 |
30 |
c# |
Long time ago: java, c, c++, fortran, lisp |
Resharper Unit testing
Testing tools in Visual Studio |
Did a stint some years ago. Not doing tdd anymore, but would love to do it again
|
Show
|
| 1.5 |
4 |
C# |
Currently just C# |
GitLab CI |
Create a test first. Build logic later. Continuous growth of complexity, refactoring and testing.
|
Show
|
| 1.5 |
5 |
It was Java |
Chora (Embedded Wizard), Python, C, a little Cpp |
GitLab CI |
just basic theory, I tried in the previous company for embedded stm32 boards but it didn't last long
|
Show
|
| 14 |
35 |
C/C++ |
Python, C#, PHP, Matlab, Javascript, Bash, Assembly |
Google Test |
You iterate writing tests first that capture the requirements, then the code that makes tests pass.
|
Show
|
| 1 |
25 |
C++ |
Python, C, Matlab |
-none- |
Read your book, informed myself through podcasts, internet. Big fan of it - that's the way to go!
|
Show
|
| 8.5 |
15 |
python, c |
java, c++ (little), shell scripting |
plain asserts inc, unittest (python), junit |
Shortly a methodology where you first write a test for you code and then the code itself
|
Show
|
| 1 |
12 |
c++ |
c, python, rust, bash |
Cpputest |
i've read the book, and worked in a test-driven environment for over a year
|
Show
|
| 1 |
10 |
C |
C++, Python |
static analysis |
It's an alternative to the waterfall design. It moves the key pint on the test side in someway.
|
Show
|
| 3 |
4 |
C |
Python |
Unity |
Read the book Test Driven Development for Embedded C
|
Show
|
| <1 |
5 |
C |
Python
Java
HDL |
N/A |
Just a cursory overview.
|
Show
|
| 5 |
5 |
c |
Python |
Not sure |
Nothing
|
Show
|
| 10 |
20 |
C |
C++, PHP |
Unity, PHPUnit |
In short: Develop to make your tests pass. Work in small steps. Run tests continuously.
|
Show
|
| 5+ |
few months |
C |
Python |
none |
not much.
|
Show
|
| 3 |
20+ |
C |
Bit of C++, C# and Python |
None |
Very little, some of my team use it and we discuss it, but I haven't actively used it
|
Show
|
| 9.7 |
42 |
C# |
C, C++, Java, Perl, PowerShell, bash, Javascript/Typescript |
NUnit, VisualStudio built-in stuff |
Code a test that fails, write the code it tests so that it passes, then refactor, move on.
|
Show
|
| 11 |
10 |
C# |
C, C++, Java, Matlab, LabView, VHDL/Verilog |
None |
Nothing
|
Show
|
| 12 |
20 |
C++ |
C Java C# |
None |
I understand the overall concept of writing tests first followed by the code to make them pass.
|
Show
|
| 14 |
3 |
Java |
Python, C++, C, Prolog, Scala |
Maven |
A software development methodology that puts functional expectations first through testing.
|
Show
|
| 1 |
8 |
Java |
c#, c++, python |
None |
It is a methodology to program more effectively and efficiently.
|
Show
|
| 1 |
4 |
Java |
C#, C/C++, Python |
none |
It makes testing less painful and tedious in the long run.
|
Show
|
| 1 |
20 |
C |
C++, C#, assembly |
Ceedling, NUnit |
Been using it for about 1 year. It is great to give confidence when something has changed or added.
|
Show
|
| 2 |
11 |
C |
Python |
Google Test |
not much.
|
Show
|
| 3 months |
8 |
C |
C++ |
Visual studio |
In TDD software requirements being converted to test cases before software is fully developed
|
Show
|
| 3 Months |
7 yerars |
C |
C++, Python |
Jenkins |
Software requirements being converted to test cases before software is fully developed.
|
Show
|
| 10 |
10 |
C And C++ |
Java,C# |
I have a Test application which calls specific function of interest. Also code coverage tools |
Nothing.
|
Show
|
| 2.5 |
3 |
c |
c++ |
- |
Nothing
|
Show
|
| 0 |
10 |
C |
Python |
None |
Nothing
|
Show
|
| 0 |
15 |
C |
C++,python |
Dont know |
Test cases are written before developing any features.
|
Show
|
| 15 |
16 |
C |
Python |
Automation |
Have basic knowledge about TDD.
|
Show
|
| 0 |
5 |
C |
C++, Python |
Jenkins automation testing |
TDD is test first development process where test case is first written before you write enough code
|
Show
|
| 1.7 |
8 |
C++ |
C, Python |
None |
Not sure about TDD
|
Show
|
| 0 |
14 |
C / C++ |
Python |
GMock |
It means:
1) understand the req
2) define a test
3) code
4) use #2 to confirm soln
|
Show
|
| 0 |
17 |
C |
C++, Python |
gtest |
I think TDD is a practice that software developers should follow to identify bugs at early stage.
|
Show
|
| 0.2 |
11 |
C |
C++ |
randomizing the UT and configuring jenkins to run it |
adding scope or hooks so that the feature can be tested independently
|
Show
|