No Scripts, No Frameworks, No Maintenance? with Don Jackson

In a land of testers far and widely journey, seeking answers, seeking skills, seeking a better way o the Test Illumination Testing podcast Guiding testers with our nation awesomeness from ancient realms to modern days, they lead the way. Oh, the testicle Awaits and Testing Podcast.

Hey, welcome back to the Test Guild Automation Podcast. Today I'm thrilled to have Don Jackson join us to discuss an exciting new development with the gentic AI. Don breaks down how this new approach differs from traditional scripting enabling capabilities like exploratory testing, improved UI automation for dynamic applications like Salesforce, and even complex validations such as checking if an image matches its text description or ensuring accessibility compliance with WCAG standards. He'll also discuss how the solution can perform actions like installing an app from a store without explicit scripting. And while I'm still skeptical, as you probably are, about this approach, which he calls no script, no framework, no maintenance, he does address common skepticisms about UI automation reliability and how the agentic AI maintains trust through screenshots and video recording. And if you're skeptical like me and you want to see this in action but have questions, make sure to join us with Don on a webinar that we're running at the end of this month at the Test Guild. And you can register for it now using the link down below. We'll cover all this and more. You don't want to miss it. Check it out. Hey, Don, welcome back to the Guild.

Well, thanks for having me, Joe. It's always good to talk to you. I love watching your stuff. In fact, I was just watching your note for this week, so hopefully everybody subscribes and is reading and watching your weekly. What do you call it? A weekly message? I can't remember what you call them.

It's weekly news show.

Weekly news show. Yeah.

Awesome. Yeah, thank you for that. Really excited about. Also, I saw some recent announcements on LinkedIn. You've joined a new company. Maybe you tell us a little bit more about that. You know, a lot of people are looking for new gigs, and it seems like you found the perfect spot. Like, how did you do that?

Yeah, well, how did I do that? So I'll answer the first part first and the second part second. So, yeah, so I've joined Perforce, working specifically on Perfecto and blazemeter. But I also, obviously, you know, I work for the company, so I look at stuff Pan Portfolio as well, not just those two products. So, like, for example, I'm talking with a couple of people that we all know, and until something happens, I can't say who but on Perforce, alm, Perfecto, blazemeter, both for API and for load testing and for service virtualization and in BlazeMeter. And then the second part of your question was how? Right. A lot of people looking for jobs, you know, in all honesty, right. I didn't specify in LinkedIn that, that I was looking, that I was open to work or anything like that. I just reached out to key people in my network that I really trusted. I trusted their opinions and used my network that way to find out, you know, where somebody was. I specifically talked with Phil Raymond, who's at Perforce, and I kind of asked him point blank, how do you like it there? Right. And obviously it was a positive response that he gave. I don't want to say specifically what he said, but, you know, went through the interview process, had a bunch of wonderful interviews, you know, really clicked with them. And so, you know, the culture was great. And I was super excited about the technology that is being released actually on July 15th. Depending on when you're watching this, that might be in the future or last week or whatever. But I was really excited about it because it's actually a concept that I had been talking about about 18 months ago that I was calling goal oriented testing. Right? Goal oriented automation, where you give an objective to the AI and let it go, figure it out. Just like a manual tester would, right? I don't tell a manual tester. I just tell them, hey, you got to log into the site. I don't tell them, how do you get to the login page? Do you have to click on the hamburger menu or the profile icon or whatever? I just tell them, go log in. Right? So same concept that we're releasing on the 15th.

All right, so I think I saw this demo. You gave me a demo like maybe a year and a half ago. I was like, wow, this is pretty cool. But you just joined this company like a month ago. Did they see that demo? And they actually executed on it, like, was it just like serendipity? Like, wow, like synchronicity?

I think it's actually happens to be coincidental because when I was talking with our head of products, you know, he didn't mention it, right? And I said, you know, this was a concept. And he goes, oh, really? Right. So I think it just, you know, two people happen to have a similar idea. And in fact, you know, I know Tree King has talked about this concept as well. So it's. We're not the only ones. But, you know, seeing what you can do with AI and you Start going, okay, so how do we take it to that next level? What can we do with it? So I'm just super excited, you know. Cause it was something that I was talking with with the products team at my last company, and that didn't go anywhere at the time. They had other priorities. That's the right way to say it. Right? They had other priorities.

Great. So for the folks that didn't see the demo, maybe break it down a little bit more like to like no one's heard of it before. What are you talking about? What is this announcement about? It's a agentic AI or is it like. Yeah, some flavor of agentic AI. What's it all about?

So it's true agentic AI. So when I say true agentic AI, there's a lot of people who say agentic AI and then you dig into it and it's like, this is just a request and response. That's not. That doesn't have any agency. So what do I mean by agency? Right? Great question. Thanks for asking, Joe. Thanks for playing along today.

Well, I was going to say what's agentic AI first, but does that have to do with the agency?

Right, so. Well, agentic AI is artificial intelligence that has agency. So what do I mean by agency is it has the ability. So whether you're talking about testing or not testing, Right. It has the ability to make decisions and take actions with minimal human intervention. That's what agentic AI is. Okay, we'll apply that to testing. What does that mean? So think about this, right? So if I were to script something, if I were to automate, let's say I'm working to test airline mobile app, right? So what do I have to do? Right? Well, the first test case is booking a flight, right? Let's be honest, right? We all understand the concept of book a flight. So how would I do that? Well, I would first log in and I would tell it how to navigate to that page. So I'd say, you know, click the login button, type, click the login id, type in the value, type in the value of the password, click the login button, and I tell it all those steps to do, right? And then I'd start booking the flight. Well, how do I book a flight? Well, I got to find the from and the to location. And I need to type in the airport name and the two airport name and then I click find flights and I gotta. I tell it all those steps. In an agentic AI, what you do is you give it a step that says Book a flight from San Francisco to New York in business class. Prefer an aisle seat. Second preference is a window seat. If there are no flights available that have one of those seats, I don't want to sit in the middle, right? I don't want to sit in the middle. So come back with an error message and all of the steps that it takes to do that of, you know, finding the objects on the screen, type in the values, think about clicking the seat map to find is it close to the window or is it close to the aisle? How difficult that would be to script. It handles all that for you. And so by going agentic, you don't actually have a script during. At runtime. It takes that natural language prompt, looks at what's going on in your application, and then makes a decision about what it needs to do to achieve that objective of booking a flight. So all of those steps that you would have had to script out, that's probably like at least 50 steps, right, that you would have to script out and deal with all those objects and all those locators, all that goes away. Your actual artifact that you track to and trace to is your test step. So there's no script, there's no framework needed. I don't have to know Selenium or Playwright or Cypress or Espresso or Appium or whatever. I don't have to know all that. What I know is the business process. And because it's making decisions at runtime based on what the application looks like and how to get through it and understand semantics and context. When the app when. Because we all know it's a when, not if the application changes. It just, it doesn't break. There's no self healing involved. It just doesn't break because it's making that decision based on how the application's behaving. Just like as a manual tester, right? If we change our application, my, my manual tester doesn't break, right? He just. Or she makes, you know, just goes the different path. And you can start doing things like find, you know, you can start doing exploratory testing with the gentic AI, find different ways to get to the shopping cart. I. To get to the shopping cart, right? There's like 10 different paths. We actually talked with one customer that was a beta customer, and they're like, we did some of this and we said, hey, here's the 12 paths that you can get to this part of the application. And they said, we only knew about nine, right? And then the other thing is, because it's Working at the user experience level is things that were just untestable before, that you just couldn't automate before, are now automatable. So we have a financial services company with another one of our beta customers. I don't know if we have permission to use their name, so I'm not going to use their name. But think about like a stock trading app, right? And you get the graph and then you can put overlays on that graph of, you know, okay, show, you know, if it's red going down, green going up. And now you can actually write a VAL assertion that says if the point in the graph before was higher than the current point, you should see red, you should see green if it's not. And oh, by the way, down in the chart where you've got the numbers, make sure the chart matches the numbers that are down in the table. Things that you just the way that you automated it before, let's be honest, right? You did static data, right? In order to test that kind of stuff, you do static data. Same thing. Like, like think about a, like a big E commerce company that we were showing this to. You know, they have a picture of their product and then a description. But they, they do marketing campaigns where the description changes, right? Sale on laptops. Right. So every single description says now sale on laptops. Well, they couldn't test those marketing campaigns because it changed the static data that was in there. They'd have to dynamically do that. And oh, by the way, I can write a validation and assertion that says, does the text match the picture? So if the text said HP laptop with a 17 inch screen and a 10 key, it could look at the picture and see, does it have the HP logo on it, does it have the 10 key and the keyboard? That kind of stuff that you just, you couldn't automate that before, right? You just. I know what I used to do, right? I used to do the cheap way out because could I automate it? Maybe really hard. Might take me a week to figure out how to do all this. I just grab a snapshot and then put a warning message in my log that says, hey, whoever's reviewing this, just look at the picture, make sure it's right when all that can be automated, right? It's super excited.

If you can't tell, I'm excited. But you know, there are skeptics. You've been in automation for a while. I've been in automation for a while. The browser has been always highly unreliable. Even I know open tech, OpenAI, all of them. Are coming up with their own browser automation and it's not good, it's not optimal, it's flaky. What makes this different? I know a lot of people heard of visual testing. They heard of image based testing. How is this reliable? Rather than going like at an API level, which I think would be the ultimate goal, but probably can't do that.

Well, there's a couple of problems with going, I'm not saying you shouldn't API test.

No, Right.

I would never say that. Right. Just to be clear, for anybody watching this, I'm not saying don't API test.

Right, Right.

I'm also saying not unit test. Right. I'm not saying that. I'm saying that you need to use your experience test as well. You usually had to do that as a manual tester to get that user experience. I'm going to go on user experience just for a second. Right, sure. Think about accessibility testing. How do you do accessibility testing? I can now do an assertion that says, just make sure that this page matches WCAG 2.0 standards. That's my assertion. And all of those standards, it goes, grabs those standards. It says, okay, is it matching those standards? That's huge. Right. So how is that different? Right. So, you know, behind the screens, what we're doing is we're actually capturing the image and then interrogating the image of what's on the screen. So regardless of which browser it is, whether it's iOS native, web native or mobile responsive, we don't care. Right. Because it's grabbing a screenshot at the time, in fact, I was playing with it when I first started, you know, a whole six weeks ago, I started playing with it and I'm like, okay, so install this app. Like, I picked one of my apps that I like to use. It's for tracking the weather. I'm not using a name of the company though. And I said, you know, if it's not installed, go install it. So it's like, oh, I see. I'm on an Android screen based on what I see. I don't see the app. Let me swipe from the bottom to see if it's in my app catalog. I don't see it in my app catalog. I'm just going to try to do a search first to see if it's in my search, if maybe it's just not. The icon's not there. So it did a search, said, no, it's not there. Said, okay, I'm going to click home and I'm going to click on the play Store and I'm going to search for it. And then it said, okay, I see it. And I'm going to click the install button. Oh, I see that there's a progress bar that's still going. I got to wait. And it waits three seconds. I cut checks again. Oh, the progress bar and the app, I was, it was a really slow to install app. That's why I'm not naming names, because to protect the guilty. And then finally it said, oh, it said, there's an open button. Now I can click open. The thing about how hard that would be to script today, I got to do a loop waiting to check the state of it to until the open button shows up. I didn't have to do any of that. I just said, hey, open the app. If it's not there, go install it. And it recognized. Oh, I was in. I was on a Google device and not a. I was on an Android device, not on an iOS device. I knew I had to go to the Play Store instead of the App Store. All that kind of stuff that I would have to script. Right. That sucks. To script. Right.

Some people like scripting. They just like to script. So the people that love to scripts, would you say to them, like, their jobs at risk? Like, how bulletproof is this method?

So I would say this to the people who love the script. Yeah. One, we're not saying replace your script if you have a bunch of scripts that work. The old adage, if it ain't broke, don't fix it. We. You can make calls to us from your framework of choice to fix that one broken area that you have that you is always causing you problems. Okay, so one, that's number one. Number two is I'm going to say something controversial. Are you ready for it?

Okay. Yes.

Some of the best testers that I've known in my many years of my career are the worst scripters. And conversely, some of the best scripters were the worst testers because they didn't have that destructive mindset. Wouldn't it be amazing if I could have my best testers be able to do automation?

Yes. Because they usually are the business experts as well that really know the application. So it's not just randomly creating scripts. You're like, yep, all right. They actually know what it is, what makes sense to help drive it. Yeah.

And to those scripters who are really good scripters, wouldn't it be amazing if they could just focus on the API testing and the load testing instead of having to deal with these stupid UI elements that are constantly Changing. Have you ever tried to test Salesforce Lightning? It's horrible. Horrible to try to test from a UI perspective because it's. Everything's constantly changing.

Yep. So, Don, for the people that don't know, you said it's image based.

Sort of.

And I know Perfecto has a great cloud type of environment. Like it has a lab.

Yes.

So it sounds like they could write the test once and they could easily just run it on all the things and not have to worry. Oh, I have to separate tests for this extra logic for that. Is that how it works?

Yep. So it's part of Perfecto Mobile. Okay. So all those features that you know and love in Perfecto Mobile. Well, at least I hope you love them because I work there. I'm hoping you love them. If you don't, here's your chance to love them. How's that? But you know, all the different flavors of mobile devices, all the different flavors of browsers, and you know, X number of versions back of browsers on your lab, you know, Safari on Mac, all that stuff, you can script at once and because it's at runtime determining the best way to go through that. You think about your application behaves differently from web than it does to iOS native and Android native. Right. For example, you usually on the web don't have a hamburger menu. Right. You have a different kind of menu that's usually a. A bar across the top. Well, that's now different objects and I have to handle differently. You know, if I'm using Selenium, then I'm, you know, switching to, between Selenium and Appium, or maybe I'm using Espresso or whatever I'm doing. Right. So now instead of having multiple scripts that do the same business process, I've got one, one test. Not a script, a test. Because I'm just doing test steps in plain language. Notice I didn't say plain English, I said plain language. How many languages do you speak, Joe?

Fortunately, one.

Yeah, me too. Me just one. But would it be amazing if, you know, those teams that I've got, you know, around the world, as we follow the sun, could write their tests in their language of choice. Now, we don't support every language that's out there. I'm pretty sure we don't support Navajo.

But it's AI. Why wouldn't you support all the languages?

Well, because the AIs don't, let's be honest, the LLMs don't have every single language out there.

That's true.

Right, right, right. So most languages how about I would say probably 98 to 99% of the languages out there we support. So for example, we did this, we were doing an event in Malaysia, so we decided to do the demo on Malaysian airline. And I've got a video for this, I'll send it to you.

All right.

And we basically said, you know, book a flight from KL to London. Okay, well what's KL mean? I didn't know until I thought about, well, what cities are in Malaysia. Oh, that's Kuala Lumpur. Okay, obviously. Right, obviously KL in this. But think about how impressive that is that the AI was understand. Able to understand that context because it said, hey, I see you're looking on the Malaysian Airlines site. I'm going to assume that you mean KL is Kuala Lumpur. So I'm going to book from Kuala Lumpur to London. And you know what, I'm going to put you in first class because you didn't specify what class of service you wanted so that you can sleep on their flight. Right. And did all this stuff. And it's like man, I to script that, you know, what used to take me days is now taking me minutes to script.

Or don. It sounds like magic. So that's funny.

This other person that you know really.

Well I know said the exact same word.

He said this magic thing.

So what could people really expect? What happens? Is it 100%? Because I've used like playwright, MCP, server from cursor. And I do the call, it does its thing and it still takes me 15 minutes maybe to get up and running to do what I need to do and actually work. And it's still kind of not 100%.

You learn really quick.

Yeah.

That sometimes your plain language step isn't terribly descriptive. That's what you learn. And you learn to be descriptive on your step. Right. So there's a lot, you know, you think about. What I said is, you know, book a flight from KL to London. Right. That's what we said. A one way flight next Monday. By the way, I said next Monday. I didn't say what date. I said next Monday. So it's got to know what date it is and what next Monday's date. Anyways. So it made a lot of assumptions in there. You know what class of. So I talked about, you know, class of flight, you know, do I want a window or an aisle seat or do I not care or whatever that case may be. So you start learning. Oh, you know, as I'm looking at the results and I can see it tells you this is, this is what I see on the screen. This is what your instruction set was. This is the assumption I'm making and this is what I'm going to do. So you start going, oh, well, I didn't want it to do that, so I changed my prompt. So you learn to do better prompting it. So if you've never done any prompting before, you're not going to be as efficient as somebody who understands the concept of prompting.

Right. And a lot of people blame the tooling rather than the prompting because I actually had that issue with the playwright. I said, do a search for this to find. I was looking for stats for my podcast and it did a search, but it didn't do search in the right area. So I had to tell it because I didn't tell it.

Yes.

I had to say, no, go to Episodes and click on that search and do the search there. So it did a search, but it didn't do search because I didn't give it enough context. So it sounds like, yep, you know, that's. It's not the tool.

So you take that prompt.

Yep.

The big difference between what you're describing and what we're releasing is that what you're describing creates a script. Right. You go through this, prompting, these iterations, and then you have a script.

Yep.

And now that script is now going to be running on your, your podcast or your website, right?

Yes. Right.

And you make a change. Yep. Now the script's broken. Okay. Even with self healing, I now have to go in and interact with it with self healing. With self healing solutions, they say, hey, I noticed your script broke in this place. Here's what I want you to do. Do you want me to do that? I have to interact with it, with our solution because at runtime, I'm taking that prompt and executing against that prompt instead of a script is your app changed? And I don't care that it changed. I'm just going to. As long as you can figure out how to navigate through there. Right. If you tell it to log in and somebody removed login from your, you know, the login process from your application, guess what, your script's going to fail. And that's a true failure, hopefully. Right. Hopefully. You didn't purposely run flogging.

Right? Right. So that's another I could see. Not roadblock, but another objection. Or someone could say, how do I know it's really doing what I think it's doing? Or it's saying it's doing, or, you know, if it's doing healing, self healing, A visual like how can I trust it? Those type of objections.

Well, that's why we take screenshots and actually have videos of it playing as well. So you can go back and watch it. If you don't trust it, go audit it. What you're going to find is your audit level is going to go way down as you build trust with it. And now I found bugs. Yeah, I have a great example of I was staying at a hotel last week and I have a password manager on my keyboard and I use a different keyboard than the OS keyboard. And on the application itself, I couldn't see the chat where I type my values. Well, if I told it to type my values, it's not going to see it either. Well, that's because there's a bug in the application. Right. So you have to tell it to handle that differently. Like tell it to collapse the keyboard because the keyboard's in the way. But some of those things are, you know, if you can't see it on the screen, it's not going to see it either. Now it'll scroll as well. Especially if you tell it, hey, you know this is a large form scroll so that you have the most, you know this is part of my prompt, right? Scroll so that you have the most fields on this large form visible at one time and then type all the values at once as one step. Right. Instead of type this, take a screenshot, interrogate it, type this. You know, I can speed it up based on how I'm prompting it. Can affect the performance of it. And by the way, I know I can see it in your head performance, right?

Absolutely.

It does not perform as fast as doing a straight Appium script. Absolutely.

But it's more reliable. This is a trade off. So it saves you time. It's more reliable, faster to script debugging, triaging, the whole. Ugh.

Doesn't break well. Well, if your application breaks. I'm sorry, that's what the test is supposed to do, right?

Yeah, exactly.

If your application breaks, you want it. You want to your script better.

Exactly.

So newsflash. If your application breaks, your script should fail.

Yes. You heard it here first. That's a big.

Yeah, you heard it here first on the Joe Colantonio's test Guild.

Hey.

Yes.

All right. So I'm trying to think of other things people might have an issue with. So you kind of just, just went over really quick. You said you had a customer and they gave you 10. You gave them 10 paths to do something they only knew of five. So is this like, like a spider. Then you just say, go to my website login, do blah, blah, blah, and it's able to find maybe areas of your code that don't have tests for. Like, what are the functionalities that this can give you that people may not think of right off the bat?

So it's how inventive and creative and destructive can you be with your prompt? Right. So this is why I was talking about going back to tester versus scripter. Right. I want to hire people that have this destructive mindset and this inventive mindset that are really good testers that can think of all the different scenarios to go through, that think about exploratory testing. Right. So wouldn't it be great if I could start automating at least some, if not all, of my exploratory testing? Well, when you are doing exploratory testing as a tester, you have an idea of what you want to do to be destructive towards this or try to break it. Right. So instead of just doing that, write the prompt to do that. And now that exploratory test is now automated. I could do an exploratory test of find, you know, figure out all the ways that I can get, like I used earlier to get to the shopping cart. Right. So you think about an E Commerce application because I use that example, because we all understand it, right? How do I get the shopping cart? Well, usually there's the shopping cart button at the top, right. That's the easy one. Right. Well, I can search for a product and there'll be a shopping cart on the bottom as well to add it to the cart and take me to the cart. Or, or I can just add to cart. Well, that's way number two. I can look at my history, my search history or my order history and potentially get navigated to the cart that way. Right. So all these different ways, Right. And so if my script. Sorry, I did it. No scripts. Right. Just say no. Just like Nancy Reagan, just say, no kids. No scripts, no tests, no scripts, no frameworks, no maintenance. That's our tagline, right?

Is it really?

Yeah, it is.

Oh, you just made that up. Okay.

No, that's our tagline. No scripts, no frameworks, no maintenance. So I'm going to be doing. I'll be talking about this at StarWest as well. Where I'm. Where I think I'm going to. I haven't decided for sure, but I think the title of my session is going to be something like Selenium Cypress. Playwright. Oh, my. No frameworks. With agentic AI. I don't know, something like that. Right. So something to try to. If you can't tell, I try to have a little fun with this too.

Right, right. Yeah. So, you know, I know Perfecto has a lot of built in functionality. You mentioned accessibility testing. If someone does a prompt, do they get extra benefits as well? Will it automatically do like accessibility checks or security checks or high level performance checks? Like, hey, this was slow. Like, does it add anything on top of it other than maybe you actually physically having to prompt everything?

Well, in the initial release, it has to be part of that individual prompt. Right. Okay, so what I, if I were operationalizing that, you know, I was implementing this, what I would do is I'd have a certain set of prompts that I would put in for everything, do a spell check on the screen, check WCAG standards and do a context check on the screen for the natural language. Right. So if somebody typed massage instead of message. Right. Well, that's not a spelling error, that's a context error. Now, what we will be releasing in the future, in the. I don't know what you consider long or short term, but in the future you'll be able to set those as essentially policies for the script. Right. I want to do, on every step, I want to do WCAG standards.

Does it know what WCAG standards are? Or do you have to have a prompt and they're ready to go? How about does it know? Give me OWASP top 10 security risk and blast it.

Sure. Right. Whatever that is. Right. So you're behind the scenes, you're prompting an LLM with that text. Right. To interpret that text. Right. So if it's a standard like OWASP or WCAG or whatever that is, you know, I don't want to say globally known, but well known that the LLM will know it then. Yes. If it's your own personal standard. No, you're going to have to define that standard. Like branding standards. Right?

Yes.

How would you automate brand compliance? Is this the right color? Red? Right. I worked at a bunch of companies that red was one of their primary colors, but they're all different shades. Right. Is this the right color Red? Right. So I could just automate that and say, hey, make sure this is the right red.

That's awesome. Because I used to be a part of companies that were acquired and you have to change the logo and you have to check everything. This is pretty cool. It could do it for you. Very nice.

Or think about, you know, hey, let's say hypothetically, because this would never happen to anybody that watches your show. Let's say, hypothetically, you had to test it in a different language than you speak.

Yes. Right.

Like, for example, I took three years of French in seventh, eighth, and ninth grade. That was a few years ago. I don't speak French too well. And I worked for a company that we had a business unit in Canada. So it had to be bilingual. Right. So they asked me to test it. I'm like, well, I don't know. It might be right. I mean, the objects are there. I could tell you the objects are there. But are they spelled right? Are they have the right context? Right. Are they using formal versus informal pronouns at the right times? Dude, I don't remember any of that stuff from French.

Yeah, I use this example all the time. I used to work for a company. They used to have Excel files of all the UIs and what the wording is, and then you have to get it officially okayed by some localization company. And then you do the test and you look at the file. This is even better because I guess you could tell if a screen. If the words go off a screen for a certain language or.

Yep.

You know, it could do that all for you. And that's awesome. Right? You could just say, hey, test this for French, see if it's correct. Nice.

Exactly.

Love it. Love it.

So, Joe, sounds like you want to work with us. You want to work for us now, right? Because now you're thinking about all the other. I mean, it really is. It's a paradigm shift in test automation. It really is. Right. So I had. I come on your podcast, what, eight years ago, seven years ago. I don't know, when we talked about computer vision and how that was paradigm shifting, right?

Yeah.

And using computer vision and AI, this is equally. If not, I think it's more paradigm shifting because it's using computer vision and it's using natural language processing, and it's using LLMs altogether to do this for you.

It's.

Joe, why don't you come watch it? We'll sit down and do a session together.

Well, Don, what's even better is I believe Perfecto is doing a webinar with us later this this month on July 3rd. It's called Perfecto AI in Action. Smarter, faster, zero hassle testing. Is this going to be what you're demonstrating, or is this something else?

Absolutely right. So I'll be on there myself and our head of product, Steven Filoni will be on there. And this is exactly what we're going to be talking about. We'll be talking about it. We're going to show it. I'm thinking about, you know, doing kind of a stump the chump type scenario and just prompting the audience say, give me a, give me an app that I can go download and we can try something just to show. Right? It doesn't matter what the app is. It doesn't matter. I'm just going to go in and do it.

And we love skeptics. So if this is you, you don't believe it, it sounds like magic. You could definitely register for that webinar down below or contact Don directly to see this in action for yourself.

Awesome. Thanks Joe for taking the time today. I'm super excited. Look for the press Release on the 15th. We'll be talking about it. We'll have hyperlinks in there too so that you can do a free. A free trial on it.

Thanks again for your automation awesomeness. The links to everything of value we covered in this episode. Head on over to test guild.com a554 and if the show has helped you in any way, why not rate it and review it in itunes? Reviews really help in the rankings of the show and I read each and every one of them. So that's it for this episode of the Test Guild Automation Podcast. I'm Joe and my mission is to help you succeed with creating end to end full stack automation awesomeness. As always, test everything and keep the good. Cheers. Hey, thank you for tuning in. It's incredible to connect with close to 400,000 followers across all our platforms and over 40,000 email subscribers who are at the forefront of automation testing and DevOps. If you haven't yet, join our vibrant community@testguild.com where you become part of our elite circle driving innovation in software testing and automation. And if you're a tool provider or have a service looking to empower our guild with solutions that elevate skills and tackle real world challenges. We're excited to collaborate visit testguild.info to explore how we can create transformative experiences. Together. Let's push the boundaries of what we can achieve.

With lutes and lyres the bards began their song A tune of knowledge, a melody of co through the air it spread like wildfire through the land Guiding tester showing the secrets to behold.