Related Content
 |
How to Build Credibility as a Tester Respect is a major player when it comes to creating and maintaining a cohesive team, and plenty of testers today feel they’re lacking the respect of their peers. With test automation sometimes being seen as some magical solution to fixing bugs, the usefulness of manual testers has come into question. |
|
 |
Is Our Innovation in Software Testing Keeping Up with Technology? The world of software testing has made many important advances in techniques and approaches, but is it keeping up with the leaps and bounds of technology's progress? Mike Sowers is an advocate for a revolutionary breakthrough in software testing, and to get there, we all need to become innovators. Here's how. |
|
 |
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. |
|
 |
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. |
