Quality assurance in higher education
Teaching quality as a compulsory subject is not enough. How measurement, resource thinking and sustainability are becoming part of everyday life at university.
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.
Shift left sounds good, but does it really make a difference? How six years of data show what Continuous Everything actually changes and what it doesn't.
Throwing specifications over the fence is a thing of the past. Domain storytelling turns users and developers into a joint team before the first code is created.
What does coaching have in common with software testing? More than you might think: clarifying orders, recognizing patterns and dealing with errors as real quality levers.
Good team goals don't fail because of the concept, but because they disappear in everyday life. Three to five metrics and a moderator change that.
Change doesn't fail because of the idea, but because of the process. Why skeptics are valuable allies and how emotional connection moves more than any presentation.
Sustainability in software development has seven dimensions, but most people only know one. What carbon footprint, frequency of use and green features really mean.
outsourced in 1978, paid according to test cases and errors found: Why this approach failed back then and which principles still apply today.
Meetings in which everyone nods and nobody really thinks? Liberating Structures solves exactly that, with concrete formats for teams that want to test better together.
Model-based testing is considered complex and formal. Boxes, arrows and a flowchart are enough to uncover requirement gaps early on and generate test cases.