Test Planning
Articles
 |
3 Types of Requirements for Testing Requirements for software are usually grouped into a bewildering array of categories. Functional and nonfunctional requirements are on top, and a huge number of subcategories are underneath. Here, Clint Hoagland boils it down to three categories, differentiated by the way they should be tested. |
|
 |
Lessons from Optimizing Computer Systems Applied to Human Teams Payson Hall learned some lessons from optimizing data system performance that could relate to human team management and leadership. For instance, if a system is overworked, it can't be any more productive beyond a certain point; the same is true for people. Both also can get more done by minimizing multitasking and prioritizing jobs. Read on to learn more from machines. |
|
 |
Exploring Together: Shared Understanding Through Paired Exploratory Testing As a ScrumMaster, Claire Moss is responsible for removing obstacles for her team. In this article, she describes her experience teaching everyone on the team—testers and non-testers—exploratory testing skills through pairing. |
|
 |
How a Software Tester Helps During Product Discovery A software tester can begin testing early—very early—before the software has even been built. Karen Johnson explains that one of the best times to start testing a product is in the product-discovery phase. |
|
 |
Fixing the Brittleness Problem with GUI Tests One common complaint about test automation is that it’s too brittle. Small changes in the system can cause lots of rework during the automated checks. In this article, Clint Hoagland shows a way to fix “the brittleness problem” by using the right abstractions in your automation design. |
|
 |
Helpful Tips When Implementing Test Automation Greg Paskal presents a list of helpful tips for when you are performing test automation. A smart plan for your automation endeavors will make a significant difference in its usefulness, adoption, and maintainability over the long haul. |
|
 |
Risk-Based Testing: Test Only What Matters Rajnish Mehta writes that test teams need to have a scientific way to support the business need of shipping a product out the door. Risk-based testing is a practical approach for test teams to utilize as it allows them to think from a business perspective. |
|
 |
Helpful Tips for Hiring Better Testers Isaac Howard describes how his experience in hiring staff taught him to interview better and recognize who are the best picks for a standout team of testers. According to Isaac, the best job candidates are driven to learn and capable of adapting to change, two traits crucial to testing. Remember, testing is learning and relearning software every day. |
|
 |
The Test Manager's Survival Guide to Going Agile Joel Bancroft-Connors presents a survival guide for testers going to agile. Joel explains what happened when he had to make the switch from waterfall to agile. Welcome to the world of being an agile manager, in which your team is a top performer, doing more in the same amount of time as before. |
|
 |
How Skeleton Strings Can Help Your Testing Brian Noggle writes about how he uses "skeleton strings" to help him when he probes an application under test. Just as skeleton keys unlock doors, these generic skeleton strings open up access to a wide variety of defects. |
Pages
Recommended Web Seminars
| May 23 | How Generative AI Boosts Speed and Quality in Software Testing |
| On Demand | Building Confidence in Your Automation |
| On Demand | Leveraging Open Source Tools for DevSecOps |
| On Demand | Five Reasons Why Agile Isn't Working |
| On Demand | Building a Stellar Team |
Featured Resources
Visit Our Other Communities
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.