Currents’ Post

AI-Powered Testing with Playwright and ZeroStep ZeroStep is an AI tool that enhances Playwright tests with the power of GPT-3.5 and GPT-4. It offers ai() function, that allows users to use AI to write playwright tests. This means that instead of using Xpaths and CSS selectors, ZeroStep's AI assistant takes actions at runtime based on plain-text instructions. I've prepared a small POC to explore how it works. Its integration with Playwright is super easy and you don't need to worry about writing Xpaths and CSS locators anymore. It's pretty much the same as if you are writing manual test cases. It comes with a free version which allows you 1000 ai() function calls per month. The paid version starts with 20$ per month which supports 2000 ai() function calls/month. This option can be customized as per requirements. For straightforward UIs, it performs reasonably well. However, to achieve the best results, you need to provide highly precise commands. It won't function if you provide multiple commands in a single ai() function. The test execution is a bit slow and can be flaky at times but ongoing improvements give hope that ZeroStep will evolve into a more mature tool someday in the future. 

Have you ever found yourself struggling to identify relevant selectors while writing automation test steps❓ 🤔 Have you considered an alternative approach to crafting readable test scenarios without relying on tools like Cucumber, ensuring accessibility to both technical and non-technical stakeholders? If you’ve pondered these questions, this blog post is tailor-made for you. 💯 ▶️ In this blog on "Test Steps with ZeroStep and Playwright" by Amr S., you’ll explore “ZeroStep,” and how it helps in writing playwright tests with AI. you’ll be gaining insights into its capabilities and uncovering both its strengths and limitations. 🔗 Visit now: https://bit.ly/tttblogamr #TheTestTribe #SoftwareTesting #Testers #Community #Playwright #Zerostep

I've been spending time with Playwright's test generator lately. And not a good time, at that. I'm getting asked all the time about test generators, (also AI tooling for that), and do they cut down on the writing time. The answer is yes. But you do get what you pay for. Time of test writing goes down, but you will pay for it later with interest, in readability and maintainability. The problem is that test generation tools don't have context. Playwright's CodeGen tool only sees locators. It doesn't understand what they are used for in the application. Or rather, when a human sees the generated result, and they do have the context, they don't see how that relates to the code, because it's not there in the code. That means more time understanding what the tests do, why they fail, and adding risks when debugging. We want a lot more from our tests. On May 7th, my "Playwright in an hour", is not just introduction of the tool, but also my take on how it helps (or not) you with your job. You know, what tools should actually do. There's whole lot of good, but as you can see, some traps are hiding in there. May 7th, 2024. Not once, but twice. Europe: https://lnkd.in/eDJNHqmK US: https://lnkd.in/e9Yyq-KF #Testing #Playwright #WebTesting #WebAutomation #TestAutomation

I've been spending time with Playwright's test generator lately. And not a good time, at that. I'm getting asked all the time about test generators, (also AI tooling for that), and do they cut down on the writing time. The answer is yes. But you do get what you pay for. Time of test writing goes down, but you will pay for it later with interest, in readability and maintainability. The problem is that test generation tools don't have context. Playwright's CodeGen tool only sees locators. It doesn't understand what they are used for in the application. Or rather, when a human sees the generated result, and they do have the context, they don't see how that relates to the code, because it's not there in the code. That means more time understanding what the tests do, why they fail, and adding risks when debugging. We want a lot more from our tests. On May 7th, my "Playwright in an hour", is not just introduction of the tool, but also my take on how it helps (or not) you with your job. You know, what tools should actually do. There's whole lot of good, but as you can see, some traps are hiding in there. May 7th, 2024. Not once, but twice. Europe: https://lnkd.in/eDJNHqmK US: https://lnkd.in/e9Yyq-KF #Testing #Playwright #WebTesting #WebAutomation #TestAutomation

I've been spending time with Playwright's test generator lately. And not a good time, at that. I'm getting asked all the time about test generators, (also AI tooling for that), and do they cut down on the writing time. The answer is yes. But you do get what you pay for. Time of test writing goes down, but you will pay for it later with interest, in readability and maintainability. The problem is that test generation tools don't have context. Playwright's CodeGen tool only sees locators. It doesn't understand what they are used for in the application. Or rather, when a human sees the generated result, and they do have the context, they don't see how that relates to the code, because it's not there in the code. That means more time understanding what the tests do, why they fail, and adding risks when debugging. We want a lot more from our tests. On May 7th, my "Playwright in an hour", is not just introduction of the tool, but also my take on how it helps (or not) you with your job. You know, what tools should actually do. There's whole lot of good, but as you can see, some traps are hiding in there. May 7th, 2024. Not once, but twice. Europe: https://lnkd.in/eHwxvyhf US: https://lnkd.in/e8C2dvsK #Testing #Playwright #WebTesting #WebAutomation #TestAutomation

I've been spending time with Playwright's test generator lately. And not a good time, at that. I'm getting asked all the time about test generators, (also AI tooling for that), and do they cut down on the writing time. The answer is yes. But you do get what you pay for. Time of test writing goes down, but you will pay for it later with interest, in readability and maintainability. The problem is that test generation tools don't have context. Playwright's CodeGen tool only sees locators. It doesn't understand what they are used for in the application. Or rather, when a human sees the generated result, and they do have the context, they don't see how that relates to the code, because it's not there in the code. That means more time understanding what the tests do, why they fail, and adding risks when debugging. We want a lot more from our tests. On May 7th, my "Playwright in an hour", is not just introduction of the tool, but also my take on how it helps (or not) you with your job. You know, what tools should actually do. There's whole lot of good, but as you can see, some traps are hiding in there. May 7th, 2024. Not once, but twice. Europe: https://lnkd.in/eHwxvyhf US: https://lnkd.in/e8C2dvsK #Testing #Playwright #WebTesting #WebAutomation #TestAutomation

Let's dive into some of our go-to Google Chrome extensions and integrations that make our lives easier! ⚡️ Supernormal: This AI notetaker seamlessly integrates with Google Meet, capturing meeting notes effortlessly. From jotting down action items to sharing notes with your team, Supernormal also generates summaries and sends weekly roundups to keep you on track and accountable. ✏️ Grammarly: Never worry about misspellings or awkward phrasing again. Grammarly is like having a friendly editor by your side, ensuring that your emails and messages always sound polished. 🔎 Squarespace ID Finder: If you're a Squarespace fan like us, you'll appreciate this handy tool. It's perfect for quickly grabbing IDs when you're working with custom code. Trust us, it's a game-changer! While there are many more extensions out there, these are some of our favourites! What are yours?

Publishers, You're Being Scraped Blind! Here's How to Fight Back The internet is full of hidden dangers, and one of the biggest threats publishers face is content scraping. Imagine someone stealing your articles and using them to make money, without you getting a dime. That's what scraping does! Here's the Shocking Truth:  - Scrapers are taking your valuable content, often without permission.  - This hurts your business model and devalues your hard work.  - Just like Napster hurt the music industry, scraping is a ticking time bomb for publishers. Don't let history repeat itself! This two article issue, https://lnkd.in/e4CguAsK and https://lnkd.in/e9e5J9aS of our newsletter Content Licensing Brief exposes the dark side of scraping and offers solutions:  - Learn how scrapers are stealing your content and what the future holds.  - Discover practical steps you can take to protect your website and content.  - Understand the ethical and legal implications of scraping. Stop letting scrapers walk all over you! Take action today and share this article with fellow publishers! Together, we can protect our content and ensure a fair digital landscape. #media #licensing #copyright #AI

📄 Generate Full-Blown Articles that rank in Google. ✅ Complete articles with headers, sub-headers , key takeaways, quotes, sources, FAQ and conclusion. 👇 Try 2 articles for $39.95 - Too powerful for a free trial GOAT OR NAH? #ai #AIContentGenerator #ContentAtAscale #aiCopywriter #aiWriter #AffiliateWeapons

📄 Generate Full-Blown Articles that rank in Google. ✅ Complete articles with headers, sub-headers , key takeaways, quotes, sources, FAQ and conclusion. 👇 Try 2 articles for $39.95 - Too powerful for a free trial GOAT OR NAH? #ai #AIContentGenerator #ContentAtAscale #aiCopywriter #aiWriter #AffiliateWeapons