<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TDD on Sven Ruppert</title><link>https://sven-ruppert.info/categories/tdd/</link><description>Recent content in TDD on Sven Ruppert</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>sven.ruppert@gmail.com (Sven Ruppert)</managingEditor><webMaster>sven.ruppert@gmail.com (Sven Ruppert)</webMaster><copyright>© 2026 Sven Ruppert</copyright><lastBuildDate>Fri, 08 Nov 2024 09:12:39 +0000</lastBuildDate><atom:link href="https://sven-ruppert.info/categories/tdd/index.xml" rel="self" type="application/rss+xml"/><item><title>JUnit annotations in focus: The connection between @Test and @Testable</title><link>https://sven-ruppert.info/posts/junit-annotations-in-focus-the-connection-between-test-and-testable/</link><pubDate>Fri, 08 Nov 2024 09:12:39 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/junit-annotations-in-focus-the-connection-between-test-and-testable/</guid><description>&lt;p&gt;The annotations @Test and @Testable have played an important role in the Java ecosystem regarding application testing. They are essential tools that help developers make unit and automated testing more effective. In this paper, we will explore the differences and connections between @Test and @Testable analyze and the motivation behind the introduction of @Testable understand. We will also play the role of @Testable in developing your test engines and discuss their importance for the flexibility and expandability of tests.&lt;/p&gt;</description></item><item><title>The Risks of Mocking Frameworks: How Too Much Mocking Leads to Unrealistic Tests</title><link>https://sven-ruppert.info/posts/the-risks-of-mocking-frameworks-how-too-much-mocking-leads-to-unrealistic-tests/</link><pubDate>Tue, 05 Nov 2024 17:49:33 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/the-risks-of-mocking-frameworks-how-too-much-mocking-leads-to-unrealistic-tests/</guid><description>&lt;p&gt;Extensive use of mocking frameworks such as Mockito in software development can lead to unrealistic tests. This is because mocking frameworks simulate dependencies of classes or methods in order to test them in isolation. However, when too many mock objects are used, the test often loses touch with reality, which can affect the validity and reliability of the tests. It is important to use mocking carefully to find the right balance between isolated testing and realistic simulation.&lt;/p&gt;</description></item><item><title>Code security through unit testing: The role of secure coding practices in the development cycle</title><link>https://sven-ruppert.info/posts/code-security-through-unit-testing-the-role-of-secure-coding-practices-in-the-development-cycle/</link><pubDate>Wed, 16 Oct 2024 22:17:04 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/code-security-through-unit-testing-the-role-of-secure-coding-practices-in-the-development-cycle/</guid><description>&lt;p&gt;Unit testing is an essential software development concept that improves code quality by ensuring that individual units or components of a software function correctly. Unit testing is crucial in Java, one of the most commonly used programming languages. This article will discuss what unit testing is, how it has evolved, and what tools and best practices have been established over the years.&lt;/p&gt;</description></item><item><title>Comparing Code Coverage Techniques: Line, Property-Based, and Mutation Testing</title><link>https://sven-ruppert.info/posts/comparing-code-coverage-techniques-line-property-based-and-mutation-testing/</link><pubDate>Fri, 31 May 2024 09:20:30 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/comparing-code-coverage-techniques-line-property-based-and-mutation-testing/</guid><description>&lt;h2 class="relative group"&gt;What is Test Coverage?
 &lt;div id="what-is-test-coverage" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-is-test-coverage" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Test coverage is a metric used in software testing to measure the testing performed on a piece of software. It indicates how thoroughly a software program has been tested by identifying which parts of the code have been executed (covered) during testing and which have not. Here are the key aspects of test coverage:&lt;/p&gt;</description></item><item><title>Securing Apache Maven: Understanding Cache-Related Risks</title><link>https://sven-ruppert.info/posts/securing-apache-maven-understanding-cache-related-risks/</link><pubDate>Mon, 27 May 2024 14:30:22 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/securing-apache-maven-understanding-cache-related-risks/</guid><description>&lt;h2 class="relative group"&gt;What is a Package Manager - Bird-Eye View
 &lt;div id="what-is-a-package-manager---bird-eye-view" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-is-a-package-manager---bird-eye-view" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;A package manager is a tool or system in software development designed to simplify the process of installing, updating, configuring, and removing software packages on a computer system. It automates managing dependencies and resolving conflicts between different software components, making it easier for developers to work with various libraries, frameworks, and tools within their projects.&lt;/p&gt;</description></item><item><title>TDD and the impact on security</title><link>https://sven-ruppert.info/posts/tdd-and-the-impact-on-security/</link><pubDate>Wed, 28 Jun 2023 16:08:03 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/tdd-and-the-impact-on-security/</guid><description>&lt;p&gt;Test-driven development (TDD) is a software development approach that prioritizes writing automated tests while creating the actual code. There follows a cycle of writing a failed test, writing the code to make the test pass, and then refactoring the code. TDD was originally developed to ensure the quality, maintainability and expandability of the software created over the long term. The specific knowledge about the individual source text passages should also be shown in the tests. Thus, a transfer of responsibility between developers is supported. Better than any documentation, tests are always up-to-date regarding the function that has been implemented in the source code.&lt;/p&gt;</description></item><item><title>The quick Wins of DevSecOps</title><link>https://sven-ruppert.info/posts/the-quick-wins-of-devsecops/</link><pubDate>Thu, 28 Jan 2021 16:56:45 +0000</pubDate><author>sven.ruppert@gmail.com (Sven Ruppert)</author><guid>https://sven-ruppert.info/posts/the-quick-wins-of-devsecops/</guid><description>&lt;p&gt;Hello and welcome to my DevSecOps post. Here in Germany, it&amp;rsquo;s winter right now, and the forests are quiet. The snow slows down everything, and it&amp;rsquo;s a beautiful time to move undisturbed through the woods.&lt;/p&gt;</description></item></channel></rss>