Related Content
 |
Building a Business Case for Automation in Your Software Lifecycle To remain competitive, organizations should consider implementing a well-integrated set of automation capabilities—not just for testing, but across the entire lifecycle. Making the investment might take some convincing, so here are some questions to ask in order to assess the potential benefits of automation. |
|
 |
The Importance of an Integrated Test Automation Plan Adopting automation tools can be a big decision. When it comes to test automation, it’s critical to incorporate an integrated test automation plan instead of piling together a mishmash of unrelated tools with the hope to create some taped together mess of a plan. |
|
 |
The Test Automation Design Paradox Testing and automation have various paradoxes that are interesting to look at for insight into the challenges and limitations of our profession. Hans Buwalda describes these paradoxes and offers methods to bring about cooperation in teams, helping them achieve great automation results together. |
|
 |
Contemplating What Constitutes an Organizational Crisis It can be hard to envision what would constitute a crisis for your organization until you’re facing one. But defining what events could be disastrous for your company is the first step toward planning for them—and having an emergency plan could be the difference that helps you respond in time. |
|
 |
3 Steps to Nurture IoT Development and Testing As more devices connect to the Internet and engage in machine-to-machine communication, QA management must cultivate an understanding of the IoT and how to create software for these connected items. Sanjay Zalavadia describes three steps to nurture IoT development and testing. |
|
 |
How Test Automation Can Help Your Business Test automation is much more than just the specific tools, frameworks, or programming languages that allow it to improve the overall quality of your software. You need to go a level above the technical terminology to understand the value of test automation. |
|
 |
Scaling Product Agility: More Product, Not More Process Focusing on scaling product discovery that feeds product delivery is valuable to scaling frameworks. A cross-team product discovery cadence highlights work that's valuable to everyone and facilitates workflow for all the teams, helping them produce more of what they really need (and less of what they don’t). |
|
 |
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. |
