
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.

100% branch coverage achieved—and yet bugs were still found. What this says about code coverage as a metric, and why assertions are crucial.

Flaky end-to-end tests and 40% of time lost to maintenance: one HTML attribute added in 2017 still prevents this today.

REST, GraphQL, webhooks, MCP: knowing which API protocol sits behind your system shapes how you test, what you catch, and how many tokens you burn.

Software architecture rarely fails on the tech. Career frameworks, delivery pressure, and untouched monoliths shape your codebase more than any design pattern.

Software architecture can go stale while you are still writing it down, not only after years. Which decisions must be fixed and which stay 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 found writing unit tests in Java easier than in their own language. The interface architecture made it work on a mainframe.

200 system states and a virtual control unit replace the physical test cabinet in e-cars. Thermal management tests get earlier and sharper.

API interfaces either break silently or get caught early, depending on the setup. Contract testing stops breaking changes in the pipeline.

164 subsystems, national lightning protection rules and offshore turbines without access. Testing wind turbine software is harder than it looks.

Teaching testing in university before real projects put pressure on you: Why architecture trumps testability and ChatGPT disguises it.

Developer friendliness costs time short term, saves it long term and makes teams happier. REST mocks and test interfaces show how it works.

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 is really testing side effects across the whole system. Why enterprise testing needs its own rules and skills.

From a sluggish monolith with hours of end-to-end testing to fast microservices: Which test strategy really works for this.

280 UI tests in under three minutes without a backend are possible with isolated UI testing. Mocked API responses keep the suite stable.

Those who test protect everyone on the team and in the project, not just themselves. A test net for embedded builds on CMake and Google Test.

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.

Shift left parallelizes testing before go-live, shift right watches production. One insurer runs the same UI tests in both worlds. How that works.

Production data often only covers 70% of test cases. How to systematically test data processes and get business and IT on the same page.

The hardware arrives late, testing starts anyway. Why simulators fail at timing and bus protocols, and when real target hardware belongs in the CI pipeline.

255 form variants, 16 federal states and over 100 fields per form stay manageable. Model-based test data and generic UI automation help.

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 tools, manual transfer errors and no cross-system solution: that was test data management. A store concept changed the entire setup.

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 is largely a question of organization instead. Monoliths, DBAs and silos slow things down most.

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.