|
Speaking to Your Business Using Measurements Justin Rohrman writes that measurement is one of the biggest problems he's experienced in test management. How do we measure quality, how do we know those measurements are good, and how do we use them to tell a story to executives? In this article, Justin explains how to speak to your business using measurements.
|
|
|
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.
|
|
|
Using Containers for Continuous Deployment Pini Reznik explains how containers can help shorten the software development feedback loop by drastically reducing the overhead involved in deploying new software environments. This leads to faster build and test executions and simplifies the standardization of the development and production environments, allowing for an easier transition to continuous deployment.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|