Practical software testing with Java
From unit tests to exploratory testing: which Java tools really count, how Maven controls the test procedure and why sustainability is often underestimated in testing.
From unit tests to exploratory testing: which Java tools really count, how Maven controls the test procedure and why sustainability is often underestimated in testing.
Stress and burnout cost the IT industry a fortune, yet one minute of breathing before a meeting can change how a whole team communicates.
Teaching testing in university before real projects put pressure on you: Why architecture trumps testability and ChatGPT disguises it.
Picking the wrong end-to-end test framework can leave whole browsers untested. Here's how to match tools to real project needs before it costs you.
Vague requirements are the most expensive problem in testing. How AI really helps when determining, formulating and checking requirements.
"It depends" is not a dodge. It is the only honest answer when context shapes every testing decision, and here is why that matters.
If you only mention bugs in an interview as a tester, you're giving away your strongest card. How to use emotions, negotiate salary and build trust.
Almost 30 years, over 1000 members, free conference tickets: What the ASQF still offers the German-speaking software quality community today.
Most teams treat BDD as a testing technique and miss the real value. Here is what happens when examples drive shared understanding instead.
Model-based testing kills two birds with one stone: better requirements and ready-made test cases from one workshop.
Testers keep losing the value argument not because their work is wrong, but because they pitch defects instead of business outcomes.
PDF accessibility doesn't just apply to websites: Why contracts, invoices and policies must now be accessible and what this means in technical terms.
Testers who frame findings around stakeholder impact, not bug counts, get action. A 15-second standup check shows how small habits outrun big transformations.
How do you create a board game that delivers real test cases? A team built it - and learned more about testing than expected.
Switching test automation frameworks mid-product is messy. Here is what a real Cypress-to-Playwright migration looks like, from the pricing clash that forced the move to AI-assisted test translation.
AI takes over testing? What it can't do: genuine curiosity, intuition and thinking outside the box. Why human tester thinking remains.
When everyone owns quality, no one really does. Why cross-functional teams often lack the deep testing skills they need most.
AI is rationalizing away tester jobs, while at the same time a wave of questionable AI-generated software is coming. What this really means for testing skills and roles.