Training Preparation -- Technical Background of 100 Attendees

Years with company Years programming Primary programming language Other programming languages Unit test harnesses Tdd knowledge
0 15 C/C++/C# C#, Python Google Test Unity NUnit Test-driven development. The tests drive the implementation. 1. Write a failing test 2. Add implementation 3. Re-test 4. Refactor 5. Retest 6. Continue cycle until "all" the tests are covered.
Show
18 25 C++ Python, Java, C#, APL, ... CppUTest, xunit variations for C/C++, Boost Test, etc. Many uses over the last 20 years. (simple level) Received training. Done training. Paired. Paired with Ward a number of times. Created a few simple test frameworks when one wasn't found. (Old Matlab, Basic) Made a variety of simple C/C++ frameworks.
Show
6 30 C/C++ Ada, Java, C#, VB, Python CUnit light tangential experience, want to learn a lot more about it!
Show
2 15 C C++ None I know that it relies to requirements as its pillars and testing against these requirements to consistently produce functional and purposeful code.
Show
5 ~10 C, C++ Ruby Python Rust Check - C CUnit - C CxxTest - C++ Boost::UnitTest - C++ Rust - built in to the language! Isn't just having your Python/Ruby script run without exception enough of a test? *Write tests before you write code. *Unit testing should be able to hit ~100% code coverage. *Tests should follow the setup, act, assert pattern. *Unit tests should never depend on test ordering. *Test feedback should be immediate and readable.
Show
5 4 C python unity cpputest attended EOC2021 workshop, currently reading James book, just finished a project test-driving it
Show
0 15 ASM C, C++ None Very little, this is the first job where I have encountered tdd.
Show
17 10 Java C/C++ None Not much
Show
0.5 4 C++ C#,C,Java,JS,Python,Perl Boost Test Framework in school I haven't heard of it, so just what I can gather from the name.
Show
18 21 C XML cmocka, Valgrind TDD, perhaps in a different form, we had many years ago. The idea was: you write the tests first and then develop. That didn't work.
Show
20 37 C awk, assembler, some more here and there ? I think I know what it is about
Show
20 40 C python cmocka The idea is quite obvious. It is not the only but maybe the best way to get meaningful unit test cases. I would rate this a helpful if code is under your control. It is difficult to apply if only minor changes are added to a suppliers code.
Show
20 40 C C#, CPP, Assembler Jenkins CI ?
Show
22 40 C/C++ VBScript, Powershell, Java, Perl. None It must be something between undriven and panic driven development.
Show
21 ~25 C/C++ python, shell if necessary: java, perl propriatery ones, sharness, python unitest it stands for "T_est D_riven D_evelopment" and if really done then it can help to make someone think before starting to code
Show
21 21 C - for GCf tests: R&S test equipment, for LwM2M: our LwM2m client on our device connected to our test server, dedicated tests are performed by out test team Nothing, this topic is new for me.
Show
0 10 Rust C, C++, Python Cargo, CMake (ctest), gtest, gmock I am familiar with the process of writing tests in advance and making incremental changes to avoid getting ahead of yourself. I only do it when I am trying to implement something that is non-trivial.
Show
Half Year 6 Python C, C++ Pytest Nothing officially, just a general understanding of the design methodology from some books. Basically that you structure your developed code around pre-written tests.
Show
4.5 15 C C++ utest, gtest i have started reading your book and we had discussions inside our company about it. but havent worked according to it so far.
Show
4.5 15 C C++ utest, gtest i have started reading your book and we had discussions inside our company about it. but havent worked according to it so far.
Show
2 5 C C++ and VHDL CppUtest Improve software maintenance and flexibility
Show
2 14 C C++ CppUTest, GTest the philosophy of writing first the test cases before the implementation and having the corresponding tests for the implementation which locks a module functional behaviour, making then easier to change without being afraid of introducing regressions
Show
0.5 3 C C++ Rust Python Javascript I don't think I've used one? I've written test *benches* with test vectors for SystemVerilog before, but that might not be the same. Write the test first, watch it fail (red), make it pass (green), and then improve it (refactor). Start from the simplest possible tests. Make it pass in the most direct way.
Show
1 40 f# c#; rust; fsunit; sunit; nunit; xunit; junit; cucumber jvm; cucumber ruby; cucumber rust; fitnesse with smalltalk fixtures I've been coaching whatever team I'm on in it the past decade, but I am still learning. Recently F# way -- and to an extent Rust -- lean on compiler: can my compiler be my unit test? Can I write code in such a way if it compiles it probably works?
Show
0 20 C/C++ Python, Rust, Assembly Catch, Rust unit tests think/write test before think/write code create a failing test first only implement enough code to pass the currently failing test
Show
2 20 C/C++ some python, little bit of lua and javascript. google test, cppunit, cmocka for each new "thing": write test first. then write code to pass all tests. cleanup.
Show
0 8 C Python, C++, C# Tessy, Parasoft, GTest, VS Native Unit Test The idea behind it is clear, but I have never used this approach before.
Show
16 20 C++ Python Infrequent: java, c#, ruby, javascript, ... Many including CppUTest googletest, boost, assert, unittest.py junit, nUnit, custom, ... I've studied and practice TDD. I use it on my projects. I use it on client projects when possible. It's common that I'll demo some examples in a code base but that the teams will not take it and run. Reasons cited include: no time, too hard, fragile.
Show
0 0 python shell script 0 My understanding is that first we need to write the testcases based on the feature requirements and then in order to pass that testcase we need to write the code.
Show
5 5 C++ C Sharp, Python, Java Karma, Jasmine I know it can save time in the long run
Show
6 9 C# C++, Javascript na Nothing
Show
1 30 years C Sharp None NUnit TypeMock / NMock Read all the books, know the principles and how to do it in C#, Scrum teams Know it needs a mind set change to realize it correctly. Know it is not about writing tests in parallel to coding :-)
Show
8 30 C - C++ - C# - Visual Studio Unit Test - Googletest Some internet researches about the basics. Test case first followed by implementing the functionality
Show
0 8 C Python, C++, C# Tessy, Parasoft The idea behind it is clear, but I have never used this approach before.
Show
2 1 1/2 Python LabVIEW, C++ PyTest, UnitTest Off the top of my head, I understand it to be the practice of consistently testing every other line of code you write assuming everything is a modular piece.
Show
30 10 c/c++ Java, Swift, Ada, SQL none This is my first instruction in Test-Driven Development
Show
2 7 C C++ only for unit testing Google Test Not so much, so it makes sense to attend this training class.
Show
4 6 C Java JUnit CppUTest GoogleTest There was once a motivation in the team to switch so i bought actually your book and tried it out in small examples. But it never made it "fully" to the project. What i tried to keep for me is to think first about what i really want before coding.
Show
1/2 3 C C++, Python No unit test harness used in the past. Rudimental steps with CPPUTEST done. That it is a really different approach of development, where you have to get used to it. It is one of our best shots to create maintainable software
Show
8-ish 40-ish C++ these days C, Java (and long time ago, Lisp) CppUTest My understanding is it's based on tight time loops between developing code and the associated unit tests. I'm a big fan of design-by-contract (interfaces first), so I'd like to get a better understanding of how these ideas relate.
Show
2 20 C Python pytest I used it in Python, but not as deeply as it is explained it your book. But I love the concept.
Show
21 2 LabVIEW, Python C++,Rust python-bdd, pytest, unittest basic principle that we need to write code that incrementally passes test units and will in the end be itself considered the documentation and verification tasks fulfilled.
Show
3.5 14 C# C, Bash Script, Python None I know the principles.
Show
9 30 C C# C++ bash script Matlab - Not so much. I know that the idea is to write tests before writing the code.
Show
5 8 C# C, Python, Javascript, Powershell Unit Tests using MSTest Framework Basic concepts
Show
15 20 c vb manual scripting fully feedback cycle to speed up development and testing software without actual hardware
Show
6 20 C# C, Java, Python, Shell Ceedling (CUnit), NUnit, JUnit, Google test I know that Kent Beck wrote a TDD framework for Smalltalk in the mid-90s. The practice makes sense and gives me (and the business) more confidence that something will work, and shortens the time to resolve what bugs do crop up.
Show
21 19 C/C++ C#, VB None Not much
Show
14 17 c c++, matlab unity, googletest i use it
Show
14 17 c c++, matlab unity, googletest i use it
Show
8 13 VHDL C, C# Non Not very much: Before coding you define tests the function later must pass. These tests are automated.
Show
6 20 C++ Bash C C# GML Java Matlab Custom frameworks I know about the basic cycle of test-code-refactor. I have tried to practice this where possible, however, we currently have a lot of legacy code that cannot easily be unit tested. I am trying to refactor this code so that it can be unit tested.
Show
6 6 C Python None Nothing
Show
4 4 C++ C, matlab, python, C# matlab, simulink, xUnit I am familiar with it using the matlab/simink framework, have put together a few tests once when writting a desktop C# program and I have maintained a few unit tests.
Show
3 4 C Python Very limited use of google-test Nothing except what has been introduced following up to this course.
Show
0 3 C C++, Python, Matlab GoogleTest, BoostTest Just the basic principles, write the test before the actual code.
Show
1 4 C None None Not much
Show
0 10 C JAVA, C++, python none No Idea
Show
0-1 4 Pyhton C, Matlab Pytest I do not have much experience with TDD.
Show
1 20 c python, c++ ? Nothing
Show
1 16 C# C++,C,JavaScript,Python,SQl MSTest, Google Test, MoQ (mocking framework in C#) A lot, I think. I followed an extensive course 10 years ago. I have worked with pure TDD driven development/scrum and gated checkin for years. Within my current department, in C/C++ TDD is currently improbable by merit of lacking design.
Show
7 15-20 C C++, Assembly, Python, bat-script google test framework Some minor experience with google-test, but not used it actively. perhaps some minor experience during education.
Show
0,5 2,5 C Python - Not very much
Show
2 20 C Labview None
Show
8 8 c assembly none Basic knowledge.
Show
6 15 C Python None That we should consider using it.
Show
0.75 30 Rust C, Python, C++ cargo test It is a SW dev. methodology that emphasises writing test early, and having complete (unit) test coverage.
Show
2 6 C C++, Python Cpputest, Unity/Ceedling Did TDD actively in my previous job
Show
1 10 C Matlab Simulink C++ Python Matlab Simulink Test utest.h (C) Catch2 (C/Cpp) tdd = write test before code.
Show
1 20 C C++ Python GoogleTest, Robot Framework Not enough I am afraid of.
Show
1 27 C Python and C++ (looking at Rust) Google test and pytest. (Looked at Catch2) It's a process where you develop tests before code in an iterative manner.
Show
0 13 C++ C, RUST, ASM Gtest, Gmock, munit (unit with a greek mu) I've watched (and read) some Uncle Bob (Robert Martin), and his red-green-refactor method. I also followed strict TDD methodologies at my previous company.
Show
9 months 15 C C++, C#, Python, ASM, Ladder, SFC, FBD, ST, IL. GTest I've read your book.
Show
2 5 C Python C++ None You start by defining the interface, write test that test that the output is correct, then write the actual code.
Show
3 6 C only C Use C++ only as needed , so not very much NA no
Show
1 8 C++, C python, Java cmocka, gtests suite develop testcase first and expect it to fail, then build SW to make the testcase pass.
Show
5 20 C/C++ Python, ARM assembly . .
Show
5 26 C++ C, Assembly None It improves code quality and reduce development time.
Show
7 20 C++ None recently, Java, python. None recently, can't remember. Not much
Show
4 10 C++ Python Bash C None not much
Show
5 10 C++ C, Python, Assembly Proprietary solution, Isolator++ It emphasizes converting requirements to tests first and using the tests to evaluate software quality/completeness instead of coding first, then writing tests later
Show
1 16 C C++, Python Only loosely explored python unittest, C unity I like the idea in general of heavy unit testing, but have not been exposed to it much in practice, outside a few smaller self-driven projects.
Show
0 25 C/C++ C++, python, perl, bash cpputest, Unity some.
Show
6 8 C++ Python N/A N/A
Show
10 16 c C++ I would say not really used any recently Very new to it for embedded system, have done CPP-Unit at start of career but not too much. I used to write dummy test functions using cpp-unit to test my code ( module, function level)
Show
2+ 5 C/C++ python cGreen that we write tests first and then write code so that we know if code is in compliance
Show
23 35 C C++, C#, Assembler, Python Self written, cmocka From my understanding: Define an API, create a dummy and test code for that and the next step is to realize the real functionality.
Show
6 10 c used cpp and java earlier, currently limited to c python based Nothing much.
Show
21 21 c language bash, python (few), c++ (few) Sw Department wide: Jenkins, Bash Scripting, Artifactory for storing logs, firmware versions, crash dumps. I have only partially experience with Jenkins. Nothing in detail.
Show
23 30 C currently none. Over the years ... project dependent. ASM/C/C++/Java/Pascal cmocka --
Show
20 20 C Python Jenkins CI server not so much. Each coding step has to be verified with a testcase?
Show
20 20 C C++ Java, Perl Jenkins cMoka
Show
20 25 C C++,Java,Python,Perl Jenkins, Android CTS Partially already used in our company
Show
many even more C ASM, C++, CMM (JTAG debugger control scripts), Script Languages for Win Command/Power Shell and Linux Shells (Bash), Python, Perl Jenkins CMoka Start with describing testable functionality. Define Test Cases by splitting down functions as far as it makes sense from the point of view of the user/customer. Having defined Test Cases start thinking about software design and implementation.
Show
20 37 C Perl, C++, Clojure, Racket, Java cmocka I bought your book some years ago ;-)
Show
0 33 Powerpoint :) C++/C/C#/Java if I have to/ruby/python/etc CppUnit, JUnit, Nunit, Xunit, all the little units A thing or two. We may have learned it about the same time...
Show
18 30 c/c++ not much else ? have some ideas - but i am probably wrong
Show
10 0 python na na nothing
Show
23 28+ C++ C, C#(Dâ™­), Objective C, Pawn None nothing
Show
4 12 C# Java, Structured text, Ladder Logic NUnit Very little: Code well-defined pieces of code and test them right away. When they passe testing it can be re-used/called by other function/modules without re-test.
Show
Tag cloud words for other programming languages