Related Content
 |
The Merits of a Collaborative Manual and Automation Test Team In many organizations, the manual and automated test teams are separate. But the most successful test teams integrate manual and automation resources into a single, cohesive team. This allows them to fill in any gaps in the test case steps and to develop a more informed automation strategy. |
|
 |
Bringing the Value of Your Test Automation Efforts Front and Center Once you’ve adopted test automation, you should determine whether it’s actually yielding the expected benefits—and you’ll want to keep these benefits visible to stakeholders to reinforce the value. A metrics dashboard aligned with the organization goals and business objectives shows you're on the right track. |
|
 |
You Can’t Compete without a Solid Automation Strategy The speed at which software evolves, adapts, and moves to the next best thing can be dizzying at times. As soon as you adopt the latest and greatest methodology and see better results, a new solution is created that somehow requires teams to better test and develop at a greater rate. |
|
 |
Just Enough Testing at Each Stage of Your Delivery Pipeline The continuous delivery pipeline should determine whether the software is a viable candidate for production. Having frequent quality gates along that pipeline that give frequent feedback about the quality of the software helps us find that answer faster. Short feedback loops ensure better product quality. |
|
 |
Developing and Testing IoT and Embedded Systems: Questions to Ask Self-driving cars are the new big thing, and the operational and environment scenarios these vehicles will encounter are practically infinite. How we should develop and test these systems is a big question, and there are no easy answers. But Jon Hagar has some ideas about where to start. |
|
 |
Removing the Performance Testing Bottleneck When you start down the road to continuous testing, even if you increase speed, performance tests can still hold up production deployments. By using application monitoring, service virtualization, and open source performance testing tools, performance testing is accounted for in every cycle of development. |
|
 |
Are We Sacrificing Quality for the Sake of Speed? Are we reducing the quality of our code by pushing teams to produce at a speed that might be too fast? Will the final product require multiple updates in order to fix bugs missed along the way? Like just about every question posed about agile, it can depend on the specific team makeup. |
|
 |
Staying Competitive in Software Testing In today’s global economy, staying competitive may be more important than ever. Three ways to contend are by focusing on price, niche (addressing a particular group’s needs), or differentiation (doing things better in some way). Which tactic you choose could make all the difference for your software team. |
