
AI Quality Assurance: When There Is No Clear Test Oracle
AI quality assurance lacks a clear test oracle, so quality is measured statistically. Metamorphic and pairwise testing help, reproducibility stays hard.
Conversations with testers, developers, and coaches who work in the field.

AI quality assurance lacks a clear test oracle, so quality is measured statistically. Metamorphic and pairwise testing help, reproducibility stays hard.

The DevOps CALMS model (culture, automation, lean, measurement, sharing) turns a battle cry against burnout and waste into daily team practice.

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? Fairness measures contradict each other, so an assurance case breaks the claim down.

Tests from rules replace hand-written cases: describe a system property once and a tool generates thousands. A shrinker traces failures to the cause.

Mobile app testing, second attempt: HUK Coburg scrapped four years of automation. Now manual testers write keyword-driven tests with Robot Framework.

Software metrics are often avoided because they reveal inconvenient truths. Yet a simple table can be enough to forecast testing effort and defects.

Sustainability in testing is already hidden among ISO 25010 quality criteria. Dropping redundant test runs saves computing power, and with it money.

User story testing starts with acceptance criteria written as concrete examples. Add specs only where they help, and use the light Three Xs strategy.

Mobile accessibility testing is mostly manual: VoiceOver, TalkBack and switch control can block each other, so the test matrix has to log every setting.

Quality by design in software prevents errors before testing has to find them. The pharma-born approach rests on risk analysis and process metrics.

Quality assurance can't be one compulsory lecture. Measurement, resource limits and sustainability belong in every semester of a degree.

Classic test techniques such as decision tables still apply in agile projects. So why does quality suffer when twelve teams work side by side?

Quality assurance at Otto works without a testing team. 15 quality specialists coach 60 teams, helped by Quality Buddies and consumer-driven contracts.

Test selection with Teamscale runs only tests that cover changed code, so 6,000 PyTest cases fit a five-minute budget in a ten-minute CI run.

Automated tests catch only about 57 percent of digital accessibility issues. The rest needs manual testing and an early start in the style guide.

Teams often make architecture decisions while coding, without noticing. Double pairs, a long-term view and mob programming make them a team effort.

Evolutionary quality goals show which quality characteristics count in each system phase. Maintainability pays off once growth brings new developers.