| Unit tests, some integration tests, end-to-end |
Secure website. React front-end, Java Spring back-end |
VsCode, Intellij |
Pair programming for real-time review, 1 or 2 person review before merge |
31-60 seconds |
50 |
40 |
10 |
Show
|
| Test Classes |
Windows |
Visual Studios Code |
Our code is goes through a review process through our coding architect |
31-60 seconds |
20% |
20% |
60% |
Show
|
| Basic functionality tests |
Embedded System written mostly in C++ and ADA |
Visual Studio, Windriver Workbench |
Only done for merges into development. Review by at least 1 other person. |
30-60 minutes |
20% |
60% |
20% |
Show
|
| By making test to ensure coverage |
To have full coverage with little to no vulnerabilities |
VSCode |
We usually bring in another team member to examine the work as we explain why we implemented it. |
1-5 minutes |
6 |
2 |
2 |
Show
|
| NUnit,GoogleTest,Manual |
Embedded C++, Desktop C# |
VSCode |
Done via Gitlab Merge Requests. Sometimes async via the website. Sometimes sync over Teams |
5-30 minutes |
50 |
25 |
25 |
Show
|
| I run the Java tests on VSCode and I use "npm test" command to run the React tests |
AWS Linux |
VSCode |
We review code every two weeks |
Under 10 seconds |
60 |
20 |
20 |
Show
|
| Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
All code is reviewed by our lead before getting merged in |
1-5 minutes |
25 |
25 |
50 |
Show
|
| Write unit tests to test for correct method and class functionality |
Not sure |
VSCode and Visual Studio 2019 |
All code is reviewed by our lead before getting merged in |
1-5 minutes |
25 |
25 |
50 |
Show
|
| Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
All code is reviewed by our lead before getting merged in |
1-5 minutes |
25 |
25 |
50 |
Show
|
| Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
All code is reviewed by our lead before getting merged in |
1-5 minutes |
25 |
25 |
50 |
Show
|
| Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
All code is reviewed by our lead before getting merged in |
1-5 minutes |
25 |
25 |
50 |
Show
|
| Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
All code is reviewed by our lead before getting merged in |
1-5 minutes |
25 |
25 |
50 |
Show
|
| Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
All code is reviewed by our lead before getting merged in |
1-5 minutes |
25 |
25 |
50 |
Show
|
| Write unit tests to test for correct method functionality |
Not sure |
VSCode and Visual Studio 2019 |
All code is reviewed by our lead before getting merged in |
1-5 minutes |
25 |
25 |
50 |
Show
|
| I use TDD. |
Currently using Java |
VS Code, Git |
My code reviews look for any errors in the way the code was written. |
5-30 minutes |
50 |
20 |
30 |
Show
|
| NUnit |
Windows |
VSCode, Visual Studios |
Lead reviews our code |
31-60 seconds |
70 |
15 |
15 |
Show
|
| NUnit |
Windows |
Visual Studio, VS Code, Gitlab |
A reviewer review our code and provides feedback. I update my code resubmit for another review. |
11-30 seconds |
50 |
25 |
25 |
Show
|
| Most recent projects have been completed with Python. Current technique is to describe a class and methods, it's inputs and outputs. Write unit tests for it then write the code blocks. Adjust testing if new methods or functionality are added. |
For our C++ code the target system will be an embedded system. |
VS Code (primarily), Visual Studio, TI Code Composer. |
Currently code review is done by person marked as approver of the open pull request. |
31-60 seconds |
30 |
55 |
15 |
Show
|
| N/A |
N/A |
VS Code |
Pair Programming |
1-5 minutes |
4 |
2 |
4 |
Show
|
| NUnit |
Windows and Embedded System |
Visual Studios and Visual Studios Code |
We push onto GitLab and have our main architect review it. |
31-60 seconds |
50 |
40 |
10 |
Show
|
| unit and e2e tests using jest and junit |
Linux and Window OSs. |
bitbucket, jenkins, AWS, SCA tools |
Conducted at the end of each sprint, any needed changes made and approve before story marked done. |
1-5 minutes |
60% |
20% |
20% |
Show
|
| Running the code on hardware (or a dev board if no hardware) and observing the behaviour. If I encounter a problem as the device runs I will single out a function or functions and maybe write some code to explicitly test them. Very much test-after. |
STM32 micros, typically for IoT style devices. |
STM32CubeIDE, Git. |
We have a rough procedure for performing code reviews but it isn't really done. |
31-60 seconds |
49 |
2 |
49 |
Show
|
| Bench testing on hardware. |
STM32F205 processor with attached ADCs, EEPROMs, etc communicated with via SPI. |
VSCode, STM32CubeIDE, JLink, Git |
Also loose code reviews on merge requests. |
11-30 seconds |
70 |
10 |
20 |
Show
|
| N/A |
N/A |
N/A |
N/A |
31-60 seconds |
60% |
10% |
30% |
Show
|
| Application testing and bench top testing. |
Multiple boards with STM32H745 |
STM32CudeIDE and VisualGDB |
In the past there were in frequent the aim forward is to have code review before pull request. |
31-60 seconds |
40 |
30 |
30 |
Show
|
| N/A |
N/A |
N/A |
N/A |
1 day or more |
0 |
0 |
0 |
Show
|
| Manually running test cases. |
Most recently, ARM core micro-controllers (M4) in a Body Control Module (BCM.) |
Eclipse, target-specific tools (MANY are Eclipse-based), Visual Studio Code, MathWorks tool chain |
Manual inspection of individual code components against design and prior version, static analysis. |
5-30 minutes |
50% |
35% |
15% |
Show
|
| Mostly run-time testing by developer, using real hardware and IDE breakpoints, watch windows, etc. Subsequent end-user type testing in our labs before official release. |
Mostly ARM Cortex M3 (STM32). |
For ARM: STMCubeIDE, Atollic, some legacy IAR projects |
Largely non-existent on existing projects. Often self-reviewed and approved. |
11-30 seconds |
60% |
10% |
10% |
Show
|
| Ad hoc developer testing |
STM microprocessors - Platform will also create libraries of tools for future development |
VS Code
Cube IDE (eclipse) |
Henny Penny has traditionally been a single developer per product line company, so they were minimal |
1-5 minutes |
33 |
33 |
33 |
Show
|
| N/A |
Its a fryer or simulated fryer |
Eclipse, Bitbucket, Jira |
N/A |
Under 10 seconds |
0 |
100 |
0 |
Show
|
| Manual checking. |
Controls a fryer (RTD ADC input, switch input, Relay outputs, etc.) |
STM32CubeIDE |
NA |
31-60 seconds |
20 |
50 |
30 |
Show
|
| I don't, I fix bugs. |
I work primarily with Nordic Semiconductor MCUs and NCS/Zephyr Rtos |
Vscode, Jlink |
Generally, no code review unless my company pays for outside review. |
11-30 seconds |
60 |
20 |
20 |
Show
|
| I am too new to Henny Penny to fully know the testing process. |
Embedded Development |
Jenkins, Visual Studio Code, Cpplint, Clang-format, Cppcheck... |
I am too new to fully know the code review process. |
1-5 minutes |
30 |
50 |
20 |
Show
|
| - Minor unit tests
- Unit tests generally are done as CLI commands |
- Various embedded nodes
-- STM32, NXP Kx Family
- Various SoMs + SBCs running linux
|
- STMCubeIDE
- MCUXpresso
- VSCode
- Segger J-Link
- Saleae Pro 16 Channel |
PRs in BitBucket; conventionally informal, but trying to change that. |
1-5 minutes |
25 |
10 |
65 |
Show
|
| - Minor unit tests
- Unit tests generally are done as CLI commands |
- Various embedded nodes
-- STM32, NXP Kx Family
- Various SoMs + SBCs running linux
|
- STMCubeIDE
- MCUXpresso
- VSCode
- Segger J-Link
- Saleae Pro 16 Channel |
PRs in BitBucket; conventionally informal, but trying to change that. |
1-5 minutes |
25 |
10 |
65 |
Show
|
| traditional debug and uart console |
stm32 esp32 |
cube ide
vscode
jlink |
mainly we dont do review we do functional testing |
1-5 minutes |
30 |
0 |
70 |
Show
|
| Through manual observation of system behaviour. |
STM32 Microcontrollers |
STM32CUBEIDE
|
Not something that I do very often but am starting to do now and am finding it very rewarding. |
31-60 seconds |
40 |
10 |
50 |
Show
|
| Some unit tests. Mostly integration testing. |
Arm Cortex M4 processor |
VSCode, arm-gcc |
We use Gerrit for code reviews. |
1-5 minutes |
30 |
10 |
60 |
Show
|
| Traditional way |
32-bits MCU, bare metal and embedded linux |
VSCode.
|
I have a practice of reviewing my code as soon as its basic functionality is implemented. |
11-30 seconds |
50 |
10 |
40 |
Show
|
| Using gtest |
Linux |
VS Code, Vim |
We do have code review in this group. |
1-5 minutes |
40 |
40 |
20 |
Show
|
| Windows debugger, protocol analyzer/jammer, automation test config |
Windows server running our PCI-e adapters connected to a storage system over a network |
Visual Studio
Klocwork
Enterprise WDk
Driver verifiers |
Peer reviews |
1-5 minutes |
4 |
4 |
2 |
Show
|
| I will write a separate module called test.c and will use member functions to test the code. To enable testing I will use Macros in my main function. If Macro is set, then the test code would work, else production code would work. |
I am using Linux - ubuntu distribution, 20.04 version. |
Visual Studio code, Segger Embedded Studio, STM32CubeIDE, MCUXpresso, Simplicity Studio. |
I will thoroughly check for all corner cases in my code. |
31-60 seconds |
40% |
10% |
50% |
Show
|
| write unit tests, use 3rd vendor test tools |
consumer devices, data center products |
ARM C++ compiler, Eclipse GUI |
use git review |
5-30 minutes |
40 |
20 |
40 |
Show
|
| unit testing and manual testing using print statements |
microcontrollers (ARM, C2000) |
Eclipse IDE, JTAG debugger, Logic analyzer and oscilloscope. |
Pull request |
1-5 minutes |
50 |
20 |
30 |
Show
|
| Some unit test, and manual test |
Embedded system |
Visual Studio Code |
Pull request |
31-60 seconds |
0 |
0 |
0 |
Show
|
| We have a small suite of unit tests (not much coverage), and then we have a software quality team test many aspects of the functionality of the software. I normally verify basic functionality before even passing it off to them. |
Currently an ARM Cortex M4F chip, but that may change in the future. Likely still ARM Cortex though. |
VSCode as my text editer, ARM-gcc is the main compiler, proprietary tools are also used quite often. |
We use gerrit for reviews. Code must be reviewed by someone other than yourself before submitting. |
1-5 minutes |
25% |
5% |
30% |
Show
|
| Unit test, integration test, alpha, beta, preprod envs. |
Not sure what 'system' means here. |
vim, company private IDE |
check correctness, coding style, test coverage. |
31-60 seconds |
70 |
20 |
10 |
Show
|
| No |
STM32, ARM/X86 Linux PC |
VS Code Eclipse |
They are long. |
Under 10 seconds |
30 |
10 |
60 |
Show
|
| Using google framework, we write test cases for the code under test. |
Earlier network elements now, data collectors for water meters. |
c cross compiler for nxp platform |
Reviewers follow the review guidelines document and review the code. |
1-5 minutes |
10 |
4 |
3 |
Show
|
| Generally top-level integration testing when changes are made |
Embedded Linux + FPGA w/soft microcontroller |
vim, CMake, Intel Quartus |
Very basic reviews on each pull-request |
5-30 minutes |
10 |
5 |
85 |
Show
|
| Run on hardware in the debugger. Hack my code to hardcode values or execution paths. |
STM32 Cube |
STM32 Cube IDE (eclipse), CLion |
All code must be merged via pull requests. All pull requests must be approved by invited reviewers |
1-5 minutes |
60 |
5 |
35 |
Show
|
| Manually. No unit tests or any automated tested machinery. |
Linux on x86. Basically a mini-desktop platform with a few GB of memory. |
CMake, GCC, Clang format, VS Code, Visual Studio |
All changes to the main dev branch must be submitted as a PR on bitbucket, req. one reviewer. |
11-30 seconds |
5 |
0 |
5 |
Show
|
| we don't |
embedded device |
stm32cubeide |
NA |
1-5 minutes |
50 |
0 |
50 |
Show
|
| Functional testing |
STM32 Cortex-M7 |
STM32CubeIDE |
Pull requests are reviewed by the team before merging into the main branch. |
31-60 seconds |
7 |
4 |
3 |
Show
|
| Manual testing. Very limited automated testing |
Embedded devices |
N/A |
Peer reviews for all pull requests |
1-5 minutes |
40 |
20 |
40 |
Show
|
| With log files and debugging statements |
Linux-OS based machine |
Visual Studio Code and GDB |
Pull requests are created that reviewers can comment on |
5-30 minutes |
20 |
40 |
40 |
Show
|
| run it |
- |
- |
- |
31-60 seconds |
50 |
10 |
40 |
Show
|
| Hardware Debugger, Print Statements, Tracealyzer, GPIO Toggling. |
STM32 Microcontroller with Cortex-M7 core, Free RTOS, GUI UI, pulse real time measurements |
STM32 CubeIDE, Clion |
I like to pull the code down and go over it in the IDE. |
5-30 minutes |
60 |
10 |
30 |
Show
|
| unit tests with google test |
pc windows software, android apps |
Qt Creator, android studio |
too few developers |
31-60 seconds |
70 |
15 |
15 |
Show
|
| debug and functional tests |
embedded devices |
Platformio for Arduino |
no code review |
11-30 seconds |
33 |
33 |
33 |
Show
|
| Currently I am writing testcases using utest, and ensure that all test cases are passed. |
Right now I'm working on a cellular module for water meters. |
IAR Embedded workbench, Visual studio, GIT |
Before merging the code into remote branch, my code will be reviewed by all other team members |
1-5 minutes |
5 |
3 |
2 |
Show
|
| I normally test the code on the target using a programmer/debugger tool. |
The target is an embedded system based on 16bit or Arm microcontroller |
I usually use the IDE supported by the microcontroller manufacturer. |
It's usually done by myself in order to find mistakes or improve code, sometimes I ask to colleagues |
1-5 minutes |
30 |
20 |
50 |
Show
|
| As a developer write and test against unit tests. Commits are tested by an automated build system. |
Thermal printers controlled by an embedded Arm system. |
Qnx Momentics, PCLint, CppuTest |
N/a |
5-30 minutes |
60 |
10 |
30 |
Show
|
| Code first, run existing tests, and create a new test if necessary. |
Target system is either an x86 VM, or an ARM chip. |
Eclipse |
Done with either a review software, or pair programming. |
11-30 seconds |
30 |
30 |
40 |
Show
|
| Python UnitTest framework unsing the web interface of our device (kind of system test) |
ARM Cortex A based embedded device running on Linux |
Eclipse, GCC/GDB, PyCharm, GitLab, Teamcity |
|
31-60 seconds |
10 |
40 |
50 |
Show
|
| Python unit tests and teamcity CD/CI |
Embedded linux and rtos |
Pycharm, Visual Studio Code, Virtual Box |
I often make silly mistakes |
31-60 seconds |
5 |
2 |
3 |
Show
|
| Unit testing, acceptance testing, manual testing for the GUI |
PC |
Visual Studio |
We are a team of two: we review each other |
11-30 seconds |
60 |
20 |
20 |
Show
|
| We currently have a few MSTests. Everytime we commit something these tests are executed.
Also before committing we execute the tests manually. |
Windows PC |
GitLab
Visual Studio
Confluence
ReSharper |
We have a small team (2 people). So usually before committing we look at the code together. |
11-30 seconds |
50 |
20 |
30 |
Show
|
| Mostly manual testing |
Embedded devices (cortex A with Linux or M architectures with RTOS) |
Eclipse, Embedded Wizard IDE, |
I've never had, except for small parts of code when they were needed by one of my colleagues |
31-60 seconds |
50 |
40 |
10 |
Show
|
| Mostly with automated scripts for unit, integration and regression test. Some unit tests (not driving the development), some debugging.
|
Portable audio analyzer, dual ARMv7 running Debian 10 on Linux kernel 4.9.11 with RT patch |
Eclipse CDT, Visual Studio, VS Code, PyCharm, Git/GitExtensions, TeamCity |
Only occasional. Some pair programming. |
31-60 seconds |
50 |
25 |
25 |
Show
|
| Some unit tests written after the code is "ready", plus integration/system tests. A a lot of manual testing... |
Hand-held device: MCU running RTOS, display, keys input, storage, USB, cloud connectivity |
-- |
Don't have code reviews at the moment, but planning to start doing it |
31-60 seconds |
30% |
15% |
55% |
Show
|
| sometime asserts or googletest |
Ultra low power embedded systems (bare metal without OS) on 16 or 32 bits (ARM) MCUS |
Mostly eclipse based tools, sometimes VSCODE |
Not yet really doing those unless a colleagues asks to do them |
1-5 minutes |
33% |
33% |
33% |
Show
|
| write and run automated unit and integration tests |
we develop for an ARMv7 CPU in printers |
Momentics, svn, git, vim |
we have a remote, asynchronous code review process, allowing experts in any time zone to give input |
1-5 minutes |
30 |
30 |
40 |
Show
|
| debugging mode,
non regression test on target side |
embedded system |
vendor IDE |
no code review |
1-5 minutes |
40 |
30 |
30 |
Show
|
| Unit tests |
Currently our target system is SPC58NH92C5 (CHorus10M) - triple core, PowerArchitecture CPU
|
CMake
Greenhills compiler
other inhouse tools
|
Walkthrough the changes |
1-2 hours |
2 |
2 |
6 |
Show
|
| By debugging and stepping through code to ensure proper execution |
A test instrument that contains a handful of separate boards controlled by one central processor |
IAR EW
Visual Studio
|
Loose peer review |
31-60 seconds |
4 |
3 |
3 |
Show
|
| Manual hands-on testing of product. |
Embedded system running Android OS |
IAR Workbench |
Lead SW developer checks over code before it is committed. |
31-60 seconds |
6 |
3 |
1 |
Show
|
| - |
Mostly STM32 |
An IDE, development board and a logic analyzer. |
- |
5-30 minutes |
40 |
10 |
50 |
Show
|
| Manually |
Its a motor tester (Test and measurement equipment) |
IAR Embedded workbench. |
Colleagues. |
31-60 seconds |
10 |
5 |
5 |
Show
|
| Mostly functional/manual level testing. |
Various embedded processors, incl Renesas, Arm & PiC |
VS Code, VS Studio, MPLab, IAR compilers/debuggers |
Not normally done in past at VF, if done then informal/ad-hoc when needed. |
11-30 seconds |
20 |
40 |
40 |
Show
|
| With great difficulty. Unit testing not included in the code base, mostly; impractical to retrofit. I often change some small piece of complex calculations, validating results is hard. For more re-usable, general, new components, I unit test. |
Windows (desktop, some embedded stuff), and other embedded platforms (with no OS). |
mostly Visual Studio, some IaR embedded workbench, some Android Studio. |
I asked once for a code review here, got nothing. No one has ever asked me to do code review here. |
31-60 seconds |
6 |
2 |
2 |
Show
|
| We have application and test engineer run validation tests on the product. |
Our products from bare metal C, windows embedded using C++ to Windows running hybrid C++/C#, Android |
IAR compiler, Visual studio, Android studio, Borland C++ |
Lead software developer would review my subversion check-ins and send back code review comments. |
11-30 seconds |
5 |
2 |
3 |
Show
|
| It is tested manually by others by following test plans. Prior to others testing it, I perform manual tests of my own to verify functionality. |
We have multiple target systems but my current system is Android on top of Linux. |
Android Studio |
I perform code reviews on each check in and provide guidance for improvements. |
Under 10 seconds |
70 |
15 |
15 |
Show
|
| I had a SW dev course that used Maven as a testing platform for all our Java and JS code for a web app project. Test functions were written for each new code piece prior to development. |
Not sure. |
Not sure what the team is currently using. |
Not currently on the team. |
5-30 minutes |
70 |
0 |
30 |
Show
|
| Manually by hand or by giving the code to others in the company. |
Unsure as well. |
Android studio |
Minimum and stylistic. We have pretty large and infrequent commits. |
Under 10 seconds |
30% |
20% |
50% |
Show
|
| I test code manually by running the program and performing different behaviors. |
unsure |
Android Studio, Visual Studio, SVN |
They are informal comments made after code is submitted |
11-30 seconds |
50 |
25 |
25 |
Show
|
| Test cases are written in Ceedling for an Embedded C project, and NUnit for a C# project. Note that sometimes the test cases are written "after the fact".
Additional tests done by QA after a release candidate is ready. |
It is a two Embedded processor system, one runs code written in C, the other in C# running on WinCE. |
Debugger, simulator, demo code, test harnesses, lab tools. |
If code reviews are done (if at all) they are informal. |
Under 10 seconds |
50 |
25 |
25 |
Show
|
| Unit Testing, CI pipeline |
SSD contollers. |
GNU GCC tool chain, JTAG debuggers, SIMICS enviourment. |
we use the code review system that comes with gerit. |
1-5 minutes |
10 |
40 |
50 |
Show
|
| Writing Unit tests. On actual H/W sometimes |
storage Controller |
Visual studio code, Source Insight |
None started in current company |
1-5 minutes |
40 |
40 |
20 |
Show
|
| PC Simulator |
Arm based controller |
gcc, gdb, VS Code, Source Insight |
- |
31-60 seconds |
40 |
30 |
30 |
Show
|
| I have test application which call the functions in a required flow. The Test APP has the added functionality to test all the interfaces for user. |
Multiple OS Like Windows,Linux,ESXi. The system should satisfy the pre-requisites SW and HW
|
Microsoft Visual studio
Linux GCC Compiler
Cross Platform Toolchain
|
The Code is reviewed by Self and Team with tools |
30-60 minutes |
20 |
60 |
20 |
Show
|
| We have testing environment and CI pipeline. |
lenovo laptop with 16GB RAM and window10 OS |
vim or visual studio code |
we use gerrit for code review |
1-5 minutes |
20% |
20% |
60% |
Show
|
| Code development yet to start |
SOC firmware |
NA |
NA |
31-60 seconds |
70 |
10 |
20 |
Show
|
| I am new to Marvell.Previously we have used Unit tests written in C and ran over visual studio |
It is a SoC with 12 ARM R8 and 2 ARM M7 |
Visual studio code |
I am new to Marvell and I dont know the answer to this. |
1-5 minutes |
40 |
20 |
40 |
Show
|
| We do manual and Automation testing.
In Manual testing, we test for particular fix/functions by running specific test.
In automation testing, we test complete code by running different test cases, which covers maximum code. |
OEM Servers with Marvell Products |
Microsft Visual Studio
Linux
Perforce
Git |
Code review is done among different team members, where code changes and unit test result shared. |
1-5 minutes |
40 |
30 |
30 |
Show
|
| PC simulation environment using python |
ARM based controllers (SoC) |
VS Code, Source Insight, GCC Toolchains, WSL |
Peers review using gerrit |
1-5 minutes |
40% |
30% |
30% |
Show
|
| Either on Simulator or EVB. |
I use a Windows Host. |
ARM Compiler 6, VSCODE |
I review the code changes thoroughly. |
5-30 minutes |
50 |
30 |
20 |
Show
|
| I have not tested the code yet |
I dont know about the Target System. |
SourceInsight, VScode, Vim etc |
I am a new Joinee and I have not created any code reviews yet |
2-4 hours |
30% |
30% |
40% |
Show
|
| PC Simulator written in Python |
SOC |
Arm compiler/debugger |
Internal |
5-30 minutes |
50 |
30 |
20 |
Show
|
| UT in visual studio |
Windows, Linux |
VS Code, Git, Jira |
peer reviews, SME reviews |
1-5 minutes |
60 |
30 |
10 |
Show
|