Over the years, I’ve heard many, many software testers insist their management expected them to “automate everything.” In some ways it seems perfectly reasonable. But does this approach to test automation make sense? Can we do better?

Automated UI testing is one of the biggest investments companies make as part of the testing process. The investment pays off, though, because these tests are easier to create for both technical and nontechnical testers, as various tools can aid in the process. Here are five prac...

Identify and correct problems sooner, rather than later: That’s the heart of the “shift left” slogan. But to do so with security — to cultivate not just DevOps, but DevSecOps — is one of application development’s thornier problems.

We can validate whether a product is working as expected, but testing has to stop at some point so the product can be released. Here are six questions to help decide that it’s time to stop testing.

At some point, your organization’s testing process may need an overhaul. This may seem daunting, but there’s no need to reinvent the wheel.

With the current focus on DevOps and Continuous Testing, test automation has become increasingly important. What does that mean for manual testers? How can they prepare for the future?

Finding defects early in the software development process is key to saving cost, time, and effort. This being said, it is important for developers to test their features before pushing it to QA.

High-quality projects need to deliberately practice failing tests, to help ensure successful tests are truly meaningful. Four examples help show how this idea embodies basic principles of Test-Driven Development.

One of the most highly debated topics in software testing is the decision between open source and vendor-based solutions for test automation.