<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wouter Bauweraerts on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/wouter-bauweraerts/</link><description>Recent content in Wouter Bauweraerts on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 28 Aug 2025 07:00:00 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/wouter-bauweraerts/index.xml" rel="self" type="application/rss+xml"/><item><title>Testing Done Right!</title><link>https://javapro-en.svenruppert.com/testing-done-right/</link><pubDate>Thu, 28 Aug 2025 07:00:00 +0000</pubDate><guid>https://javapro-en.svenruppert.com/testing-done-right/</guid><description>&lt;p&gt;Oh no! Not another article about testing! You can find a lot of publications about automated testing in software development, but there is a good reason for it. Testing your code is one of the most important aspects in software development!&lt;/p&gt;
&lt;p&gt;I’m not going to write yet another article about how you should write your tests. I’m also not covering the details of various types of tests. I will elaborate on some pitfalls you should be aware of when writing tests and how to solve them. This is not a scientific approach; it is just my opinion. What&amp;rsquo;s covered in this article? Let&amp;rsquo;s start with discussing why testing is so important in software development. Next, I’ll elaborate on some risks and how we can avoid them. I will also dive into sociable testing and test data generation.&lt;/p&gt;</description></item></channel></rss>