This saves me 5-10 seconds on each commit.

https://t.co/tXmDxD2gXj one of my favorite things I've built with

This can be very helpful when trying to identify flaky tests

Stumbled upon an epic, fatigue-resistant software testing wiki dropped by @lucgagan on Rayrun! 🤓 Dive in to geek out and join the QA community: https://t.co/RL6Lx3solc #qa #testing #wiki

I feel bad rejecting all the consulting offers because some of these companies are phenomenal. Need some sort of way to off load these requests to the community.

Writing an article about tools used for Visual Testing with Playwright. Which tools should I cover?

TIL that you can watch releases on GitHub

I am grateful to everyone who dedicated time to this matter and helped me shape a healthier perspective. The https://t.co/y8sHJcwCoY has been also updated to properly acknowledge the work of the ZeroStep project.

I extend my apologies to the original authors for the manner in which I led this discussion. I neglected to fully embrace the open-source ethos by failing to adequately acknowledge those who laid the foundation for my work. I am committed to improving in this regard.

While I still believe the structures of our codebases are distinct, I recognize that I referred to their work while conceptualizing auto-playwright and that it is essential to properly credit the original creators.

I now understand how my actions, particularly copying parts of their documentation and code verbatim, may have been inappropriate. Although I began with a fresh start, I extensively reviewed their code to grasp its functionality.

After reflecting on the situation and my response to it for a day, I realize that I need to revise my position. The ZeroStep project significantly influenced the development of Auto Playwright.

This was the favorite thing I've learned myself this week!

Discovered that GitHub Actions can be triggered manually with custom inputs, which happens to be a great way to stress test tests. What other use cases have you found this to be useful for? https://t.co/h5UZtrAXoj

I am still experimenting with ways to surface those scenarios. Your input would be appreciated.

This approach helps you identify flaky tests that are flaky as a result of network related race conditions. However, it does not handle scenarios such as: out of order execution or flakiness as a result of unexpected side-effects (like a modal closing unexpectedly).

Simple but effective way to detect flaky Playwright tests by throttling the network https://t.co/7z1FFxjxrY

The reality is that most of these companies are building in the direction of AGI. The true everyday enhancing AI applications will come from niche use case applications, like that of Auto Playwright.

Over the last 24 hours received lots of DMs and comments along the lines of "you are not Google/IBM/Amazon so stop trying to do AI" Yikes! Those who restrict their learning to what comes out of these companies are going to be deeply disappointed when they will be left behind.

The irrational hate for "AI wrappers" in dev community is scary. There are some that are open to the idea of exploring what's possible using AI, and then there is everyone else who are taking the position that can effectively be summarized as "AI won't replace my job"