C++ Core Guidelines: Ownership Is the Most Important Rule
The C++ Core Guidelines by Stroustrup and Sutter put ownership first: does code own a resource or only borrow it? Getting it wrong crashes programs.
Podcast Software Testing : Page 12 of 13
Latest Episodes
Conversations with testers, developers, and coaches who work in the field.
User Feedback at MOIA: When Colleagues Are the Users
How MOIA collects user feedback from its own drivers: monthly surveys, mockup interviews, test drives and slow rollouts to 20% of the fleet.
House of Agile Quality: Roles, Approach, and Tools as Pillars
The House of Agile Quality rests on a test foundation and three pillars: roles, approach and tools, topped by lean quality engineering methods.
Shift Left: Quality Starts with the User Story
The shift left approach builds quality in early: vertically sliced user stories, feedback in the IDE, solid unit tests and contract testing with PACT.
Ensemble Programming: One Types, the Whole Team Thinks
Four to six people, one keyboard, real code: ensemble programming and ensemble testing bring testers and developers together where meetings fail.
Cypress Component Testing: Stable Tests in a Real Browser
Cypress component testing runs in a real browser, so tests are more stable than with Jest's emulation. How it rights the test pyramid, and its limits.
Speech Recognition Testing: Every Fix Means Retraining
Speech recognition testing means testing a black box: every fix costs days of retraining. Golden test sets and generated variations find errors early.
Prompt Engineering for Test Cases: Review Remains Mandatory
Prompt engineering for test cases gets better results with few-shot examples and embedded specs. Still, two of eleven generated tests remained wrong.
Software Testers and AI: Routine Goes, Judgment Stays
Software testers and AI: routine checks move to AI, while judging requirements coverage stays a human task. A carpenter explains his path into testing.
Test Case Selection: Only Run the Tests a Change Touches
6.5 hours of test runtime, reduced to 10-15 minutes: How test case selection across C++ and Java makes it possible.
Sustainable Software Development: How Testing Saves Energy
Sustainable software development starts with the requirements, long before deployment. Performance, maintainability and lean test pipelines all count.
Game Testing at Tibia: Exploratory Testing Before Checklists
Game testing for Tibia means weekly patches for a 25-year-old game with 500,000 players. Exploratory testing and big external tests keep it stable.
Mental Health at Work: Breaking the Silence in IT Teams
Mental health at work starts with talking openly. Once one person breaks the silence, colleagues open up, and a bad day no longer gets misread.
Contract-Based Testing: Detecting Breaking Changes Early
Contract-based testing lets provider and consumer agree on a versioned contract. Breaking changes then surface in the CI pipeline before integration.
ISTQB: President Wants to Review Curricula Every Five Years
The ISTQB runs almost entirely on volunteers across 68 member boards. Its president wants every syllabus, CTFL 4.0 included, revised within five years.
Selenium Automation Testing: A Browser Tool First
In Selenium automation testing, Selenium only drives the browser. Good selectors, page objects and the vendor drivers in Selenium 4 keep tests stable.
Software Reviews: Finding Bugs Before They Become Costly
A software inspection finds errors early, before fixing them costs ten times more with each phase. Perspective-based reading helps, bosses don't.
AI Test Automation: Machine Learning Finds Root Causes
AI test automation turns 200 failed tests into seven real causes. Machine learning groups failures by root cause and frees testers to write new tests.