ATDD for LLMs: Failed Dialogs as Tests and Training Data
With ATDD for LLMs, each new requirement becomes a dialog-based test. After fine-tuning, the suite shows whether the model learned without regressions.
Podcast: Software Testing, AI and Quality Insights : Page 13 of 17
ISTQB in Practice: Building Test Expertise in Telecom
ISTQB in practice at a telecom vendor: exploratory testing of undocumented third-party systems, homemade load test robots and a shared test vocabulary.
Replacing an In-House Test Framework with Robot Framework
Swapping a grown XML test monolith for Robot Framework took a year, a custom .NET remote library server and one developer freed from release duty.
Stoicism for Product Teams: Don't Confuse Luck with Judgment
Stoicism helps product teams judge a decision by how it was made, not how it turned out. Its tools: premeditatio malorum, 10-10-10, a decision diary.
Test Pyramid: How Test Layers Should Complement Each Other
The test pyramid is often misread: many unit tests, high coverage, still bugs. Why many JUnit tests in microservices are really integration tests.
Quality Requirements Call for an Adaptable Architecture
Separating functional and quality requirements sounds clean, but in practice the line blurs. Good architecture hides decisions and stays changeable.
Shift Left in Acceptance Testing: Build Trust Early
Shift left in acceptance testing means testers shape requirements early. Acceptance tests then build trust instead of hunting bugs just before delivery.
Minimum Viable Test Strategy
Test strategy via workshop instead of a hundred-page document: How a collaborative format quickly brings teams to a common test picture.
Green Software: What If Planet Earth Were a Stakeholder?
Green software starts with one question: what if the earth were a stakeholder in your next sprint? Supporting old devices cuts e-waste and saves costs.
German Testing Day: End Users Set the Agenda
Since 2011, the German Testing Day has been shaped by a board of end users with no vendor interests: practical talks, open formats, unusual keynotes.
Software Expert Witness: State of the Art Means Proven
A software expert witness checks whether software is state of the art, a legal term meaning proven, and judges its maturity by defect density.
Team Conflicts: From Glasl's Stage Four, Get Outside Help
Team conflicts carry energy a team can use. Up to Glasl's stage three, managers can resolve them; from stage four, outside facilitation is needed.
Happy Birthday: Podcast Software Testing Turns One
One year, 67 episodes, over 22,000 downloads: What became of a spontaneous video idea and where the journey will take us next.
Continuous Discovery: Domain Expertise Belongs on the Team
Continuous discovery fills the gap Scrum leaves before the backlog. Event storming, story mapping and Gemba walks help the team understand customers.
Choosing an E2E Testing Framework: Requirements First
Choosing an E2E testing framework starts with your own requirements, such as Safari support or speed. Why Playwright led a comparison of five tools.
Exploration and AI: Human Context Can't Be Replaced
AI speeds up routine work, but exploration needs human context it lacks. Quality stays hard to sell, so testers should pair with developers and network.
Remote Teams: When They Outperform Office Teams
Remote teams can work better together than office teams, but only on one condition: Knowledge must be networked, not people.
The Future of Test Organization: Cells Instead of Hierarchy
The test organization of the future replaces hierarchies with cell teams, and testers need V-shape skills with deep knowledge in several areas.