Open Source: With Care
Open source is more than free software: licenses, maintenance, quality, and the question of what you can give back to the community.
Quality and testing concerns around software architecture, testability, interfaces, integration, databases, and data quality.
Open source is more than free software: licenses, maintenance, quality, and the question of what you can give back to the community.
Software architecture is a cornerstone of testability. Why testers and architects should have coffee together more often.
Explore how effective test data management can drive software quality. Discover strategies for overcoming testing challenges in 2025.
Optimize your SAP test strategy for quality in e-government systems. Master complexity with integrated testing approaches. Discover how to excel in 2025.
Enhance your IT landscape by tackling software testing challenges and optimizing legacy system management for future growth.
Explore effective Data Warehouse Testing strategies. Optimize results verification with Automated Testing Techniques for accurate data quality assurance.
Explore software integration challenges and the key dimensions that enhance integration test objectives effectively.
Explore what is object oriented technology and its impact on software development's promises and realities. 2025 insights await!
Discover Agile Software Testing strategies to manage technical debt and improve software quality effectively
Optimize your cloud services testing and business process modeling to enhance operational efficiency in your projects.
Optimize your data quality through targeted audits, ensuring effective database schema audit and uncovering weaknesses. Improve your data quality now.
Explore how metrics of UML diagrams in software projects enhance design efficiency and quality.
Ensure your migrated system performs equivalent to the legacy system with effective migration testing. Optimize success for software migration testing.
Optimize your geoportal testing with structured methodologies and ISTQB Certification to enhance geoportal quality assurance.
Intensive Testing of Web Services ensures high quality, leveraging WSDLTest Tool for effective API Testing Solutions and automated response validation.
Software architecture doesn’t become obsolete only after years—sometimes it happens even as you’re writing it. Which decisions really need to be set in stone, and which ones can safely remain open.
German companies want AI and robotics, but their processes are blocking any progress. Why no business case makes sense as long as data silos remain.
COBOL developers said writing unit tests in Java was easier than in their own language. Here's the interface architecture that made that possible on a 60-year-old mainframe.
200 possible system states, a virtual control unit instead of a physical test cabinet: how thermal management tests in electric cars are becoming earlier and more precise.
Let API interfaces continue to break silently or recognize them early? Contract testing shows how consumers specify what they need and changes stop the pipeline.
164 subsystems, lightning protection according to national law, offshore turbines without service access: testing software in wind turbines is more complex than it seems.
Teaching testing in university before real projects put pressure on you: Why architecture trumps testability and ChatGPT disguises it.
Developer friendliness costs time in the short term, but saves it in the long term - and makes teams measurably happier. REST mocks and test interfaces from a real project show what this means in concrete terms.
Anyone who builds test data manually or derives it from production data risks GDPR problems and hardly finds any new bugs. How synthetic generation solves this.
Anyone who configures SAP always tests side effects. Why enterprise testing needs different rules and how experts without a testing background can still get fit.
From a sluggish monolith with hours of end-to-end testing to fast microservices: Which test strategy really works for this.
280 UI tests, under three minutes, no backend required: How isolated UI testing with mocked API responses becomes faster and more stable than classic component or E2E testing.
Those who test don't protect themselves, they protect everyone. How a test network works in embedded development and why CMake, Google Test and a self-built automocker are the key.
Why does your brain just not understand some code? Working memory only processes four chunks at a time, and good code respects this limit.
What happens when a third of the adopted code is only available as a black box? How an agile mindset and honesty can save a ticket store project.
Why do testing activities always end in a traffic jam just before go-live? Shift left alone is not enough: How synthetic monitoring reuses the same test case.
Production data often only covers 70% of test cases. How to systematically test data processes and get business and IT on the same page.
Testing embedded software without having the hardware? How unit tests, CI pipelines and MISRA standards interact in practice.
255 form variants, 16 federal states, sometimes over 100 fields per form: How model-based test data generation and generic UI automation make this effort manageable.
Architecture documentation quickly becomes outdated because the tools slow it down. Documentation as Code and Continuous Documentation solve exactly that.
Separating functional and quality requirements: useful or misleading? What this distinction really means for architecture decisions.
Five different tools, manual errors when transferring, no cross-system solution: this is what test data management looked like in practice before a store concept changed everything.
Teams often make architecture decisions unconsciously while coding. Three experiments show how this can be achieved jointly and comprehensibly.
Cloud migration sounds like technology, but it is largely a question of organization. Why monoliths, DBAs and silos often slow things down more than the infrastructure.
Why are hundreds of unit testers created, but the software still doesn't run? Because isolated tests alone do not prove a feature - and that is the problem.
C++ is 45 years old and yet deeply rooted in autonomous driving, medical devices and AI libraries. What the Core Guidelines have to do with it.
Contract-based testing decouples providers and consumers so that interface changes no longer deliver any nasty surprises. How this works in practice.