Automation deep-dives on Ish's Blog

Fetch GraphQL query from an Apollo client using APQ - Part 2

Sat, 10 Aug 2024 00:55:00 +0530

As discussed in part-1 of this blog, when using apollo client one can boost the performance of the graphql queries by using “Automatic persisted queries” or APQ. By using APQ, the server caches each requests initiated from the browser against a hash which if not found, forces the web browser to re-send the request with the complete graphql query.

Fetch GraphQL query from an Apollo client using APQ - Part 1

Sat, 20 Jul 2024 23:55:00 +0530

APIs (Application Programming Interfaces) for web applications have evolved significantly since the early days of the internet. Initially, APIs were simple and used primarily for data exchange between server and client, often through protocols like SOAP (Simple Object Access Protocol). These early APIs were cumbersome and required extensive documentation and strict adherence to protocols.

The rise of REST (Representational State Transfer) in the early 2000s marked a major shift, offering a more flexible and scalable approach to building web APIs. RESTful APIs leverage standard HTTP methods, making them easier to use and more intuitive. However, 2015 saw a paradigm shift, Facebook (now Meta Inc.) introduced GraphQL to the world, allowing clients to request specific data, resulting to it’s rapid adoption amongst enterprises. According to reports, it is projected that by 2025, over 50% of enterprises will use GraphQL in production, up from less than 10% in 2021.

Understanding the Selenium Webdriver

Wed, 19 Feb 2020 21:47:38 +0530

Over the course of time, my pursuit for understanding the internals of Selenium compelled me to crawl the corners of the internet in search for answers. I was searching for something that can help me connect the dots between the the browser and selenium.

With countless blogs and documentation fuelling my experiments, here is what I’ve been able to learn of the WebDriver and the W3C WebDriver Protocol.

What is a WebDriver?

According to the selenium documentation :

Generating HTML reports for your tests via Gradle

Mon, 17 Feb 2020 18:45:18 +0530

In the test automation world, visualizing the results of your tests have an equal priority in conjunction with the tests being executed. How will you be able to make the most out of the tests being executed? Would a simple report having Pass/Fail ratio along with the screenshots suffice? or the reports need to be more comprehensive? maybe the report needs to keep a trend of the tests being executed over time? or needs to have a documented step for each action?