Test Planning

Articles

Designing Scenarios for Agile Stories Designing Scenarios for Agile Stories

The needs to improve the time to market of a quality product and adapt to a changing business environment are driving organizations to adopt agile practices in order to be competitive in the marketplace. However, a project team is bound to face difficulties if it is not trained on the fundamentals of agile. Read on to learn how to design scenarios for agile stories using a structured framework.

Sharath Bhat's picture Sharath Bhat
Testing at the Super Bowl Testing at the Super Bowl

The single largest retail event in the United States in 2014 may just be the Super Bowl. Selling those products—everything from hats to jerseys and foam fingers, too—means shipping logistics, websites, and, yes, a lot of software. In this article, Lisa Crispin and Lanette Creamer discuss how that software is tested; you might be shocked at what they found.

Lisa Crispin's picture Lisa Crispin Lanette Creamer
Why Testers Need to Get Used to Change Why Testers Need to Get Used to Change

Jeremy Carey-Dressler describes how changes in technology, like the growth of mobile devices over personal computing, has altered the traditional roles of testers and their methods. As the market creates winners and losers, things will settle down some and it will become slightly easier to have common test techniques. For now, testers must get used to change.

Jeremy Carey-Dressler's picture Jeremy Carey-Dressler
Have You Used Word’s "Smell-Check" Features? Have You Used Word’s "Smell-Check" Features?

Terry Wiegmann writes about how Microsoft Word's features, like its spelling and grammar checkers, can help one identify agile smells—those signs that something might be wrong. While we may want to minimize documentation and the use of Word, we can mentally use some of Word’s features to sniff out some whiffs of smells.

Terry Wiegmann's picture Terry Wiegmann
Measuring End-User Performance Consider Rendering Times While Measuring End-User Performance

Mukesh Sharma writes that if you want to build an effective performance test strategy involving smart devices, you need to consider rendering times. It’s no longer OK to simply measure the response times on desktop web applications like we did in the past. For mobile, the rendering time can make all the difference between a good and a bad user experience.  

Mukesh Sharma's picture Mukesh Sharma
Quantifying Your Value with Test Metrics Are You Quantifying Your Value with Test Metrics?

On a fairly regular basis, test and QA management have to explain their value and role to their clients. Sanjay Zalavadia writes that in these situations you must choose metrics that provide insight into what you are doing instead of obscuring it. This will help tell your story in a compelling way.

Sanjay Zalavadia's picture Sanjay Zalavadia
The Bugs That Deceived Me The Bugs That Deceived Me

Every time we look at the data, we perform an analysis that helps us make decisions—hopefully the right ones. In this article, Gil Zilberfeld describes a few traps where bug data misled him to make bad decisions. These traps are in the data itself, not the tools, and can lead us in the wrong direction.

Gil Zilberfeld's picture Gil Zilberfeld
2013: A Year of Software Development and Testing in Quotes

In this roundup of noteworthy quotes from industry experts interviewed in 2013, read about what constitutes effective agile methods, the year in testing techniques, and why you shouldn't put too much trust in the latest and greatest tools.

Jonathan Vanian's picture Jonathan Vanian
Don't Ignore the Smoke Tests Don't Ignore the Smoke Tests

Justin Rohrman writes about the benefits of smoke tests. These tests can be simple and concise, and because of that, low cost. Spending a few minutes of your time watching the smoke test run can be a fantastic way to defocus and notice some things about your product that may normally go unnoticed.

Justin Rohrman's picture Justin Rohrman
Automate, and Add Value Testing Services: Isolate, Automate, and Add Value

Understanding what’s going on “behind the scenes” provides us both insights into test design and details on failure, which makes our work more valuable. Testers, who are likely already the subject-matter experts on their applications from a business perspective, become much more powerful assets for their teams when their level of technical knowledge of their application increases through the process of service testing. This is a win-win-win for the tester, the test team, and the project team.

Don Prather's picture Don Prather

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.