Related Content
 |
What to Do When Bugs Are Found—Based on When They Are Found When executing test modules, an interesting question to ask is “What needs to happen with issues that are found?” Hans Buwalda suggests making a distinction between issues found during a sprint and after the team has declared the functionality under test "done"—and describes how to proceed from there. |
|
 |
Test Automation Is Mandatory, Thanks to Agile Unlike waterfall, where people had to do their best to explain the value of automation, agile more naturally promotes that need for these tools through its rapidity and integration of testing throughout the development process. Agile assumes automation is the key ingredient of your mission strategy. |
|
 |
Why Is Estimating Software Testing Time So Difficult? Management loves to ask testers to estimate how long their efforts will take. But so many important factors elude measurement that it makes it difficult to predict. If you need to explain why estimation is so tough, here are nine factors that significantly influence our ability to estimate testing time. |
|
 |
Make Better Software by Learning from Your Mistakes If you accept that it’s OK to make the same mistakes over and over, you’ll never give yourself the opportunity to grow. If you don’t grow, you won’t improve your software. A writer should always ask why an editor did what he did, and a developer should understand how he can fix the code he broke. |
|
 |
To Deliver Value in Your IT Projects, Understand Context First Starting a project without understanding can lead to a mess from a usability perspective. Too often, we build what we can without taking the time to question whom we are building it for and why. A user story is a simple but effective tool to determine how much we understand about the context of a problem. |
|
 |
How Poor Testing and an Early Release Can Damage Your App and Business Mobile or PC apps that crash, have poor user experience, don’t run smoothly, or lack features give your customer the idea that whatever they bought didn’t get the tender, loving care it deserved—even if they know the issues can be fixed in a later release. |
|
 |
Before Jumping into Software Testing Tools, Get Your Code Straight Software testing tools can be incredibly helpful, but only if you're implementing them from a good starting place. If your code is a mess, a tool won't fix that; you'll end up simply adding layers on top of the mess. Matt Heusser explains how your team would be better off learning elements of code as craft. |
|
 |
The Importance of Just Enough Software Measurement and Metrics When it comes to the development, testing, and deployment of software, some argue that metrics have little value. Others take measurement to the extreme and have books of metrics, but without any meaning or action. Mike Sowers thinks metrics are vital, but it’s most beneficial to have just enough metrics. |
