
Swiss Testing Board: Measurable Learning Goals for ISTQB
The Swiss Testing Board grew from an SAQ working group and brought measurable learning objectives based on Bloom's taxonomy into the ISTQB syllabi.
Conversations with testers, developers, and coaches who work in the field.

The Swiss Testing Board grew from an SAQ working group and brought measurable learning objectives based on Bloom's taxonomy into the ISTQB syllabi.

Playwright vs Cypress vs WebdriverIO on four criteria: why Playwright wins new projects, where WebdriverIO trails, and when a switch isn't worth it.

Custom fuzz testing pairs random inputs with knowledge of the format. Why a random IBAN rarely passes the checksum, and where LLMs fall short.

Synthetic test data from XML and JSON schemas is GDPR compliant, covers extreme values and finds bugs that anonymized production data misses.

Autonomics is a new discipline for autonomous systems, drawing on control engineering, computer science and sensors. Their safety must hold at runtime.

Legacy modernization usually stalls on missing subject matter experts. How RAG makes legacy code queryable and why working in slices lowers the risk.

HUSTEF drew 260 submissions for 36 slots in 2025. Why the nonprofit conference in Budapest, held since 2011, sits on a par with EuroSTAR.

QA coaching replaced central control: eight people support over 100 applications, and an unread test manual became guardrails that teams accept.

Nudging for security starts where most attacks start: human error. Secure defaults, opt-out 2FA and password meters guide users without forcing them.

Nonviolent communication has four components: Observation, feeling, need, request. What this looks like in everyday testing.

At Signal Iduna, insurance specialists automate their own acceptance tests. With simple tools and coaching, a release check now runs in three minutes.

A reference implementation as test oracle computes target values for 2,500 signals automatically. The ISO 26262 review then becomes a code review.

Learning with simulations like the Okaloa Flow Lab lets teams and managers feel WIP limits and the pull principle at a board rather than on a slide.

A lightweight test plan does not end up in a drawer. The Federal Office of Administration built one from short modules and released it as open source.

End-to-end across web, desktop, database and 3270 hosts: where Robot Framework earns its place, where web-only tools stop, and why it won't die soon.

Many podcasts die after three to seven episodes, because the production effort is set too high. Conferences are the best source of guests for new shows.

Enterprise software testing checks how configuration changes in SAP ripple through dependent processes. Why business users test mostly the happy path.

Microservices testing at REWE: unit and API tests per service, few end-to-end tests on the money path, flaky tests in quarantine, production monitoring.