Related Content
 |
How to Choose the Right Test Cases to Maximize Efficiency For test teams, throwing every test case in the book at a project isn't practical or necessary. By understanding test design techniques and what to look for in a good test case, teams can choose the ones right for their requirements and improve their testing efficiency. |
|
 |
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. |
|
 |
3 Ways to Foster Enthusiasm in a Software Team Enthusiasm can’t be forced on you. If you’re not passionate about software, it’s difficult for someone to get you to the point where you wake up in the morning excited to develop a mobile application. However, the conditions of your software team can change your level of enthusiasm drastically. |
|
 |
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? |
|
 |
When You Can’t Manually Test All Possibilities, Turn to AI and Automation With Niantic Software’s Pokémon Go, the variables you’re dealing with are eons beyond what a normal testing team can manage. Millions upon millions of players are experiencing the application all over the world and putting it through paces that the development team might have never dreamed of. |
|
 |
A Case for UI Automation in Software Testing When testers talk about automation projects, especially in the user interface, they describe cautionary tales and the million ways these projects can fail expectations. However, there are contexts where automating the user interface works well and, more importantly, helps the development team. |
|
 |
Reasons to Consider Software Tests as Products Software tests have to meet quality and robustness criteria that are similar to the application under test, but tests seldom get the attention and investments that the applications get. Hans Buwalda outlines why you should consider tests as products. |
|
 |
Legacy Code Can Hinder Your Agile Transition Although there's a lot of practice evolution that happens with agile transitions, legacy code can still be a major obstacle to agile success. A few risks and considerations emerge when scaling agile while still managing legacy code barriers. |
