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 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. |
||
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. |
||
Why Is Estimating Software Testing Time So Difficult? Management loves to ask testers to estimate how long their efforts will take. But so many important factors elude measurement that it makes it difficult to predict. If you need to explain why estimation is so tough, here are nine factors that significantly influence our ability to estimate testing time. |
||
Before Jumping into Software Testing Tools, Get Your Code Straight Software testing tools can be incredibly helpful, but only if you're implementing them from a good starting place. If your code is a mess, a tool won't fix that; you'll end up simply adding layers on top of the mess. Matt Heusser explains how your team would be better off learning elements of code as craft. |
||
Automation Friendly Test Design—An Example A major contributor to success in test automation is test design. If tests have many unnecessary detailed steps and checks, even a skilled automation engineer will not be able to make the automation efficient and maintainable. Hans Buwalda shares an example of a test design that is automation friendly. |