Anyone involved in software testing and quality wants a practical approach to the basics of testing methods. This can be found, for example, in the book "Software Testing kompakt", which covers a wide range of topics from the test pyramid, Java test frameworks and test automation approaches to the sustainability of tests.
In this episode, I talk to Pascal Moll about his book "Software Testing Kompakt". It's about the basics of testing and test automation with practical examples from the Java world. Whether test pyramid, JUnit or Selenium. Many methods and tools are illustrated. In his book, he also addresses topics such as sustainability: How much do our tests actually affect resources?
"I've been asked this quite often at lectures, talks or other occasions: How would you start if you wanted to get into testing now?" - Pascal Moll
Pascal Moll is a freelance consultant. In 2021 he came second in the 'Freelancer of the Year' competition. His focus is on Java development, test management and test automation of web and desktop applications, especially SAP. He is an 'ISTQB Certified Tester, Full Advanced' and a certified software architect. He regularly shares his knowledge in podcasts, webinars, articles and blog posts. Since 2024, he has also been a lecturer at the Würzburg-Schweinfurt University of Applied Sciences (THWS) for the Software Testing course.
More and more companies are relying on digital solutions, and software must function reliably. But how do you actually ensure that programs run without errors? This is exactly what the podcast "Softwaretesting kompakt" with guest Pascal Moll is all about. At German Testing Day 2025 in Frankfurt, host Richie talks to the experienced author and tester. Pascal has written the book "Software Testing Kompakt", which provides a practical introduction to testing and test automation with Java. In this blog edition, we highlight the most important points of the conversation.
Many people don't know which tests they need or how to get started. Pascal Moll says that he is often asked whether you need to be able to program as a tester. His book provides an overview for beginners: What is testing actually, how do test types differ and why is the topic so diverse? Anyone who deals with testing quickly realizes that it doesn't always mean the same thing. The most well-known terms alone, such as unit test, integration test or acceptance test, show how deep the field goes.
The podcast also makes it clear that it is important not to just start testing, but to build up basic knowledge. If you know how the different test levels work, you can test in a more targeted and better way.
Richie asks Pascal what testing looks like in typical Java projects. Pascal explains the famous test pyramid: at the bottom are the unit tests that run most frequently and quickly. They test small units of the program. At the top are integration tests, which allow several parts to interact. At the top are system and acceptance tests, which usually take longer. The Selenium tool is often used for surface tests.
Many of these tools exist for other languages such as Python, but Pascal remains in the book and conversation with the Java focus. JUnit is the best-known test framework here. Those who work with APIs can use Wiremock for testing. Maven helps to integrate libraries and control tests in the build pipeline.
The Java world offers a wide range of test tools. JUnit remains the classic for unit tests. When it comes to API testing, Wiremock is practical. Selenium takes care of surface testing. Maven manages everything to do with libraries and the build process. Pascal's book explains clearly how these tools work together and how to use them for projects.
One exciting point is the automation of tests. Developers can use Maven to control which tests run when. This helps to detect errors early on and saves effort. The concepts of how to work with native language (Given, When, Then) are part of Behavior Driven Development, which can also map complex test cases.
Pascal explains how to manage test data cleverly. Feature files and Gherkin code are ideal for organizing data in scenarios. For large amounts of data, he recommends using CSV files or even real databases. Organizing data is crucial to making tests understandable and repeatable.
Java brings its own challenges. In the podcast, Pascal says that developers often pay attention to maintainability, but sometimes overlook the "edge cases". Testers should check what happens in the event of invalid values or errors. Exception handling is dealt with specifically so that programs also react appropriately in an emergency. This perspective helps to step out of developer thinking and thus make the software more robust.
A surprise topic in the book is sustainability. Because testing not only costs working time, but also electricity. Not every test case makes sense. Running thousands of tests consumes resources. Pascal and his co-author Daniel encourage you to consider in advance which tests are needed - especially if the tests run on large clusters or several browsers are opened in parallel. Not everything needs to be tested. Quality also means testing what is important and using energy wisely.
The interview with Pascal Moll shows that software testing is not rocket science, but neither is it a topic that you can "just do on the side". A lot can be achieved with good tools, a clear understanding and an eye for the essentials. If you want to deepen your knowledge, you can even win a copy of his book - link in the show notes. One thing is clear: a good introduction to testing helps every developer and every company to ensure the quality of their software.