Testing Banking Apps, WebDriverIo, E2E Playwright TGNS133

What test tool are testers of banking and financial apps raving about? Have you seen the latest mind blowing release of Webdriver IO? And how do you do API Database and end to end test automation using Playwright? Find out all about these and more in this episode of the Test Guild News show for the week of August 18th. So grab your favorite cup of coffee or tea and let's do this before we get into it. If you haven't already, please make sure to subscribe to Our Test Guild LinkedIn News Show Newsletter. They'll have a link to Down Below to never miss another episode. So our first item is a little different. You know me, I don't like to criticize tools or tool vendors. Still, many testers have told me how frustrated they've become with this huge company. I'll leave Nameless, which has been the preferred solution for financial services and major banks. Some have told me they've also gone as far as discontinuing its use or considering doing so. The they also tell me how annoying it is to use because of its complexity and the excessive time required to automate test cases, which slows them down in their testing efforts. And many of these tests have reverted back to do manual testing of things that can be automated, especially for testing processes across different applications and devices, including email and PDF checks. A lot of the enterprise type of testing you need to do in these types of environments, but testers at the most advanced banking and financial services solve that problem. How? I'm going to spill the beans now. They did it with one simple step. They made a simple switch to Test Results IO. This is a company of founders that I've interviewed on my podcast in the past and it's a solution I think it's worth considering and it's a solution you should see and try for yourself. So I have a special offer for for listeners of this new show. Send me your email address via DM and I will personally introduce you to the founders of Test Results IO as I know them personally. This is an exclusive opportunity to speak directly with them. They'll even tell you which tool vendor I left Nameless in this post. And to make this deal even sweeter, I'm going to offer a Free Automation Guild 2025 Ticket Exclusive Automation Guild Community access in my ebook with with every Test Results IO license you purchase. So make sure to DM me to learn more. Next up is a new release of a test tool I think you need to know about. So I heard about this from TRISTAN about how Webdriver I.O. was just about to release a new version and he was hosting an event that was going to go over some of the new features. And then I saw this post last week from OpenJS foundation which announced the release of WebDriver IE version 9. And this post goes over all the new features and benefits for the new version, introducing several enhancements and its improved performance, usability and integration capabilities, making it a huge upgrade for developers and testers alike. And some of the new features that popped out to me were the enhancements to webdriver by Die. There's a new URL command parameter that helps you do a bunch of cool things. Also, it has automatic piercing of web components, iframes and shadow doms. It has visual testing, reporting capabilities and a bunch more. And to hear about all these new features, definitely check out my latest podcast interview I just released yesterday with Christian, who is the main contributor and maintainer of WebDriver IO. As we talked all about the latest version 9, you don't want to miss it and you can find links to all these in the comments down below. All right, next up is how to do API Database End and testing using Playwright. In this recent blog post by matab, they provide insights into the unified approach for API database and end to end testing using Playwright. They highlight the challenges faced by testers due to the fragmented testing ecosystem, which traditionally requires use of multiple tools for different testing domains. This post proposes Playwright as a comprehensive solution capable of addressing these testing needs under a single umbrella, and the blog post provides practical examples and code snippets to demonstrate Playwright's features, such as its ability to handle various test scenarios and its capabilities with modern testing requirements. Also, one of the major advantages of using Playwright, according to this post, is the reduction in complexity and learning curve for testers, and by consolidating multiple testing tools into one, Playwright simplifies the testing process, which could lead to quicker test development and execution. So check out the post, let me know your thoughts. And speaking of Playwright, this next post, which is posted on Bonder Academy by Autumn Bonder talks about Playwright Not Waiting for Elements, which discusses a common issue faced by many developers and testers using Microsoft Playwright framework for automated browser testing and this article delves into the intricacies of effective waiting for elements to appear in the DOM while using Playwright ensuring more stable and reliable test outcomes. This blog elaborates on different strategies to handle situations where tests fail because an element is not yet available, and emphasize the importance of understanding Playwright's built in waiting mechanism and how they can be leveraged to avoid unnecessary test flakiness through detailed code examples. It guides you to how to use functions like wait for selector, and also touches upon advanced usage scenarios such as handling dynamic context and and network responses. And I think the primary takeaway from this blog post is that the understanding of Playwright's waiting mechanisms is crucial for writing stable automated tests to ensure that all necessary elements are loaded and interactable before allowing tests to proceed. And this definitely could prevent a lot of script flakiness that you've probably been seeing. Definitely check it out in the comment down below. All right, this next article is all about trusting AI and machine learning. So this recent blog post by Tony, who wrote a detailed article that provides insight into the pivotal role of automated testing and ensuring the reliability of artificial intelligence and machine learning technologies. And as you know, there's a growing reliance on AI ML and various sectors necessitates really stringent testing protocols to verify the accuracy, performance and security. And this blog post highlights the need for a robust framework for testing AI and ML systems due to the inherent complexities and unpredictable behaviors resulting from vast amounts of data and intricate algorithms. And these technologies need continual assessment not only at the development stage, but throughout their operational lifecycle. He also emphasized the traditional testing methodologies are often inadequate for AI ML systems given their dynamic, evolving nature. Therefore, specialized automated testing approaches such as modeled validation, simulation based testing and anomaly detection are crucial, and these methods help in managing the constant feed of new data and configurations that AI ML systems encounter. And it gives some examples and it also goes on how the incorporation of automated testing into AI ML development pipelines not only ensures the elimination of biases and errors, but also enhances the transparency and trust in these Systems. Definitely another Mark 3 that you can find in the comments down below. All right, are you using Cypress? This next article is all about Cypress Web accessibility and this by Matter who goes over Ensuring Web Accessibility with Cypress? A comprehensive guide, and this offers a thorough explanation how web developers can leverage the Cypress testing framework to ensure their sites are accessible to all users. And the guide provides a step by step process on integrating accessibility checks into the development lifecycle using Cypress and it begins by highlighting the importance of web accessibility, referencing global standards and regulations, including the Web Context accessibility guidelines, and the author emphasizes the societal and legal imperatives of making web content accessible to people with disabilities. Some key sections of this guide detail the installment and configuration of Cypress, demonstrating how developers can write and automate accessibility tests. Additionally, the guide covers how to use plugins like Cypress Axe, which integrate the Axe accessibility testing engine within Cypress and through practical examples. The guide showcases how to write accessibility tests that identify common issues such as missing alt text, poor color contrast, and improper heading structures. Definitely a worthwhile thing to learn more about if you're using Cypress for sure so this next blog post is about a security hack I didn't know anything about. So I found this next article because because it was posted by Mark about how researchers have introduced a novel class of high precision branch target injection attacks. What is it? I didn't know. So I clicked on this article and after reading it, it's all about how MTI attacks target the latest Intel CPUs including Rapture Lake and Alder Lake models. And the study uncovers new vulnerabilities within the indirect branch predicator and the branch target buffer and in these processors, allowing attackers to bypass existing security measures. And by reverse engineering these components, the researchers developed precise BTI attacks capable of breaching security boundaries in various scenarios, including cross process and cross privileged environments. All the things you need to worry about as a tester and this is just something I think you just need to be aware about as well. All right, for links of everything of value we covered in this news episode, head on over to the links in the first comment down below. So that's it for this episode of the Test Skill News Show. I'm Joe. My mission is to help you succeed in creating end to end full stack pipeline automation awesomeness. As always, test everything and keep the good. Cheers.