Why do UI test automation projects often fail? With many automated test frameworks, getting started with your first few tests is the easy part. Building a sustainable, flexible test suite that gives you valuable data on the quality of your applications can be daunting to say the least.
I’ve witnessed dozens of UI test automation projects over the years, that make the same critical mistakes time and time again. I’ll walk through them and provide some practical steps that can help you avoid these pitfalls. Continue reading “5 Common Pitfalls of UI Test Automation”
This is a talk I did for the SWmobile group with Kevin West back in February 2016. The practical advice from the talk is covered in 5 Common Pitfalls of UI Test Automation.
Why do UI Automation projects often fail? With many automated test frameworks, getting started with your first few tests is the easy part. Building a sustainable, flexible test suite that gives you valuable data on the quality of your applications can be daunting to say the least.
Let us take you from those first few tests to an end-to-end BDD process that has become part of our everyday work. Discover how having rejected the idea of a dedicated QA team, the core development team take responsibility for quality and invest in a process that delivers value for them.
Learn how Test Cloud solves many of the issues that typically derail automation projects, how to handle ongoing maintenance, how to maximise test reuse between platforms and how adopting the Page Object pattern can help build test cases that can handle even a complete UI redesign with ease.
Having adopted Continuous Integration to build applications multiple times a day, it can be a struggle to find a testing strategy that gives teams the confidence to move to Continuous Delivery. Typically they start out with the aim of automating all tests, but this can be an unrealistic and unhelpful goal.
For a complex application, it is unlikely that automating all test cases for every build is the most effective approach. A risk-based mindset for your regression testing can help you to decide which gaps in your testing – if any – are acceptable.
Continue reading “From CI to CD with Risk-Based Regression Testing”
Zero Defect Culture is a term I came up with just over a year ago to describe an approach that focuses on keeping your in-development defects at or around zero.
It can be applied to any team developing a software application in phased iterations to help minimise disruption created during feedback cycles between releases.
Continue reading “Establishing a Zero Defect Culture”
Have you given your development processes the thought they deserve? Do you consider the benefits of different approaches in different contexts? Do you question whether established practices are right for you and your team?
It seems obvious to say that we need to separate our tools from how we choose to use them. Or that ‘best practice’ varies depending on your particular situation. Yet it is common to see teams fall into process by default.
Continue reading “Process By Default”
Have you ever had trouble convincing your colleagues to adopt a new technology, agree to a change in process, or modify ways of working?
It may be worth considering whether your proposal would be more successful when reframed as an experiment.
Continue reading “Continuous Improvement Through Experimentation”