With the newly gained knowledge about Playwright, we have everything together to go and automate a browser to do repetitive tasks. Let's figure out how Playwright differs from Selenium when it comes to download Jetpack statistics.
In this post we explore 3 helpful ways to figure out what went wrong if Playwright cannot find the elements we are looking for.
Last week we got Playwright up and running in Python. In this post we build on that and start to automate our browser.
Over the last few weeks, I experimented with Playwright and wrote a few posts on how to work with it from C#. Because I got so many comments about Playwright whenever I blog about Selenium, I go for a slightly shorter set of posts that cover Playwright for Python users. The obstacles I run into in C# may happen to you in Python too.
If you need to find out what went wrong during an end-to-end test, a recorded video of the browser with all its interactions can be a time saver. Let's look at how we can create these videos with a dynamic Selenium Grid.
While preparing the code samples to record videos of my test runs, I run into a severe problem: Selenium Grid cannot do what I need it to do - at least not with the approach I had so far. Let's regroup and switch the way we create the Selenium Grid.
One of the greatest benefits of Selenium Grid is to run Selenium against multiple browsers. This can be multiple instances of one web browser that we run in parallel, or browsers from different vendors. Let's see how we can configure a flexible solution without much effort.
Sometimes it would be great to have a web browser in a specific version. Installing that on your machine may not be possible, but that is exactly the problem we can use dev containers for. Let’s look how Selenium and Docker can help us to get more flexibility (and additional features).
Selenium is great to automate repetitive task in a web browser. We can take that concept one step further and use it to create end-to-end tests for web applications. Today we look at an approach to keep the initialisation code for Selenium in one place and use it in as many tests as we need.
The Jetpack extension of WordPress.com uses a lot of JavaScript to work. With Selenium we do not have to bother about that and let our web browser deal with it. This allows us to grab the statistics Jetpack collects for this site.