EN 
DE Testing, quality and safety of embedded software
Software quality is unfortunately still too often reduced to the formula: "As long as it works!" But anyone with experience working with software that has evolved over years knows the unpleasant consequences of this one-sided view. Precisely because software can be quickly changed and expanded over a long period, its quality must be given special attention.
Expertise: Software quality is both the means and the goal of successful software development
Simple and clever: wogtest is the innovative MicroConsult solution for embedded software testing.
Fields marked with make it easier for developers to integrate Test-Driven Development into embedded projects – without the complexity of Google Test, without time-consuming porting, and free to download.
Blog post: Simple and clever – wogtest
Test ended well, all is well.
Black-box tests using white-box metrics do not result in gray-box tests. However, each of the three fulfills an important function in defining the end of the test and minimizing the number of necessary software tests.
Blog post: Test ended well, all is well
TDD – Test-driven development of embedded systems
Test-driven development (TDD) is the implementation of the test-first approach in component testing and involves writing unit test cases before the actual implementation. Adherence to just three rules and a few tricks for dealing with the target hardware bottleneck makes TDD possible even for embedded systems.
Blog post: Test-driven development of embedded systems
Test-First = Test first, think later? – Test-driven development of embedded systems
Many agile development frameworks emphasize the test-first approach, which, regardless of the test level, is based on starting with testing as the first step towards the actual implementation of functionality: testing at a point when one is still focused on the "what" and the "how" is still pending. Test-driven development (TDD) is the implementation of the test-first approach in component testing and means writing unit test cases before the actual implementation. Adherence to just three rules and a few tricks for dealing with the target hardware bottleneck also make TDD possible for embedded systems.
Presentation: Test-First = Test first, think later (ESE 2019, PDF)
Script: Test-First = Test first, think later (ESE 2019, PDF)
Secure software from the start – developers under time pressure
Just as dragons plagued humans and threatened their lives in ancient myths, today technically unsafe systems pose a source of danger. The crucial difference: while dragons belong to the realm of fables, technical systems as potential sources of danger are part of our everyday lives.
Article: Taming the dragon – Secure software from the start
Functional safety: Mitigating systematic errors through structure and processes
A holistic approach and a thorough understanding of the details are essential when it comes to creating functionally safe systems. Software integrity can be achieved through structured and targeted methods and techniques.
Blog post: Functional safety through structure and processes
Object-oriented testing of embedded software
Introducing C++ into an embedded project is a major challenge for most teams. Underestimating the effort involved can potentially delay the entire development process. And now, the C++ software is supposed to undergo additional complex security testing? Is it even possible to test quality into C++ software?
Blog post: Object-oriented testing of embedded software
Debug – Press:
MicroConsult's cooperation with Lauterbach provides developers with bundled know-how for multicore debugging.
MicroConsult and Lauterbach have entered into a cooperation with the common goal of offering even more effective support to all embedded developers who use multicore architectures.
Press release: Multicore Debug Training (German)
