One of the ways to prevent bugs from escaping into the wild and affecting customer experience is using test automation. The earlier the bug is caught, the less expensive it is to resolve. It comes as no surprise that many companies have a long history of test automation. They also try to maintain a healthy Test Pyramid. However, as software projects grow, often the shape of the Test Pyramid can become quite the reverse of that intended and, in fact, a poorly maintainable Ice-Cream Cone. There's another shape Test Pyramid can take - an Hourglass. This is the current structure of our iOS tests and something we are actively improving. I'll be talking about the steps we take to fix this. I'll also unveil some of the peculiarities of the iOS Test Pyramid we have in Bumble. One of the projects we currently have is to return iOS Test Pyramid in shape, so I'll explain how it's organised and how we involve multiple teams in it.