Related Content
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. |
||
How Continuous Integration Can Save Your Team Substantial Time and Effort Continuous integration is all about the feedback loops between your developers, testers, product owners, customers, and everyone involved in your organization. That’s great to write as if it’s gospel, but what can continuous integration and continuous testing do for you right now to improve efficiency? |
||
Container-Based Deployments and the Future of IT Operations Container-based deployments have become the preferred approach for managing the build and release of complex applications. Many of the tasks handled by IT operations today may not be necessary in the world of containers. Will Ops continue in its current role, or will it need to evolve with the new challenges? |
||
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. |
||
The Essential Role of QA in Digital Transformation Many organizations are undertaking a total digital transformation in order to accelerate processes, innovations, and opportunities. But if you think you can update your development efforts without making a change to your QA program as well, your change will not be successful. QA is essential to reliability. |
||
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. |