
Accessibility in Apps: Why Do We Perform Manual Testing?
Mobile accessibility testing is mostly manual: VoiceOver, TalkBack and switch control can block each other, so the test matrix has to log every setting.

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.

In automotive testing, even a windshield wiper is safety-critical. Automotive SPICE and functional safety prescribe boundary value analysis and MC/DC.

Cybercrime works like a start-up with a division of labor. Defenders should think like attackers, separate systems and not pay the ransom.

Does Continuous Everything really improve quality? Six years of data show trunk-based development smooths out the defect peaks around each release.

Domain storytelling is collaborative modeling: users tell stories from their domain, the team draws actors, work objects and activities as a diagram.

Software testing starts with clarifying the assignment, or errors surface late and get expensive. One of several lessons testers can take from coaching.

Team alignment with OKR needs three to five early metrics, health metrics as a counterweight and a neutral facilitator who guides goal setting.

Overcoming resistance to change means addressing the transition and the identity people lose. Skeptics become allies, and emotion beats slide decks.

Green IT makes software draw less power, green by IT uses software for sustainability. How the Pink Index, caching and smaller cloud nodes help.

Software testing paid by test cases, coverage and errors found: how Europe's first independent test lab worked in 1978 and which principles still hold.