Let’s see how we can do the Kubernetes workload automation using the Rest APIs.
Kubernetes is quickly becoming the new de-facto standard for container deployment and orchestration in the cloud. In our day to day life, most of the times we use kubectl to interact with the kubernetes cluster. Kubectl is a command line application written in Golang which takes your CLI commands and pass it to the Kubernetes API Server via REST communication.
Lets’ see this picture to make it more clear.
Kube-API-Server is the main interface which exposes a communication channel and allows us to interact with the…
Picture speaks more than the words.
In this article we will be talking about the visualisation of the performance timings in the microservices environment which is not at all an easy task specially when these services are highly reactive and asynchronous.
Let’s take an example of a typical micro services architecture to set the context, where services are running inside a containerised environment.
Let’s see, what will be the challenges here to monitor the performance of each micro service.
As you can see below our performance testing client will sit outside the cluster to mimic the actual user and our…
In the Part 1 of this blog series, we have learnt how to spin up a Selenium Grid from scratch inside a Kubernetes cluster. In this second part, we will learn more about the auto-scalability aspect of this Selenium Grid Cluster.
Auto-scalability is an essential attribute for any application to make it more elastic, scalable and available.
Kubernetes has an in-built auto-scaling feature called Horizontal Pod Auto-Scaler (HPA) which automatically scales the number of pods in a replication controller, deployment, replica set or stateful set based on observed CPU utilization.
But, this native HPA does not fit in to our…
To maintain a home grown Selenium grid cluster is not at all an easy task due to the complexities involved in running and maintaining these hundreds of browser containers. Due to this same reason, most of the companies end up outsourcing this task to vendors like Saucelabs, Browserstack and AWS to save the time and energy of their engineers and to bring more stability to their Selenium Grid infrastructure. These vendors are really expensive and one would need to shell out hundreds of dollars to execute their UI test cases on these public cloud of browsers.
In case your application has a clipboard feature where users can copy the screen content to clipboard in a specific format then it could be a good candidate for automated testing.
Testing the text content and format visually is a tiresome job so one would definitely like to automate it.
To make you understand the scenario better let’s see the example of this demo website where you have to test the copy functionality.
We will type some text in to the text box and then click on copy button. Then as an assertion point we have to read the content…
This article is in continuation to my previous article “Selenium + Chrome Dev-tools makes a Perfect Browser Automation Recipe” where I talked about how we can debug a chrome instance using Chrome dev-tools protocol.
I will strongly recommend to read the previous article in case you are not familiar with chrome dev-tools protocol.
Recently a gentleman asked me if we can debug a chrome running inside a docker container using the same dev-tools protocol.
The Web Notification is not something which is new in the market. All the major browsers are supporting these notifications since last 4 to 5 years.
At-least this blog is a proof that notifications arrived in Chrome in the year 2015.
When my team recently got a task of automating these web notifications, I started googling about it and to my surprise there is no strategic solution available for this problem over the entire internet.
As a normal tech person I decided to throw this problem to my automation fraternity on Linkedin but unfortunately did not find any concrete solution.
I was just browsing the Twitter and came accross a tweet mentioning that Chrome 63 is coming with Multi-client remote debugging support.
In sheer excitement I also replied to this tweet.
You must be wondering why I was so excited by this feature. It made me excited as it opens up hell lot of possibilities for people like me who works in Test Automation.
Recently I struggled a lot to solve some of the Browser automation issues where I found Selenium WebDriver was not perfectly equipped to solve them.
The issues like: