| 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
|
| 2 |
45 |
C |
Python, C++, Rust, Bash, ... |
Python unittest, Catch, in-house |
Once did a 2-hour TDD course: inspirational, but I desire additional teaching.
|
Show
|
| 10 |
20 partial |
C |
C# |
None |
Only got an introduction to it, but sounds interesting
|
Show
|
| 18 |
18 |
C |
C++, C#, Ladder Logic, Structure Language, Motion Perfect, VB |
CMOK, CUNIT |
I know the principles and apply some of them
|
Show
|
| 2 |
40 |
C |
C++, Java, ... |
No much Unit testing Experience. Years ago I got some Junit during period working in Java |
Very little, I think. I never had my brain set for the TDD. I normally focus on design.
|
Show
|
| 0.3 |
9 |
C |
C++, Python, Javascript, Java |
Unity, Ceedling, GTest, Jest, JUnit |
I've read Beck's book, but haven't applied it to anything beyond university assignments
|
Show
|
| 5 |
<1 |
C |
none |
don't know / n/a |
nothing
|
Show
|
| 7 |
1ish |
C |
Python |
UNK |
I create a test function with known output, if I can, that I can compare my program to.
|
Show
|
| 2.8 |
8 |
C |
C++, Python, VHDL |
Homemade |
Write tests before writing a function.
|
Show
|
| 7 |
5 |
C |
C#
VB
LabVIEW
Python |
Catch2
gMock |
write tests first before writing code
|
Show
|
| 8 |
35 |
C |
Python |
Roll-your-own |
Nothing really
|
Show
|
| 5 |
20 |
C |
C++, Python, VHDL, Verilog, System Verilog |
Cppunit |
Very little, just that it can help prevent regression issues using a design for test philosophy.
|
Show
|
| 2 |
5 |
C |
python |
none |
Nothing
|
Show
|
| 3 |
5 |
C |
Python |
Unsure |
Almost nothing
|
Show
|
| 4 |
15 |
C |
Python, JavaScript |
Unity |
I have read James' book and other resources about XP and SOLID programming (especially w/ Uncle Bob)
|
Show
|
| 2 |
2 |
C |
C# |
NUnit/JUnit
Ceedling/Unity/CMock |
I have heard about TDD a few times, also had a course in software testing while studying.
|
Show
|
| 9 |
20 |
C |
I've been really focused on C for the last longest time. |
Unity |
I've had a little experience with it.
|
Show
|
| .5 |
2 |
C |
python |
cunit |
only the basic concept behind unit tests, ive never written any.
|
Show
|
| 2 |
10 |
C |
C#, C++ |
Unity |
It is used to create more bug-free code by first designing the test methods.
|
Show
|
| 3 |
8 |
C |
Python |
None. |
I understand the concept and tried to implement something.
|
Show
|
| 3months |
10 |
C |
C++, python, bash, c# |
GTest, NUnit, CUnit |
Writing tests before beginning development
|
Show
|
| 6 |
15 |
C |
Python |
Ceedling |
Few concepts (having used ceedling)
|
Show
|
| 3 |
4.5 |
C or C++. It varies. |
Assembly(device specific), Python, C#, JavaScript, TypeScript, Markdown, LaTeX |
Ceedling and GoogleTest |
It's a method of writing software to be easily tested & write tests, to reduce time spent debugging.
|
Show
|
| 6 |
21 |
C# |
Python, Java, JavaScript, C++, C (although very rusty in C++ and C) |
MSTest, NUnit, JUnit, Selenium |
I know the principles but struggle with the application on a macro scale
|
Show
|
| 1 |
8 |
C# |
C, C++, VB, HDLs |
Visual Studio Unit Test projects |
Using testing throughout the software life cycle to save time and sanity when developing.
|
Show
|
| 8 |
20 |
C# |
C, C++, Python, VHDL |
None |
I understand it in the abstract, but have never applied it.
|
Show
|
| 3 |
3 |
C# |
C, C++ |
None. |
Not much, just that it has a large focus on test development earlier on.
|
Show
|
| 11 |
28 |
C# |
C++(Arduino)
|
Never used one. |
Just the very little of your book I've read so far. It sounds very interesting.
|
Show
|
| 3 |
6 |
C++ |
Python, Java, C#, qml |
CppUTest |
You write a test and then code to make the test pass
|
Show
|
| 2 |
40 |
C++ |
Python, Go, C, Java, C# |
Various, mostly home grown |
Just the basic principle
|
Show
|
| 2 |
20 |
C++ |
Python, C, Rust |
Catch2 |
the main stuff: write failing test, make it pass in the simplest way, refactor
|
Show
|
| 6 |
10 |
C++ |
C, Python, Rust |
Catch2, pytest, nosetest |
Test driven development drives the writing of code through tests. Red, green, refactor. An art form
|
Show
|
| 3 |
10 |
C++ |
C
Python
Rust |
Catch2
cpputest
Pytest
Cargo test
Cucumber |
functionality/interfaces are first defined in the tests, code is then written to pass tests
|
Show
|
| 3 |
15 |
C++ |
C, Python, others |
googletest |
start with writing tests that fail. then code till tests pass.
|
Show
|
| 2 |
40 |
C++ |
C, Rust |
Boost.Test
Ceedling
Rust's inbuilt test harness (cargo test) |
Its use is controversial and subjective. Tends to polarise developers.
|
Show
|
| 0.1 |
30+ |
C++ |
C, Python, PHP, shell, assembly, Java, Javascript, Objective-C, ... |
CppUTest, XCTest, JUnit, Selenium, ... |
Step 1: Create tests to enforce spec requirements.
Step 2: Code to pass tests.
|
Show
|
| 1 |
30+ |
C++ |
C, C++, Python, JavaScript, Java, Php, HTML, CSS, MySql, assembler, etc. |
roll my own |
necessary step
|
Show
|
| 4 months |
14 years |
C++ |
Rust, Python |
Google Test, CppUTest, Rust built in. |
The goal is develop tests first and then write the functions later to verify they do what you need
|
Show
|
| 5 |
10 |
C++ |
C
Java
Python
Bash
|
None |
Not much, but seems a bit backward and risks missing reqs for the sake of making it testable.
|
Show
|
| 11 |
30 |
C++ |
C
C# |
CppUTest
GoogleTest |
Write a test for new use case, compile w/ coded interface (fails). Then implement to pass test.
|
Show
|
| 14 |
14 |
C++ |
C#, python, matlab |
Did not understand the question |
Often it is best to start by implementing a test case rather than start by implementing the feature
|
Show
|
| 5 |
9 |
C++ |
Python, C and C# |
Google test, python unittest |
Concept? Creating tests before coding features.
|
Show
|
| 4 |
4 |
C++ |
Python |
none |
In practice, not much. The idea is very intriguing.
|
Show
|
| 12 |
20 |
C++ |
C, Python, Matlab |
Catch, MStest |
I know the principles quite well.
|
Show
|
| 5 |
8 |
C++ |
C |
google test |
nothing
|
Show
|
| 1.5 |
5 |
C++ |
Python, JavaScript, C# |
Stubs, mocks |
Idea is to write tests first and then the actual implementation should pass the tests.
|
Show
|
| 2 |
25 |
C++ |
C, C#, python |
googletest |
The idea has been presented or demonstrated few times over the years but I have never used it
|
Show
|
| 6 |
10 |
C++ |
Python, C#, C |
Google Test framework |
Creating tests for a feature before writing the code that implements it.
|
Show
|
| 5 |
5 |
C++ |
Python |
|
Read the book
|
Show
|
| 3 |
8 |
C++ |
C, C#, Python |
GoogleTest, CppUTest |
That it is a software development technique with the goal of making code easier to test.
|
Show
|
| 6 |
20 |
C++ |
C, python, Java |
cpp unit, gtest/gmock |
Writing test firsts based off requirements and executing continuous test runs while developing code
|
Show
|
| 1.75 |
7 |
C++ |
C
Python
JS/Css/HTML
Rust
|
Gtest |
It's a way to layout behavior before coding functionality
|
Show
|
| 4 |
10 |
C++ |
Java, Python |
GTest |
It's a way to ensure software is doing what's specified by requirements, unbiased by implementation.
|
Show
|
| 4.5 |
12 |
C++ |
C
Python |
googletest
cpputest |
test if software outputs the expected result with certain input
|
Show
|
| 1.5 |
7 |
C++ |
Python
Bash
JavaScript |
GTest |
Design tests(establish functionality needs) first then write the code.
|
Show
|
| 7 |
30 |
C++ |
Python, Rust, C, Bash |
GTest |
Write the test first, then make the test pass by implementing software.
|
Show
|
| 1 |
6 |
C++ |
Python, C#, Javascript, Rust, Solidity |
not sure |
It seems it is about writing unit tests before the actual functionality.
|
Show
|
| 8 |
25 |
C, C# |
C++, Python, bash, Perl, VB |
Those in Visual Studio, but just a little bit. |
I have good theoretical understanding, but I have not used it much.
|
Show
|
| 25 |
20 |
C, C# |
JAVA, Python |
JUnit |
Tried once.
|
Show
|
| 0 |
11 |
C, C++, Python |
Flutter |
Unity, pytest, inhouse tools |
The basic structure, but I've never gotten it to stick.
|
Show
|
| 2 |
5 |
C, Java |
C++ |
Cmock, Cpputest |
Test-first emphasis to eliminate regressions & guarantee behaviour for a set of (specific) reqremnts
|
Show
|
| 1 |
5 |
C/C++ |
Python, bash |
CppUTest, ZTest, BATS. |
Write the tests before your code and you'll catch a lot of mistakes that would have slipped by.
|
Show
|
| 2 |
9 |
C/C++ |
Python, SQL, Bash, C# |
None |
unfamiliar
|
Show
|
| 7 |
15 |
C/C++ |
Python |
gtest/gmock, pytest |
Start by defining the test body how something is expected to work
|
Show
|
| 5 |
12 |
C/C++ |
Python rarely |
Gtest |
Design test first, then write code to make the test pass.
|
Show
|
| 2 |
8 |
C/C++ |
Python, Java |
Gtest |
Not much
|
Show
|
| 1.5 |
35 |
C/C++ |
C++ |
GTest |
not much
|
Show
|
| <1 |
15+ |
C/C++ |
C# and some python, but not really. I Know enough to get in trouble. |
None, experimented with Unity and CppUTest due to TDDEC Book |
Failing tests come first, the test is the first client, test doubles help w/absent dependencies
|
Show
|
| < 1 |
5 |
C/C++ |
Python, JavaScript |
CppUTest, Unity |
I've read James Grenning's TDD book a couple times and have tried implementing it once or twice.
|
Show
|
| 1 |
30 |
Embedded C |
C++ |
none |
Don't know yet, still learning
|
Show
|
| 2.6 |
16 |
Embedded C/C++ |
All sorts of programming languages e.g. java, python |
google unit test |
You write test first and then code later
|
Show
|
| 3.5 |
3 |
Java |
C++, Bash, Python, |
Java |
I hadn't heard of it until I came across your course.
|
Show
|
| 2 |
1 |
Java, C# |
Python, XML, HTML, JS, SQL |
0 |
It's a programmatic way of shifting testing to the left. White-box testing.
|
Show
|
| 3 |
15 |
Python |
JS/TS
SQL
C#
|
Pytest
Unittest
Robot Framework
React Testing Library |
Write unit tests first, then code to satisfy those tests.
|
Show
|
| <1 |
2 |
Python |
C++
Javascript |
unittest |
It's difficult at first but rewarding at the end
|
Show
|
| 4 |
10 |
Python |
C++ |
Catch2
pytest |
Write the test first then the functioanlity.
|
Show
|
| 2 |
6 |
Python |
C++, Rust, Bash |
Pytest, Unittest, Catch, Cargo |
It should be used to guide the design of the code from the perspective of the user of the function.
|
Show
|
| 4 |
8 |
Python |
C/C++, HTML, JS, CSS, MATLAB |
Not a familiar concept to me |
Very little, I'll try to come in with as open a mind as possible!
|
Show
|
| 5 |
3 |
Python |
C, VB.net, labview |
none |
Write tests before you ever write a line of code. Then you write code to pass those tests.
|
Show
|
| 7 |
45 |
QML |
c++, python, bash |
Google, others but I forget as it's been a while |
not much. Sounds like a good buzz phrase.
|
Show
|
| 1 |
6 |
Ruby |
C, Kotlin, Python |
Unity, CppUTest
Espresso
Rspec, Nose |
I'm all about it
|
Show
|
| 3 |
5 |
VHDL |
Verilog, C, C++, C#, VB |
None |
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
|
| 20 |
25 |
c |
c++ rust |
ceedling catch |
write tests before changing code
change just enough to make the test pass
|
Show
|
| 2 |
10 |
c |
C++ |
TDD |
know a little
|
Show
|
| 1 |
9 |
c |
python |
unity
Cunit |
start with the test design then develop the application to satisfy the test cases
|
Show
|
| 3 |
5 |
c++ |
c, python, matlab |
None |
No much - excited to learn!
|
Show
|
| 3 |
3 |
c++ |
python, c, java, c# |
GoogleTest and CppUTest |
Not much other than we're hoping that it expedites our unit testing efforts
|
Show
|
| 2 |
10 |
c++ |
c, python |
gtest |
only some theory
|
Show
|
| 4 |
4 |
cpp |
python |
google test |
You should do it more.
|
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
|
| 16 |
0 |
n/a |
I'm a quality engineer wanting to gain better understanding of software testing. |
n/a |
nothing
|
Show
|
| 21 |
21 |
python |
IEC-61131 (ladder / structured text), Labview, TestStand, C, C++, C#, Matlab |
pytest, Unity |
I have been reading your book as well as done exercises from throwtheswitch.org
|
Show
|
| 2 |
5 |
python |
C |
Unittest |
red-green-refactor
|
Show
|
| 2 |
6 |
python |
java |
mypy |
Building a test first, that fails, then writing code to fulfil the test
|
Show
|
| 1 |
1 |
python |
Java, Javascript, C++ |
none |
The opposite of how I test my code
|
Show
|