Systems | Development | Analytics | API | Testing

November 2022

Happy birthday, Testlio

On a gloomy Friday evening ten years ago, two young Estonian entrepreneurs with a dream sat in a dimly lit flat in London, trying to come up with a name for their future company that would improve the way software testing is done. The AngelHack hackathon was starting the next day and the couple was planning to to pitch their idea there. A bit before midnight, the goal of choosing the company name was reached - Testlio was officially registered and our founders Kristel and Marko Kruustük were ready to take on one of the biggest and rewarding journeys of their life - creating a globally distributed company that powers networked testing to enable human possibilities.

How will test automation shape the future of QA?

Like many tech endeavors, QA has undergone radical evolution over the past decade, and to keep up with the competition, dev teams are looking toward the future of QA. Now, perhaps more than ever, consumers hold a critically high bar for their web and mobile apps. This means, of course, continued investment in efficient, high-quality testing to stay competitive. But what about the A word?

Five test automation challenges and how to overcome them

Automation is critical for a holistic software testing strategy in today’s DevOps cycle. Efficient automated QA systems run by talented engineers can shorten development times, improve time to release, lower costs, and drive scale. It’s worth noting that nearly a quarter of companies that initiated automated software testing showed an ROI within the first six months. Sounds perfect, right?

Which software testing staffing model is right for you?

If you are reading this, you have likely already identified a high-level need to scale or improve your current approach to testing without the mass hiring of in-house testers, or shifting left to make devs fully responsible for QA. Partnering with a software testing company is a great start, but what if a vendor offers multiple models? How can you define which software testing staffing model is right for you?