test automation

Hans Buwalda describes five of what he refers to as misconceptions about test automation.

A product that doesn't do what it's supposed to do, security flaws, issues that devalue the user experience—for all of these reasons and more—establishing an efficient test management strategy is an essential step in creating great software. Herein lies the value of building an API regression suite.

Automating functional testing is almost never easy. As testers, how we organize and design tests has a big impact on outcomes, but developers can—and should—have a role in making automation easier. This ease or lack of ease is part of what is known as "testability."

Some form of automation should be used to streamline testing, but leveraging automation as a crutch won’t help you or your team spot every bug and produce high-quality software. In automation, the tools don’t do all the testing—they simply do what they are told to do by the actual tester.

Automation integration is a huge value to QA teams, but not everything can or should be automated. By understanding the difference, teams will be able to utilize their tools more effectively and streamline operations for better results. Sanjay Zalavadia looks at when and when not to automate.

There’s no single solution that can guarantee success in the mobile testing space. However, by incorporating virtualization and making use of the cloud, you can test the functionality, performance, and security of an application across a bevy of networks.