Testing ad integrations is quite a tedious process. Since we work with third-party SDKs that can hardly be controlled, it can be challenging to automate the testing process. Nevertheless, to reduce testing time, we have developed and implemented a debug panel, which we will discuss in this article.

Founded on years of work experience in testing

There is a tremendous variety of QA Engineer vacancies, ranging from junior to lead tester and even to principal QA Engineer. We’re often asked what qualities a senior-level tester should have compared to junior or middle-level ones. Let’s try to answer this.

Over the past 4 years, we’ve developed an adaptation process enjoyed even by ultra-experienced newcomers. Today, we’ll share its main stages and a basic checklist. You can easily adjust them to fit engineers of any level that you hire.

As your application grows, so does the flow of tasks for QA. And if you don’t reduce that amount of work in time, it will begin to threaten your releases. And just resemble a sprawling bush that’s not being looked after. I will tell you how we reduced the regression testing time from 5 to 3 days in a couple of months maintaining quality and relieving the level of stress for the QA team.

Since most of our users are from the USA, FunCorp decided to update its icon and splash screen for the Halloween holidays last year. Let’s recall that story. The task seemed trivial, but in the process, we found some more cases and grew our essential checklist from 8 to 13 items (attached).

If you want to build an efficient UI auto-testing process for your project, it’s essential to first consider how testable your application is generally, as well as how you can write effective UI tests.