Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
Have you ever met a widely known Selenium issue that drag and drop gesture doesn’t work for Selenium in some cases? This bug has been around for years and Dmitrii Bormotov will tell you how to resolve it, especially in just a few lines of code if you use Python.
PractiTest has released its eighth annual State of Testing© report containing insights from software testing professionals from around the world. This document confirms the growth of test automation and that software testers are working more and more outside their traditional QA silo.
One of the question that is often spotted on software testing forums is “How can I get a job as a software tester if I have no experience?” In this article, Mirza Sisic shares with us some tips on how he managed to achieve his goal of starting a software testing career.
Hardware-as-a-service (HaaS) allow using distinct hardware components through the Internet analogously to the cloud services. This article discusses the differences of the testing approaches that could be used to test hardware compared to software.
Welcome to this Cerberus Testing step-by-step tutorial for testing mobile applications. This guide will help you understand the test automation workflow and good practices supported by Cerberus Testing to test mobile apps using Appium.
Exhaustive testing is a type of software testing approach where all the behaviors of a system are explored during the tests. If this approach is good in theory, it is not feasible in most testing contexts where time and resources are limited. This article presents the distinguishing characteristics of exhaustive testing and explain how to perform it.
The Fuzzing Book is a website / online book that presents tools and techniques for generating software tests. Fuzzing is defined by Wikipedia as “automated software testing technique that involves providing invalid, unexpected, or random data as inputs to a computer program. The program is then monitored for exceptions such as crashes, failing built-in code assertions, or potential memory leaks.”
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates