What's new in Test Automation? - Someone is pulling the strings once again

-


Reading the headline of this article you are probably wondering what is the reason for the "Pulling the strings" analogy. Well, you will understand why in a minute.

So what is Playwright?

Playwright is an Open Source Node library for automating Chromium, WebKit, and Firefox by using a single API. It also supports Headless mode for all browsers on all platforms.
Playwright interacts with the browser via the native Debugging protocol (CDP) and according to the contributors was designed with the primary goal of boosting up test automation, eliminating flakiness, speeding up executions and allowing better browser operation. All things mentioned make Playwright an interesting new option for Test Automation.

Sound familiar?



If all of that sounds familiar to you, it is not a coincidence. Playwright was created by the same team that developed the notorious "Puppeteer" (Which is a very similar Node library that offers control over Chromium via the Dev Tools Protocol and is maintained by Google). The Ex-Googlers that originally built "Puppeteer" have since then moved on, joined Microsoft and led a new generation of Automation solutions.

So what is different in Playwright?

Playwright is designed to have many if not all of the capabilities of his older brother, and beyond. The vision was to make it cross-browser. (With a small set of features available for different browsers). The supported browsers are designated to be "Chromium (Including the new Edge), WebKit and Firefox which are designated to be downloaded as an executable during the installation of the Playwright npm package. We can learn from the documentation that mobile-web is going to be supported in the scope.  It is also implied that Playwright is going to have smarter timeout-preventing mechanisms such as waiting for elements to become visible and available for click actions. For more new (And not so new) features, you can visit the API documentation found in Github at the moment.

Sounds good?

Well, actually Playwright is not quite ready yet. It is being actively developed and the team is working on the parity across the supported browsers. Will this be the next Buzzword in Test Automation? Well, we will have to wait and see.





Comments

  1. Francis SmithMay 14, 2022 at 10:08 AM

    Staying organized inside the kitchen means making smart use of your surroundings. That’s why you see many homeowners installing shelves and spice racks. how much weight kitchen cabinets hold

    ReplyDelete
  2. Ivy PJune 28, 2024 at 11:15 AM

    Appreciatte you blogging this

    ReplyDelete

Post a Comment

Popular posts from this blog

Sharing is caring - Intro to Jenkins shared libraries

-
Image
  Whether you're just dipping your toes into the world of automation infrastructure, or already crafting your first jobs to automate your test execution, Jenkins is your new best friend.  In this blog post, we will talk a bit more about the practice of infrastructure as code, its relevance to test automation, and how you can avoid code duplications, align with industry best practices, and enable velocity, maintainability, and collaboration. So, whether you're a seasoned pro or just starting out, let's dive into the world of Jenkins Shared Libraries and see how they can make your life easier. Jenkins Shared Libraries play a crucial role in the realm of Infrastructure as Code (IaC).  So, what are they exactly? Think of Jenkins Shared Libraries as your secret stash of code snippets, neatly organized and ready to be plugged into your pipelines whenever needed. Let's explore the aspect of reusability within Jenkins Shared Libraries: Reusability is the cornerstone of efficien...
Read more

Intro to Terraform and how it is related to test automation infrastructure

-
Image
In this post, we will take a closer look at one of the most popular infrastructure-as-code software tools developed by HashiCorp, and if you follow my recent content, that name should start ringing a few bells. So, what is Terraform and why do we need it? Terraform allows you to define and describe your infrastructure in the form of code. To be more specific “HashiCorp declarative configuration language” (or HCL in short). With Terraform you can manage your resources and infrastructure modules like servers, VPCs, security groups, and much more, even if they are located on different providers such as AWS or Azure.  Generally speaking, cloud providers have their own infrastructure-as-code tools like CloudFormation or ARM. But, Terraform has very extensive support for different cloud providers and platforms allowing you to use a single tool for cross-cloud configurations. This makes it easier to manage your resources, easier to onboard and this is a scalable and in general, the “best ...
Read more

Test Automation, Security, and other vegetables

-
Image
Automation, Security, and other vegetables What is commonly overlooked when focusing on Quality? In this blog post, I want to delve into an aspect commonly overlooked in the context of Test Automation, and that’s the Security aspect.  As test automation developers, we often overlook the basic fact that we are working on a software project. Just like any other software project, considering security in our test automation practices adds a vital layer of protection to our work environment and helps ensure that our work which was initially meant to save time and help quality efforts, will not provide an easy and accessible breach point to our application.  So, on this note, let’s dive into why security should be an integral part of our automation efforts and explore some strategies to ensure our project is as effective as it is secure.  Analyze the attack surface - Before we can effectively secure our test automation infrastructure, it's crucial to identify and analyze poten...
Read more