Lukasz Fryc

At Status.im, I worked as part of the core development team that ensure the high quality of Status mobile app.

During my time there, we had noticed that with new releases, the app had started to consume more and more battery and bandwidth. It became necessary to improve upon it as it directly impacted our users.

To measure the battery and network consumption, I created a set of automated tests using Appium, Android ADB, and Docker stack. The Dockerized Appium tests ran on real devices and saved the results in InfluxDB that was then used by the Grafana dashboard. The tests were then used to compare the efficiency of nightly builds.

How do you maintain and keep scaling a large set of end-to-end UI tests?

Being an old hand with test automation and front-end apps, I took on the lead role in improving the end-end test framework at Base. I refactored the code using Page Objects and Screenplay patterns as well as created multiple developer-friendly tools to simplify the process of creating new tests and debugging failures.

One of my roles at Base (now Zendesk) was designing and implementing complex API tests to verify interactions between multiple REST microservices the system had. The test automation framework I used was developed in Ruby and RSpec.

Many of our clients at Testmunk had hybrid mobile apps with the same UI across all platforms (Android, iOS) so I created a cross-platform test framework that allowed us to run identical UI acceptance tests on all the platforms using the same test code; it was written in Cucumber and used the Page Objects pattern. The only thing that was different for each platform was the set of UI selectors that were extracted from the test code.

Sharing my knowledge and experience is really important to me so I have recently started posting on Quora and in a relatively short amount of time, have become the most viewed writer for QA topics.

In the near future, I plan to write more about successful test automation solutions so make sure to follow me.