UI automation Infatuation, State or Observability and More TGNS113

How would you compare the difference between Cypress versus Safe Test? Are you infatuated with UI automation? And have you seen the latest report on the state of observability? Find out in this episode of the Test Guild News show for the week of March 10th. 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 newsletter. You could find the link in the comment section down below and never miss another episode. And speaking of LinkedIn, if you have a news item you'd like me to feature, let me know on LinkedIn. For example, the folks at Pacific Northwest Software Quality Conference 2024 wanted me to remind you that their Call for proposals Pacific Northwest Software Quality Conference 2024 is open until April 1st. This is a great organization and conference, and it's if you are serious about software quality and you want to share your expertise on a topic, make sure to submit your paper now to one on what I think is one of the world's most respected conferences in the space and tell them I sent you So I mentioned Safe Test a few weeks ago on this show, so I was happy to stumble across this next post and this by Gleb. He's an expert in Cypress and automation and development, and he's taken a deep dive into both Cypress and Safe Tests and and he offers a real detail analysis on his blog between Cypress vs Safe Test. So if you don't know, Safe Test is built on top of Playwright and it was released by Netflix aiming to streamline component testing. And Gleb contrasts it with Cypress's component testing feature, using concrete examples for a real, thorough comparison. Also, Gleb's analysis offers several key aspects, including whether these frameworks should be considered a dev or production dependency, installation process, test speed, and developer experience. And Gleb notes that Save Test appears to be a production dependency, a point he disagrees with and advocates for testing libraries to be dev dependencies. As is the case with Cypress. He also goes over installation ease. Test execution speed and overall developer experience are amongst some of the criteria that he uses to compare the two. And Cypress, for instance, automates much of the setup process and doesn't require running the application for testing, unlike Safe Tests. He also points out that this, along with the faster test execution and seamless integration into the developer's workflow, positions Cypress as a highly efficient tool for component testing. Also, Gleb touches on the support for mocks and spies and overrides and the ability to write test easily in both frameworks. And despite the strengths of Safe Test, including its innovative approach to extracting components for testing, Cypress is highlighted for its interactive mode that really enhances test writing and debugging. And at the end he concludes his analysis and Gleb leans towards Cypress for what he thinks is its developer friendly approach and efficiency. And he does acknowledge the potential for Safe tests, especially with Netflix backing. So if you want to take a deep dive and understand the comparison and see which one is best for you, definitely check out Gleb's article in the links down below. And speaking of Playwright, as you know, web overlays and pop ups often disrupt automation tests. That's what this next article addresses. And this article goes over this feature that enables seamless handling of web overlays, enhancing the reliability and efficiency of automated testing. And this post also delves into the practical application of Playwright's ad Locator Handler, which offers insights on how to effectively manage these web interruptions so for developers and testers really look at to streamline the testing process and ensure a smoother testing experience or animation experience. Mastering the use of Locator Handler with Playwright really can help you make your tests more reliable. And this advancement not only promotes and tackles the nuance of web popups, but also helps you to elevate the quality of your automation by making automated tests more robust and and dependable using built in features of a lot of these tools. So if you haven't tried the Locator Handler with Playwright, here's your opportunity to try so right now. And while UI automation is awesome, as you can tell by the previous post, a lot of times it's not as reliable because you have all these other things going on like pop ups. So what do you do? Well, Alan Page revisits the contentious subject of test automation and his new blog post titled the A Word and Revisit It. Check it out. And as I've been mentioning many times, I've been following Alan forever. He's actually featured in my Automation Awesomeness book on page 22, so definitely check this out as well. But but he goes over in his blog post. Drawing from his extensive experience, Alan critiques the software industry's ongoing infatuation with UI automation. He highlights its limitation and often misplaced emphasis on automating user workflows. Instead of addressing testing challenges through through code and reflect on his own work, including the ebook the A Word under the covers of Test Automation, Alan advocates for a shift towards developers taking a leading role in test automation. He argues this approach not only yields more robust and maintainable tests, but also results in better design and more testable code. And Alan's insights underscore how test automation and the need for innovative testing solutions and approaches should really go beyond traditional UI automation to improve your software quality and development practices. I think this is a must read and you could check it out as well. Let me know your thoughts in the comments down below. In my trends for 2024, I mentioned how I think this was going to be the year of how observability or development for observability is going to be a big trend. And so I was excited to find this new report that goes into detail on different things as it applies to the state of observability. And this is the latest report by Dynatrace and It's surveyed over 1300 tech leaders and reveals that the average multi cloud Setup now spans 12 platforms. And 88% of leaders say their tech stack complexity has increased in the past year and this complexity explosion is making it harder to deliver outstanding customer experiences, according to 87% of its respondents. The report also finds teams are drowning in data, with 86% of leaders saying that data volumes are too much for humans to manage. And organizations are using an average of 10 different monitoring tools, further compounding this complexity. And the report dives into a few things on how to overcome these challenges. For example, the report asserts that a mature AI and automation strategy leveraging a unified observability platform really is key. Already, 79% of organizations plan to adopt AIOps in the next 12 months to team multi cloud complexity. And the report suggests Moving beyond traditional AIOps to a more predictive AI driven analytics is needed to really drive innovation in the modern cloud era, especially for testers and developers. Another great report. Check it out, let me know what you think. This next company just unveiled its latest advancement in security testing and the offering is attack service discovery and it introduces scalable AI penetration testing. And it goes over how this enhancement aims to empower security teams, which often find themselves overwhelmed, to stay one step ahead of the rapidly evolving cybersecurity threats we find ourselves in. And what's really cool is this uses AI technology to enhance the effectiveness and efficiency of penetration testing. And I think this really highlights how we're making a move towards how more and more companies are taking cyber threats more seriously and how they're leveraging tools that are AI powered to help them with their security testing as well. All right, as I was looking up security tools, security testing this next article came my way on my LinkedIn stream and it was posted by Monday posting to a post about owasp NET Attacker and this post was written by Harleen who talks about an automated pen testing tool called NET Tracker, which is an OWASP developed automation penetration testing framework. It was developed with Python and NET Attacker streamlines security testing phases such as information gathering, enumeration, scanning and vulnerability assessment and and this tool stands out for its automation in discovering services, vulnerabilities, misconfigurations and generating detailed security posture reports. It's also open source and accessible on GitHub. Net attacker encourages contributions from security professionals and developers that really help to foster continuous improvement on it and its compatibility with Python really enhances user flexibility and ease of operation. And additionally, NET Attacker boosts a unique ability to bypass firewalls, IDs and IPS's, increasing its efficiency and uncovering hidden vulnerabilities. And this is just another cool development and another cool tool coming away from the folks at owasp, so definitely worthy to check out as well. All right, for links of everything value we covered in this news episode, head over to Links in the comment down below. And while you're there, make sure to subscribe to the Test Guild and News show newsletter so you never miss another episode. All right, so that's it for this episode of the Test Guild 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.