Related Content
 |
Five Misconceptions about Test Automation Hans Buwalda describes five of what he refers to as misconceptions about test automation. |
|
 |
Validate Your Core Business Assumptions Early On Verifying whether a product is being built per specifications is only solving half of the problem. Validation is a very significant activity performed by testers to ensure that the final product is ready for consumption by users and answers an important question. Are we building the right product? |
|
 |
Look to Corporate Standards to Guide Your Organization In large organizations with distributed teams, departments can have their own procedures, acting as if they are in completely isolated silos. One approach to solving this issue is establishing corporate standards. Tap the models of widely used standards to create practical guidance for your own organization. |
|
 |
To Test APIs Effectively—Build an API Regression Suite 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. |
|
 |
Why Your Test Efforts Should Tackle Data First Automation projects often start by tackling the technical issues, but Linda Hayes says a specific data environment should be established first. If you can’t control, define, and predict your data, you won’t have the repeatability that makes test automation practical—but it makes sense for manual testing, too. |
|
 |
Improving Application Testability 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." |
|
 |
Automate for Efficiency: How Test Automation Does More than Spot Bugs 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. |
|
 |
When and When Not to Automate 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. |
