Thank you for taking the time to have a quick read about who we are and what we’re up to. Hopefully the following post gives you a bit of an understanding of why we started Codified Testing and what we’re trying to achieve.
We’ve been building and launching mobile apps for over 10 years. In that time we’ve worked for governments, fashion brands, entertainment companies, educational organizations, multinationals and start-ups. Every project and client had one thing in common: pain points in the development process thrown up by annoying frontend bugs. These types of issues normally crop up at the end of a build and get put into the “just about 5% left to do” bucket. They always turn out to take twice as long to find and fix than expected. Because building new products for mobile is hard, these frontend bugs are left till last as fixing them is deprioritized.
Over time, mobile QA testing became our biggest frustration.
- Finding and fixing these issues takes up valuable engineering time. That time is expensive and should be utilised somewhere else on bigger harder problems.
- Working with outsourced testing agencies is costly. It also eats up more time and money. It’s not scalable and it's hard to find a reliable partner in this space.
- There is simply no way to find all these frontend bugs easily. It’s a manual endeavour prone to human error.
Tracking and managing this process is a headache and we wanted to find the painkiller. Which is why we have created Codified Testing. We help development teams to implement automated frontend QA testing into their development lifecycle. This means that you don’t have to worry about finding errors with each new release. Our code does it for you.
We’re passionate about this. It’s changed how we work and we want to help others to change to. In the next post, we’re going to deep dive into some more of the actual tech behind what we do but in the meantime please feel free to reach out to us with any specific questions you might have.
Thanks for reading,