
Rosenberg's Nonviolent Communication in Everyday Testing
Nonviolent communication has four components: Observation, feeling, need, request. What this looks like in everyday testing.

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.

Informal networks are who people actually turn to when things go wrong. Why they decide how fast teams adapt, and why you cannot order them into being.

An AI audit needs a yardstick. The TÜV AI Lab's AI Assessment Matrix maps test dimensions against the lifecycle, so assessors pick the relevant fields.

Quality coaching in SAFe closes the gap between teams on a release train through requirements coaching, process workshops and defect management.

Migrating from Cypress to Playwright took a team over a year alongside daily QA. The main hurdles: session handling, request interception, legacy tests.

Which headline do you not want in tomorrow's paper? Risk-based testing starts with that question. One team cut its end-to-end tests by 50 to 60 percent.

UI testing with mocked API responses checks the frontend as a full app, no backend needed. At Volkswagen, 280 tests run in under three minutes.

Requirements analysis with DEFOSPAM: seven question areas expose unclear definitions, ambiguity and missing parts. AI adds ideas, people judge them.

An AI test description makes AI systems testable: five capabilities and quality criteria like correctness and bias turn standards into concrete tests.

Only 6% of surveyed testers fit the tester stereotype. Many come from boatbuilding, theater or urban planning, and degrees barely predict their roles.