Automate Browsers With Playwright
After we got Playwright up and running in the last post, we can now take a closer look on how we can automate a web browser with Playwright.
After we got Playwright up and running in the last post, we can now take a closer look on how we can automate a web browser with Playwright.
After last week's turbulences, many people on Twitter talk about moving to Mastodon. For me the biggest challenge to create an account on Mastodon was to find an instance. Unlike Twitter, Mastodon offers many places where you can create an account, or you can host your own server.
Playwright is a reliable end-to-end testing framework for web applications. It is open-source and available for C#, Java, JavaScript, and Python. While it is similar to Selenium and Cypress, Playwright has its own twist on testing and offers a nice set of tools to make writing tests less tedious. Since Microsoft is putting a lot of resources into Playwright, I expect it to be around for the long haul.
I had an annoying experience at the NDC workshop: when I tried to load the solution for the workshop, my Visual Studio immediately froze. It took me a few rounds to try to start Visual Studio without any code. But even then, Visual Studio was still unresponsive.
If something goes wrong with the permissions of your Git repository, you may end up with an error like this:
A few weeks ago, one of our Windows Server made a reboot in the middle of the day. That was not planned, so we wanted to know what happened. Windows logs events like the reboot in the event log. The challenge is to find the right message in the huge pile of unrelated log messages. As it turns out, we can use a filter and get the right message in no time.
Back in Oslo at last. After an online edition of NDC Oslo in 2020 and the travel restrictions at the start of the Omicron wave in 2021, I haven't been to Oslo for a while.
Visiting in September is in many ways different from June. It is colder, and it gets dark early (around 7 pm), yet Oslo is still the same with its constant changes. The Munch museum and the new Deichman main library are now open. After seeing for years how those buildings grow, I now had the opportunity to visit them. Both are close to the Oslo Opera House and worth a visit.
Developers spend a lot more time on reading code than writing it. Therefore, if we want to get more effective, we must take a deep look at the reading part. In this Workshop Mark Seemann uses a set of heuristics to address the common obstacles developers face when it comes to understanding code.
Keep in mind that heuristics are a rule of thumb that you always should take with a grain of salt. They may be a great help for certain situations but may miss important details in others.
As I was working on a project, GitHub Desktop bombarded me with this login dialog:

If your Git client does not clean-up the local branches after those branches got deleted in your remote repository, you can run this command to get rid of them: