Podcast

Did you hear or see the must view resource on modern day Oracles or BULL Machines? How to survive in the ChatGPT world have you seen the new Playwright Model Context Protocol? And what is K6 Studio? Find out in this episode of the Test Skill News show for the week of March 23rd. So grab your favorite cup of coffee or tea and let's do this. Hey, before we get into the news, I want to thank this week's sponsor, Zap Test AI, an AI driven platform that can help you supercharge your automation efforts. It's really cool because their intelligent copilot generates optimized code snippets while their plan studio can help you effortlessly streamline your test case management. And what's even better is you can experience the power of AI in action with their risk free 6 month proof of concept featuring a dedicated ZAP expert at no upfront costs. Unlock unparalleled efficiency and ROI in your testing process. Don't wait. Schedule a demo now and see how it can help you improve your test automation efforts using the link down below. All right, this first resource comes your way via Michael bolton so on LinkedIn. Michael Bolton recently wrote a post urging testers to exploit a newly released resource that dissects the impact of generative AI on critical thinking and decision making. The work, called Modern Day Oracles or Bull Machines how to survive in a ChatGPT world was created by two University of Washington professors, provides an accessible overview of AI systems, particularly large language models like ChatGPT has their influence on education, public discourse and intellectual rigor, structured with short chapters discussing prompts and embedded videos, and the content is really designed in a way to help you really understand what's going on here and how to think better or more critically about AI. And the reason why I think this is important is Michael actually connects the material directly to the core responsibilities of software testers applying critical thinking to software systems in the environment in which we operate. And Michael argues that while all team members exercise judgment, testers are uniquely tasked with scrutinizing and exposing issues, making resources that strengthen analytical skills particularly relevant to you. So thank you Michael for another thought provoking resource. Definitely follow him and check out this resource in the links down below. All right. Also notice that Cypress just introduced a new feature. So Cypress has just released a new feature called Cypress Stop, designed to give testers more precise control over test execution within a spec file. This command halts further test execution at any point in a test run, allowing developers and QA engineers to stop tests programmatically based on custom logic or unexpected conditions. This update follows the earlier introduction of Auto Cancellation, a Cypress Cloud feature that automatically halts all parallel test runs when a new commit is pushed, ensuring CI resources aren't wasted running outdated test builds. And it also goes over the key distinctions between these two features. Some Cypress Stop operates within a single spec file during a local or CI runs, and Auto Cancellation applies across all parallel test jobs in the cloud environment. The Cypress Stop command is particularly useful during debugging or in conditional test flows, where continued execution could result in misleading or irrelevant test outcomes. It doesn't throw an error or fail the test run, it simply ends it. So speaking of new features, Mark announced on LinkedIn how Grafana Labs has announced the general availability of K6 Studio, which is a new open source application aimed at simplifying the process of creating performance test. Designed for software testers, developers, SREs and QA professionals, K6 Studio enables users to record API interactions and automatically convert them into structured test cases. Compatible with the popular K6 performance testing tool. The application also includes rule based systems for modifying test scripts, supporting features like data extraction and parameterization, and and allows users to run their tests directly in Grafana Cloud. K6 the goal is to reduce the technical friction often associated with writing performance scripts from scratch, hopefully encouraging broader adoption of a continuous performance testing across teams. I think this launch really follows the growing demand for tools that accelerate test creation, but also reduces the overhead associated with performance testing, especially in fast paced DevOps and CI CD environments. A must check out resource that you can find down below alright, so over the past month or so I've been talking a lot about mcp. So Playwright has just introduced their own MCP protocol. So I first heard about it from Shivam who talked about how Microsoft officially introduced the Playwright Model context protocol, which is aimed at bridging browser automation with AI powered testing workflows. And it's just been released, already has 398 stars on GitHub. And why I think a lot of people are excited by this is that the protocol allows large language models to interact with web applications using structured accessibility snapshots rather than relying on visual pixels, inputs or computer vision techniques. Also, MCP builds on Microsoft's existing Playwright framework and introduces a standardized interface for LLMs to retrieve semantic context from the DOM. This means that instead of interpreting raw HTML or rendering page visually, AI models can now access a well organized structure of the page's elements including roles, labels and states. Mirroring how assistive technologies access content in the structured context enables LLMs to perform more reliable and explainable interactions with web elements, potentially improving the quality and maintainability of automated tests driven by AI. Microsoft notes that MCP could accelerate the development of natural language based test generation, automated bug reproduction, and accessibility validations. So as I mentioned, we talked a lot about mcp, but if it's your first time hearing it or you want to know what the heck is the buzz all mcp? Well, I have a resource from you. I actually found it. It was posted by Angie Jones a link to this article which they Deep dive into MCP and the Future of AI Tooling and this post by Yoko explains the Model Context Protocol introduced in November, which as you know, is an open standard designed to streamline interactions between AI models and external tools, data sources and services. And by providing a unified interface, MCP enables AI agents to automatically select and integrate various tools to to accomplish tasks, reducing the need for custom integrations. And this article breaks it all down for you. It talks about how developers have begun implementing MCP across various applications and it gives an example. For instance, the Code Editor Cursor utilizes MCP to transform into a multi phase platform capable of sending emails via the Resend MCP server, generating images through the replicate MCP server and integrating with services like Slack. And this flexibility allows developers to manage tasks directly within the integrated development environments. And as I mentioned, it goes over some code examples and some workflow examples as well, as well as things to look out for as potential issues also so another term I've been hearing more and more about over the past week or so is around Vibe development. What is it? Well, I found another LinkedIn resource all about this as well, and this by Adonis, which is an article on what is Vibe coding and why you should avoid it. So the term Vibe coding has emerged referring to the practice of of using artificial intelligence tools to generate code based on high level descriptions provided in natural language. This approach allows individuals to create applications by interacting with AI models which then produce the corresponding code. Advocates suggest that this method lowers the barrier to software development, enabling those with limited programming experience to build functional software. However, this article goes over concerns that have been raised about the reliability maintainability of AI generated code. Critics argue that while AI can produce code snippets quickly, the resulting code may lack optimization and contain errors that are difficult to detect without a deep understanding of programming principles. There's also concerns regarding the security of such code, as AI models might not adhere to best practices, potentially introducing vulnerabilities. And while AI assisted Coding or Vibe coding offers a novel approach to software development Software testers should be vigilant about the potential for suboptimal and insecure code, so something you definitely need to be involved with, especially if your team is starting to use this approach for developing software. So this week for some reason has been the week of AI warnings and concerns, and this last article really ties it all together. It's by Tyreek King who goes over Escaping the Agentic AI Hype matrix. So if you don't know Tyreek King is an AI expert and head of Test IO and he does a critical examination of the current enthusiasm surrounding agentic AI. And he contends that the concept of AI agents is not a novel development, but has been foundational to artificial intelligence since at least 1995. And Tyreek highlights that intelligent agents systems capable of perceiving their environment, making decisions, act upon those decisions and learning from those experiences have long been integral to AI advancements in areas such as robotics, multi agent systems and virtual assistants. But he does express his concern over the software testing community's role in and amplifying the hype around agenting AI, noting instances where AI driven testing tools have been promoted despite their limited effectiveness in testing and while acknowledging that enhanced capabilities brought by large language models. Tariq emphasizes that the vision of fully autonomous general purpose AI agents remains speculative. He advocates for a balanced approach, recommending the integration of AI co pilots and agents within well defined task supervised by human oversights to effectively augment intelligence rather than pursuing unattainable autonomy. All right, for links of everything value we covered in this news episode, head on over to those links in the comments down below. So that's it for this episode of the Test Skill News Show. I'm Joe A mission to help you succeed at creating end to end full stack pipeline automation awesomeness. As always, test everything and keep the good. Cheers.