Preach what you practice

Turning caffeine into code and bugs into features. Join us as we code, create, and innovate - one line at a time!

Maestro in practice: one UI suite for Android and iOS, owned by QA

Maestro is an open-source UI automation tool. You write a user journey as a short YAML file and it drives the app on a phone or in a browser the way a person would. Over the past couple of months we used it to build the UI regression suite for a mobile app that ships on Android and iOS, and for its web admin. This post covers what we built, how we structured it so that a QA engineer can own it, the two properties of the tool we had to design around, and where we decided a UI test is the wrong instrument.

The best bug I ever found was one I never got to report

Shift left is not about testing unfinished work or moving QA to the front of a process. It is about bringing QA into the conversations where requirements, risks and edge cases are decided, so problems can be addressed while they are still cheap to change. This article looks at how earlier QA involvement changes the role of testing, why bug counts can be a misleading measure, and why tools alone cannot create a shift-left culture.

AI in QA: partnership or rivalry

Artificial intelligence is reshaping quality assurance by automating repetitive tasks and helping teams deliver software faster than ever before. While some people worry that AI will take over QA jobs, I see it as a powerful partner that enhances our productivity and efficiency. The real question is whether AI should be seen as a rival or a partner, and why human creativity remains irreplaceable in the testing process. The future of QA isn't about robots replacing us, it’s about humans and AI working together.

AI for QA: keeping your product private

Working across different QA projects has taught me that a useful tool is not always the tool with the most access. AI can speed up test case writing, API test preparation and automation drafting, but it does not need to connect directly to the product, repository or private environment. I used AI with controlled inputs such as feature flow videos, HAR files, screenshots and repo structure examples. That gave me useful output while keeping the application, sensitive data and VPN-protected environment private.

Android TV QA beyond playback and remote control

Testing Android TV apps is often described through remote control navigation, streaming playback and big-screen UI. My experience is slightly different. I work on Android TV apps used in a commercial environment, where the TV is not something a user actively controls every day. It is expected to run reliably, display scheduled content, recover from problems and report what happened. That changed my QA focus from simple screen validation to long-running playback, provisioning flows, kiosk behavior, logs, schedules and device stability.

Want to see our projects?

Built by Ignit.

EXPLORE WORK