Testing accessibility with those affected
Accessibility does not work automatically just because components are accessible. What goes wrong when assembling and why manual testing remains.
Conversations with testers, developers, and coaches who work in the field.
Accessibility does not work automatically just because components are accessible. What goes wrong when assembling and why manual testing remains.
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.
Anyone familiar with impostor syndrome knows that rational thinking often doesn't help. Which strategies really lead out of the impostor cycle.
Model-based testing sounds good, but often fails due to a gap between the abstract model and the actual test. Why this is the case and how a two-phase approach can help.
AI-generated test code that compiles but tests the wrong thing: Why writing unit testers yourself and having business code generated instead is often the smarter approach.
Testing proves bugs, but never freedom from bugs. Formal methods can do this, from type systems to verified kernels, and the effort is more scalable than expected.
What does quality actually mean when no one in the team has an answer? A look back at 20 years of testing and the questions that are now becoming urgent.
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.
More data does not automatically mean better decisions. Which software metrics really help and why context is more important than any number.
Anyone who writes requirements already thinks like a tester - or should. A look at a data warehouse project shows how this ensures quality at an early stage.
From tester to leader: Why the interpersonal challenges exceed anything a leadership course can ever prepare.
Pen tests at the end of a project always find the same things: headers, misconfigurations, standard gaps. Integrating security into the pipeline reduces this to 4 to 5 really critical findings.
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.
Mechanical engineers and the Cyber Resilience Act: What companies can expect, where the real hurdles lie and why early action brings a concrete cost advantage.
Testing is a team affair, not a lone wolf discipline. Which skills are really in demand today and how to plan your career path in testing.
Architecture documentation quickly becomes outdated because the tools slow it down. Documentation as Code and Continuous Documentation solve exactly that.