🧪 Why We Failed at Testability (and What We Learned!) 😱

Back in 2018, we thought we had nailed testability and automated testing. We transitioned from manual regression testing and drastically reduced our reliance on automated UI tests. 🙌

As a team, we built testability into our codebase, giving us real-time insights into changes in behaviour allowing us to quickly adapt, release, or dive deeper with exploratory testing. It felt like we were winning! 🎉

But by 2020, things had shifted. Our automated testing had stopped, and the team had reverted back to manual regression testing. 😔 What happened?

Here’s what I learned: The issue wasn’t technical. Implementing testability was actually the easy part. The challenge was working as a team to embrace testability, which needed a whole new way of working — and that’s where Leadership comes in.

💡 Leadership was the key to making testability successful. Want to know what leadership behaviours made the difference?

🧠 Creating psychological safety,

⚠️ Learning from failure,

👯 Working across discipline boundaries and

🖼️ Positively framing the work

📢 Check out this week’s post which dives into each behaviour and how to foster them in your teams is Quality Engineering Newsletter: