Related Content
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. |
||
Worried You Might Mumble? Here’s How to Speak Clearly Feeling nervous, being afraid of saying the wrong thing, or just talking too quickly are some of the main reasons people mumble when they speak. Often, however, people don't even realize they're mumblers. If you think you may be one, read on to learn how to speak confidently and—of course—clearly. |
||
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. |
||
Avoid Embarrassing Glitches: Proofread Your Documents To avoid embarrassing errors in your emails, documents, and proposals, it's a good idea to proofread. But simply glancing over what you wrote isn't enough. Naomi Karten gives some tips for thorough proofreading, such as coming back to your document later, printing it out, and reading it out loud. |
||
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. |