Appium proves to hold a lot of value in the effort of achieving mobile application automation. Appium allows more granular control in automation efforts compared to scriptless automation. Though, to programmatically code text and visual assertions in appium scripts can be tedious and time-consuming, along with yielding not-so-ideal script bloat that can be difficult to maintain as an application changes from release to release. By applying an AI-driven engine on top of appium automation and providing a baseline session, AI can return text and visual discrepancies far faster than the original, programmatic attempt with less effort and maintenance. This allows quality engineers to not only catch more defects within their automation, but also allow them to automate additional tests quicker while still gaining the advantages of appium automation.

It is common yet quite new to hear the term ‘Observability’. But what does that mean?

Is it just another new acronym for monitoring? 

In the current era, organizations are building applications with more complex architectures such as - blockchain, distributed systems, and microservices. The job of maintaining these systems and ensuring it is working as expected has become a challenging task. Gone are the days where testers have to rely on the UI’s to validate an application. Now it is all about what happens underneath the hood. I worked on a distributed system where no one had any idea of what was going on and why there were production issues. We had some monitoring and logging in place, but we had no clue where, how, and what to look out for whenever there was a problem.

Join this session, where I discuss my journey with Observability. I will share how I discovered various insights about my system by using this approach. How I learned this technique and implemented it within my engineering team.

In the current era, organizations are building applications with more complex architectures such as - blockchain, distributed systems, and microservices. The job of maintaining these systems and ensuring it is working as expected has become a challenging task. Gone are the days where testers have to rely on the UI’s to validate an application. Now it is all about what happens underneath the hood and how far you shift testing. I worked on a team where we followed DevOps and started testing as early as possible by shifting left. But that wasn’t enough in terms of the quality of the product or keeping our users happy. That’s where we changed our process and started taking smaller steps into shifting right. 

We had some monitoring and logging in place, but we had no clue where, how, and what to look out for whenever there was a problem.

Join this session, where I discuss my journey with shift left and shift right approach. I will share how using this approach has been helpful to our team.