Related Content
 |
The Value of Testing Simply People obsess over the number of tests and test coverage, but tests that cover more code don’t always improve quality. Some tests have low value and thus, implicitly, high cost. Simple tests may not seem impressive at first glance. But the goal of testing is to ensure quality, and simple tests can be very valuable. |
|
 |
Agile Testers Shouldn’t Be Enablers Testing has often been seen as the final stage of creating an application. Since we weren’t shifting testing left as much as we do today, a great deal of work was thrown on the testing team at the very end of an exhausting project cycle. But testers shouldn’t be seen as the last line of defense. |
|
 |
The Importance of Testing in Conjunction While it is important to have distinction between testing efforts to maintain specialization and core subject matter expertise, having overlap in test efforts—testing in conjunction—is becoming a common practice. |
|
 |
Build the Right Things and Build Them Fast: Accelerate the Continuous Delivery Pipeline When most people think about continuous delivery, they think of improving the build-test-deploy-operate cycle. They don’t think about how to improve the intake process. Ensuring that quality is built into the application—not tested for after the fact—is the key to achieving accelerated continuous delivery. |
|
 |
Why Testers and Developers Don’t Have to Be on the Same Page Since software development is highly subjective in nature, different thought processes and assumptions between development and testing teams can positively impact applications and lead to a more successful, well-rounded product. It might not seem like it at the time, but there’s value to dissonance. |
|
 |
Where to Begin with Test Automation Most test teams want to try automation for some tasks in order to be more efficient, but it can be daunting. If you are wondering where to start automating, the answer is usually as close to the code as you can possibly get. The farther you get from the code, the more you expose yourself to issues. |
|
 |
Reviving the Master Test Plan in the Age of Agile In the competitive environment of delivering software more quickly, many teams have abandoned detailed test plans. Michael Sowers argues for bringing back the overarching master test plan—not to have more documentation, but for the questions, creative test designs, and critical thinking the planning brings. |
|
 |
When User Acceptance Testing Isn’t User acceptance testing is a great way to find issues that will matter to your customers before you release your product—but that's only if you're performing it correctly. Are you aware of what user acceptance testing entails (and what it doesn't)? Are you sure your team is clear on these goals, too? |
