Tutorials and resources on how to apply test automation in software testing
Code generation with AI tools is rapidly expanding in the software development world. The software testing and QA activities are also impacted by this trend. What does it mean for suppliers of test automation tools? In this article, Maz Daly explains how they should transition from turnkey solutions to providing a platform that allows customers to build their own software testing platform with confidence and scale.
A privacy product tells a user that her personal data has been removed from data broker sites. Every test in the suite passed. Was the data removed? Most test suites cannot answer that question, and this article explains why, and what to do about it.
AI-assisted code generation has changed the capabilities of organizations to produce code. In this article, Hélder Ferreira discusses the impact on software quality created by this new situation. The main problem is that this new code is often created by tools that lack the knowledge of the global context of both the application infrastructure and the process being automated.
Today, you can find tools that generate code and AI-assisted test automation tools that will handle the quality assurance part. Is it the death of traditional manual testing? In this article, Rimpal Mistry reminds us that human validation is still needed to provide the final check of delivered software.
Confluence can store QA docs, but it seldom helps testers find the right one when release pressure hits. The problem is rarely the editor. It is that test plans, environment runbooks, and release checklists drift out of date faster than anyone updates them, and a wiki that merely holds pages cannot tell you which ones still reflect reality.
When today’s applications run on various browsers (Chrome, Firefox, Safari, Edge, etc.) on different mobile or desktop devices with specific screen settings. This is why you need to perform cross-browser testing for your automated tests. This article lists the main desktop or online cross-browser testing tools available today.
In this article, Mikhail Golikov, the sole QA on a seven-team backend e-commerce platform, explains where each regression check belongs, in the browser or at the API. He shares the rule he actually uses, two bugs that only one layer could have caught, and the realization that finally made his browser suite small and stable.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates