Exploring the code vastness of the legacy space - Where no test has gone before In the galaxies of software development, ensuring quality is of paramount importance and yet so often neglected. Working in untested and unknown code is as common as it is universally disliked. Who looks forward to
In addition to principles, the Clean Code Developer Initiative also specifies various practices that a team should apply. These include integration tests (orange level) unit tests (yellow level) coverage analysis (yellow level) continuous integration (green level) These four practices together make a very important contribution to the value of correctness. The Integration and
Update 29.01.2024: I have adapted the sample code to .NET Core 8 and the latest NuGet packages. Furthermore, the code is now on GitLab instead of GitHub. Are integration tests useful? The question of whether integration tests are useful or even necessary comes up again and again in our training courses. Our clear answer
Dependencies exist in software projects. If interfaces and dependency injection are used, the construct can be tested automatically with the help of mocks.
The realization that automated tests are useful and necessary has now become widely accepted. Nevertheless, in many projects no or too few tests are written.
Inspired by the discussion with participants of a Clean Code Developer Workshop, I once again addressed the question of which strategies I use and recommend for automated testing.
In legacy code projects, there are typically few or no automated tests.
Unit tests of the GUI? Automated testing of the GUI (graphical user interface) of a desktop application is a major challenge at first glance.
Resource accesses such as reading or writing files or database accesses often cause problems in unit tests.
CCD Academy GmbH
Am Steinernen Kreuz 27
53343 Wachtberg
English 
German