Fewer UI Tests, Fewer Problems

Now, which failed, which passed?

A question we often ask ourselves when running commits through our Jenkins pipeline. While we love that we have automated our testing and deployment workflow, we’re frustrated that our pipeline isn’t perfect! One of the challenges we face is, since we run our UI Tests on real devices, there are a slew of issues that cause that stage to fail unpredictably. As we refactor and add new code, we always try to eliminate UI Tests by converting them to Unit or Unit Integration Tests. We’ve found that we can achieve higher confidence in our code and our pipeline this way. This song will take you through our journey of removing the flakiness from our automated tests. Please enjoy Fewer UI Tests, Fewer Problems!

0 Shares:
You May Also Like