Software Quality Days
15 years, a scientific track with Springer publication and speed dating: what sets Software Quality Days apart from other testing conferences.
Conversations with testers, developers, and coaches who work in the field.
15 years, a scientific track with Springer publication and speed dating: what sets Software Quality Days apart from other testing conferences.
Fair AI sounds good, but what does it mean in measurable terms? Why fairness measures can contradict each other and how a structured assurance case can help.
Millions of test cases generated automatically instead of laboriously written by hand: What property-based testing is and what its limitations are.
Throwing away four years of test automation and starting from scratch: Why this radical cut was the right decision and what was done differently this time.
Software metrics are often avoided because they reveal inconvenient truths. Yet sometimes a simple table is enough to manage projects in a measurable way.
Sustainability has long been part of ISO 25010, only hidden. Which quality criteria contribute to it and how testers can already work more resource-efficiently today.
User stories should be testable - everyone nods, hardly anyone knows how. What requirements engineering has to do with it and which three testing activities really help.
Accessibility in mobile testing: Why assistance systems hinder each other and which test matrix helps.
Don't test for errors, don't introduce them in the first place: Quality by Design transfers an approach from the pharmaceutical industry to software development.
Teaching quality as a compulsory subject is not enough. How measurement, resource thinking and sustainability are becoming part of everyday life at university.
Agile testing has long been common sense, but why does overall quality still fail when twelve teams run at each other?
60 teams, 15 quality specialists: How quality remains anchored everywhere when coaching becomes more important than classic testing.
6.000 test cases, CI runtime under 10 minutes: How test-based selection via code coverage makes exactly that possible.
57 percent of accessibility criteria can be tested automatically - the rest requires human judgment and the right process.
Teams often make architecture decisions unconsciously while coding. Three experiments show how this can be achieved jointly and comprehensibly.
Demanding maintainability early, even though the market is still lacking? Wrongly prioritized. The evolution model shows which quality goals really count and when.
Automotive testing: a windshield wiper is already considered a safety-critical system. What this means for test methods, standards and everyday life as a tester.
Out of 73 universities audited, they had to abandon one in five because there were too many gaps. What this means for software security.