members
Measuring the Productivity of Developers
Episode 46: Better Built By Burkhard
Continuous Delivery
Following the principles and practices of continuous delivery helps manufacturers provide better software faster. Continuous delivery is all about feedback within seconds, minutes, hours and days. The best way to gain this feedback is to run a continuous delivery pipeline, which enables your development team to work at a constant and fast pace - without sacrificing quality. Continuous delivery is the secret formula for high-performance teams.
Latest posts
members
Episode 40: Better Built By Burkhard
Doing TDD with I/O-Free Tests
members
Episode 38: Better Built By Burkhard
Standard Metrics for Continuous Delivery
members
Episode 36: Better Built By Burkhard
A Basic Continuous Delivery Pipeline for Embedded HMIs
members
Episode 33: Better Built By Burkhard
Why TDD is a Main Driver for High Performance
members
Episode 32: Better Built By Burkhard
My Favourite Books of 2022: Enabling Continuous Delivery
The Key Principles of Continuous Delivery
In the seminal book Accelerate, Forsgren and her co-authors provide empirical evidence that Continuous Delivery has a positive impact on the performance of software development organisations. If organisations neglect some of the principles and practices of Continuous Delivery, their performance
Can We Use Trunk-Based Development for Legacy Software?
Not right away! Trunk-Based Development requires that the software builds and passes enough tests, before we integrate our changes into the main branch (a.k.a., trunk). We have enough tests, if breaking the software is highly unlikely. By definition,
Applying TDD to Classes Accessing Files
We start with unit tests reading a file line by line with QFile. Unit tests accessing the file system are not considered unit tests, as they may be slow and may depend on each other in surprising ways (see A
Applying TDD to HAL Drivers with Memory-Mapped I/O
A client recently asked me to help them get a legacy HAL driver under test. They want to use TDD to maintain and extend the driver. We ran into a couple of problems, because the tests run on a 64-bit
A Basic Continuous Integration Pipeline with GitHub Actions
In a previous post, I built a basic CI pipeline with CTest that uploaded its results to a CDash board. It worked fine except that we had to start the pipeline manually from the command line. In this post, we
Building a CI Pipeline with CTest and CDash
We can use CMake, CTest and CDash to build a basic Continuous Integration (CI) pipeline. The pipeline builds the applications, runs the tests, collects coverage information and uploads all the results to a dashboard on a web server. All this