Related Content
 |
Tools Need Testers: Why Automation Isn't Automatic Test automation isn’t quite as automatic as its name suggests. There’s a misconception out there that you can buy a bunch of test automation tools, set them up properly, and walk away without a second thought or worry. However, it’s important to understand that automation is a skill in itself. |
|
 |
The Top 5 Test Automation Mistakes Test automation is a valuable process, but it can be difficult to integrate into your existing test strategy. Melissa Tondi talked to hundreds of people about the biggest mistakes they’ve made when automating. Here are five of the most popular answers—and advice on how we can stop repeating these mistakes. |
|
 |
Why User Interface Test Automation Is Worth Doing Well It can be hard to produce reliable, stable UI tests. But these tests come the closest to simulating the actions of a real user, and they help ensure that your product works as a cohesive system. Consequently, UI test automation is worth doing, and worth doing well—with the same standards as any other tests. |
|
 |
Is the "Traditional Tester" Just a Myth? When discussing agile and its impact on the industry, the concept of the “traditional testing role” is often a topic of conversation. However, we shouldn’t just assume that this “traditional” tester is as common as we seem to make it sound, as testers have always had to do more than just test. |
|
 |
Five Misconceptions about Test Automation Hans Buwalda describes five of what he refers to as misconceptions about test automation. |
|
 |
Where Do Software Bugs Come From? There's much more to bugs than either a programmer screwed up or there are missing or misunderstood requirements. Many more possibilities could be responsible. A good tester warns that these areas are unknown; a great tester might even test for them. Look over your bug trackers and see what you can learn. |
|
 |
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. |
|
 |
Creating a Test Strategy and Design for Testing Data These days, data comes from multiple sources, is transformed in many different ways, and is consumed by hundreds of other systems, so we must validate more data, more quickly. Mike Sowers shares his work in progress checklist for things to consider when developing a test strategy and design approach for data. |
