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.
Podcast: Software Testing, AI and Quality Insights : Page 16 of 16
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.
BDD Testing: Given-When-Then for Business and Developers
BDD testing uses Given-When-Then scenarios so business stakeholders and developers share one understanding of a feature before any code is written.
Agile Quality Assurance: Talking Comes Before Coding
Agile quality assurance starts in the conversation about requirements, long before acceptance testing. Leaving tests out is fine if the risk is known.
Whole-Team Quality: The Three Factors Good Teams Share
Quality as an attitude makes quality the whole team's job. Good test cases, static analysis as a hard gate and test automation back it up.