Balancing Speed and Quality in the AI Era with Jim Trentadue

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 on our way to Testing Podcast.

Hey, what if I told you that the biggest threat in your QA career right now isn't AI replacing you, it's you ignoring AI. In today's episode, I'm sitting down with Jim Trentadoo, a 28 year veteran of the testing world, to uncover exactly how testers can thrive in this new AI powered era. So we're going to talk all about why testers who survive and succeed are the ones who actually adapt. What skills you must add to your testing toolkit today, and how to balance quality with release speed in the age of automation. And we'll also dig into a controversial question. Did we make a mistake turning testers into developers? This is a conversation packed with career changing insights. So stick around all the way to the end because we have a huge announcement as well. You don't want to miss it. Check it out. Hey, Test Guild community. Before we get into today's episode, I got something special to share with you today. After years of connecting with you through podcasts and online content, I'm finally doing something I never thought I would do. Hosting our first ever Test Guild IRL event. That's right, in real life. But here's the thing. This might be the first and last time I do this, depending on how it goes. So if you've ever wanted to meet me face to face, network with other top QA professionals, or learn cutting edge AI testing strategies in person, this is literally your only chance. We're keeping it intimate. Just 75 seats in Chicago on September 18th. I've got Jim Trentedou joining us to share how to balance Sprint delivery speed with deep, effective testing using AI powered techniques. We're also going to talk real strategies you can use the very next day. No fluff. Plus, there's going to be a live expert panel where you can ask those tough questions that keep you up at night. And yes, there will also be food, networking, and even a raffle. But you have to be there to win. Look, being an introvert, I'm really putting myself out there with this event. It's free, it's exclusive, and honestly, I'm nervous about whether people will actually show up. But that's exactly why you should be there, to be part of Test Guild history. Whether it's the beginning of something bigger or a Beautiful one time experience. Heading over to test Guild Me IRL and grab your seat. Only 75 available. And when they're gone, they're gone. September 18th, Chicago. Don't let me be that guy talking to an empty room. But seriously though, I can't wait to meet you in person. Let's make this one count. Register now. Use that link down below. Hope to see you there. Hey Jim, welcome to the guild.

Hey Joe, thanks for having me. I'm finally big fan and I'm excited to be on for the first time. So thank you.

Yeah, you know, I'm excited to have you. I've known you for a while, I've heard your name for a while, but we actually first actually physically met I think in Star east this year. So. You've been around a while though, Jim, so I'm surprised our paths haven't really crossed before. So a little bit more maybe like how you got into testing.

I was a marketing analyst. I started messing around with an application because I was annoyed on how much it was breaking and I talked to developers and this the late 90s, I started talking to developers. I'm like, why don't you just turn it over to me before you go to production? I don't know, let's. Let's do like a little testing phase and just give it to me and let me play around with it before. Before I. You actually go to production. Oh, so like a little testing phase. I'm like, yeah, I guess if that's what you call it, you know. And I had no idea it was like a formality of a industry. Then I started them. Like, I kind of like this. I kind of looked around and saw some contracting jobs. I'm like, people actually pay people just to sit and break things and test. I'm like, that's amazing. I mean it was an amazing concept to me. When I got into it like that people were paying to for me to actually test. And then I walked into it and I didn't know how big of a career it was. I mean I. All I thought was give them an app, click around. No formality of test plans, test case. I knew nothing of that. So it was just fun playing around.

Nice. How'd you learn?

When I left my job, I went over to a company called AC Nielsen at the time and they had a really formal, formal group of folks. I learned from two of these two ladies and one of my manager who taught me everything and I'm like, I realized what I didn't know and so I learned about Some automation. One of the things they did with me that I loved and I recommend for people coming in, I knew nothing about automation. They sat me down in the lab and just analyzed the automation runs from the night before. That was every day. That was half my time just sitting and analyzing that like any of the API runs, any of the, any of the UI runs and see where the failures were. Go talk to the developers, see if it's a bug. I started just playing around like that and then they showed me the formal way to write test cases, to write some test plans on how to go about a given release. So I had some really good mentors that really helped, like show me the way. Because I knew I knew nothing about nothing, you know, almost this is going on about 28 years ago, but I knew nothing about nothing. So, you know, I think I was fortunate enough to have a couple, a few good, really mentors that took me under the wing. They saw potential in me, but they kind of helped mold it out.

Love it. I think you've been giving back as well. I think I read somewhere you're mentoring students in the University of South Florida. So what's that like, what advice do you give them then from your perspective now being now the roles of change? You're the mentor.

There's a class, a software testing class and from a professor named Alan Hevner who's you know, very thought leader and now he's doing an AI class. And it's a lot of kids who are trying maybe their intro into the, the industry. They may have a job as like an analyst or senior analyst and they're taking a master's class in software testing. So it's really helping them kind of, hey, what tools, what kind of open source can I start looking at? What kind of where, what other skills can I harness to really, you know, bolster my marketability? So it's, it's been a lot of fun with that and you know, especially, you know, and I see the same with a lot of the consulting companies that I work with, you know, some of the Infosys, tcs, Wiprose, Cognizant. It's really kind of working with some of those folks like as well. They'll bring on some junior level people and we try to help give them some guidance as well.

Nice. All right, Jim, So I'm just curious to know like, are there any themes you see especially for the younger generation coming up now, especially with the role of AI being hyped more and more within, around the world basically, I think.

This generation coming out of this newer generation of testers coming out, I think they've got a huge potential here and I think it's learning AI both agentic and prompting to bolster their software development and software testing capabilities. So it, they have to have that as part of their toolkit. Like it's a must now for them to have as at least part of their toolkit. I think this is where they're going to be able to really shine and go through to show, hey, you know what, look, this is what. I've done this with Selenium, I've done this with Cypress Playwright, but I've also, I've helped AI has helped me build some framework components in here and it's also helped me identify some other areas as well that I need to be testing. So when they're learning that alongside with what, you know, automation skills they have. You know, it's funny as we say this because some of these AI, right, we're talking about coding. I don't. Coding going away, right? And this vibe coding, I don't know if it's ever going to replace the need for strong coding skills and understanding because I think more than ever, I think some of your peer reviews and code reviews need to be stronger. Right? You've got to understand what output that your AI is going to be generating. Is this a good structure? Is this a good foundation? Is this class good? Is it a. Does it actually utilize my. If it's UI automation, my page object model? Well, is it doing things as, as efficiently as possible?

Yeah, I definitely agree there's probably going to be a lot more AI slop generated and I think it's going to make maybe I'm wrong applications less secure and less performant. So it's almost like testers need to increase their role into knowing more about security and performance as well. I'm not sure if you see anything.

Similar along those lines or not 100%. You know, I'm reading about some, you know, I've taken some, worked with security teams to learn about some penetration testing. This is prior to AI. Then you learn about some of the security vulnerabilities that are stored in like Docker containers and Kubernetes, like how they can. These can mask themselves in just a container and just kind of ride along to almost take the bus ride into your code. AI, like, it's one of those things where I don't even know where the AI security starts, you know, And I think that's a lot of us where we're trying to still learn where are those security layers in? Is it something that you're building into your rag? Is it something that is kind of fire all that your LLM? I'm like, where is that? I think we're still learning that. But I did work for a couple companies that really, if you wanted any kind of AI, even poc, you wanted to do with a vendor, you wanted to do with, you know, ChatGPT or Copilot Gemini, you had to have such security clearance because, you know, much more than onboarding a new tool. A new tool like, hey, all right, what kind of ports do I have to open? What kind of firewall exceptions do I have to have? What kind of VPN access? Very standard and vanilla stuff. But this AI, I think it's going to be. We're still trying to figure out where the security and vulnerabilities are and that's a little scary. But I'm confident we have such a strong. There's so many certified security analysts out there and they're coming out in droves and they're going to learn this and we'll be ahead of that. I just don't know if we're there yet, but I'm sure as an industry, we'll get there.

Nice. This might be controversial. I think we got things wrong. I don't know if you heard that mantra. Oh, testers, the developers too. And it almost like they took the focus off of testing, you know, being subject matter experts and more as developers. And a lot of these AI tools are doing a lot of the things that you would do as a developer, but not necessarily the, the testing expertise. So any thoughts on that? I think we're all need to become subject matter experts again or business analysts again because that's really the value that we bring. If AI is really going to be the hype of creating all this code for us too.

100%, you know, remember automation itself. So let's step back a minute. Automation is going to replace all the manual testing jobs, right? Right. So that hasn't happened and it shows the need. Now there's people that have helped really lessen the gap. Just take one step back in like historical time. There were tools out there that you and I grew up with. Rational robot, Windrunner, empirics, you know, segue. So some of these tools that you needed, you needed to have a coding background. One of my favorite, and I got to meet her at Star East. One of my favorite heroes in the QA industry was Linda Hayes, who came up with a whole keyword driven approach. You know, there were models that kind of brought it along to still bring manual testers in to say, even though I'm a manual tester, I don't know code, but I can contribute to automation by learning these keywords, you know, and we helped bridge that gap. Even the automation engineers. I'd say most organizations that I've seen at least they still require some level of manual tests to be at least available or scenarios before I go right into developing code or developing a coded solution for my tests. Do we need that necessarily? I don't think. I don't know if we do all the time. But I do think it's helpful to have some kind of framework that shows, all right, these are at least the scenarios that you think you're gonna, you want to test from a negative, from a boundary, an equivalized class, like these are ones. And I can hand it over to an automation engineer that say, right, these are scenarios I want to do. Help me build that framework that can support this.

Absolutely. So, you know, you did say automation's not. The promise of automation was it's going to replace manual testers. It never took off. But I did see it replace testers that didn't embrace it. They just dug their heels in and said, I'm not learning any automation tool. Because it didn't. No, it slowed them down. So someone that knew testing and how to at least use a tool seemed to have better opportunity. I think it's the same exact thing with AI. I know a lot of people saying, no, it's. This is a different case, but I don't really think it is. Maybe I'm wrong. I think it's testers that don't replace, that don't embrace AI. At least learn what the hype is so they could talk intelligently about it, what it can and can't do to the management, probably in jeopardy.

I'm with you, with you 100%. It's a newer way of a technology that could threaten people who want to dig in their heels. I couldn't agree with you 100%. I agree with you because automation, same thing, dig in their heels, you know, and I'll, I'll even split it off to say, well, API automation, well, you're not exercising the ui, but your business logic is stored at the API layer. And those who dug in their heels to say no always need a visual representation of our test, you know, and it was a continue. Yeah, this is a little different feel, but in the same family of what you're saying the same concerns. If you dig in your heels and say I'm not going to use it, then I think you're going to find yourself in a different industry. I ask this to those why wouldn't we want that? Why wouldn't we want to see technology evolve us to be something better? I challenge those testers to say, do you really want to do regression testing even if you haven't automated it? Do you really want to do just basic user story implementation all the time? Or do you want to put your true, this is allowing you, if you embrace us, to put your true creativity to the testing aspect on display?

Yeah, it makes you be a true tester. Right. Because it's generating all this stuff. But you need to have the knowledge of the application in context and actually challenge what it's giving you. So it's almost like you said, you can come up with all these ideas, give me this. But you're the thinker that has to say, okay, is this right? Is this wrong? And I've been doing some vibe coding just to make sure I'm staying up to speed. And it's great until it's not. It gives the illusion of being awesome until you start digging deep into it. And you know, I wouldn't have that confidence now if I didn't stop messing around with it. And I think testers need to at least start doing that so they could say what's it doing? What's it not doing? Rather than just taking like a guru's thought on you should it's going to replace you. Or even gurus that say it's garbage. You have to try yourself. I think.

Yeah, Joe, 100%. I mean it's. Yeah, try it. I mean look at, you know, you've come from, you've probably come so from some background as well as me where at one day in time object oriented programming was new. When I actually think, you know, and I say this to the, I don't want to say the more experienced, you know, some of those who are coming in, they have a chance to put AI as part of their toolkit right away. But I think some of those who have been around the industry for a while, this is a great opportunity as well because you've seen this, you've seen this shift in waterfall to agile. Like that was a big change, right? If we really think about it, like what is this agile thing? Like, what are you talking about? Sprints? Kanba. What? You know, there were these things. So we've seen this is another evolution. And I Think the experienced, I don't want to say the older generation, I'll say the experienced generation, they embrace this because they've gone through so many changes, you know, with automation, with software developments. They've seen all this. And even the whole concept of like from procedural to object oriented programming, that was a big shift too. So this is just another big shift that the experience generation, this is just another one that you're already used to.

Absolutely. I shouldn't say this. It's almost like people that have experience have a leg up now, I think because we understand testing and we, I don't know, like, because people are looking. I think AI could probably replace really low level things that probably an intern or a first fresher could have done. And then they don't get the chance then to get that experience where we've already gone over that. Humphrey, once again, not sure if that's true or not.

No, I agree. I think it's going to be a little combination. Like if you're coming out of college, I mean, honestly, you graduating with a computer science degree, you're 4.0 GPA, right? Regardless of where you go, you're probably going to be put on the prod support team. You know, as soon as you come out of college, you're probably going to be put on the pride support team. Help fix these medium level priority defects. Not even tier 1 or tier 2 is right. Fix these medium priority defects and then we get to see your coding style and everything to make sure that you're following our framework. Okay, now we're going to start to give you higher level and then maybe we'll put you on the sprint teams, you know, and that's okay. You got to earn your stripes. I do think that the experience generation is going to have a little bit of a leg up on that. Only because I think they've seen all the dynamics and shifts of the industry so far. So this is one, but this is my. And I think you're saying the same thing. We're advising this younger community to come in and say, just walk alongside it hand in hand with what you're learning. You're learning Python. If you're learning that in Pytest or playwright, you know, whatever ide that you're really comfortable in. Marry that with, you know, your AI kind of capability.

Yeah, they should be embracing it because if they can then go to management, say, hey, not only dino testing, I got out of college, but I know AI, I'm like an AI first generation. Really embrace it full force. I think that'd be helpful as well.

I think there's some of it, you know, just speaking on AI and you know, look, I've watched webinars, I've watched people talk about AI. Like when we talk about operationalizing it, I really don't think that we've truly operationalized it. I'm sure there's people bobby out of this podcast saying no, no, no, I have, I have Mike. Well, okay, so to me when we say operationalizing AI, that means I every sprint and I'll put it, I'll focus it at a sprint level because that's where all work is done, right? Every sprint it is clear like how much we know the velocity and how much AI you know, tuning is going to be needed, how much re editing and how much prompting is going to be needed. We know that velocity every single sprint. If not, I don't know if we're, if we can truly say it's operationalized. You know what I mean? I like right now using that just a standard Fibonacci sequence, right. You could estimate a story points of like the 1, 3, 8, 11. You have a good idea on how to estimate on your story points to give an idea of how big that is to test how big that is. So your Scrum master or nose. I don't know if we've done that with from an AI perspective. I don't know if you've seen any other guests that have said that because I talking around the industry, I haven't seen that yet. It's coming.

So what do you mean? Like because we don't have enough knowledge of AI how much effort it's going to take. We can't really estimate better in our sprints.

Yes. On a regular basis on a truly consistent you as my Scrum Master, I don't think I can give you every sprint. I know how long the AI is going to take to generate. I know how long my AI is going to take for me to edit and review to make sure it's good. I know how long it's going to be to add in my additional scope that maybe this AI missed out and I can deliver on this sprint if I can answer those three questions to you seamlessly. I don't know. I haven't seen it where we're there yet.

So interesting. Jim. I don't know if this is related. I saw an article I wish, I wish I prepared for this. I would say we were almost going back to waterfall because in order to use AI we need to have the requirements up front Everything needs to be stated effectively so everyone knows what they're building. It's not just these little sprints at least until we get AI savvy to go back to Agile. I don't know if that's the same.

Thing or not, but I'm sure I'm going to have people think I'm insane. I never minded waterfall. I thought that some of the change control aspects if we could have handled change control aspects better. But it really gave us a mission. And I think there's a lot of companies still do an agile ish, you know, and still has waterfall components. And how long is at Agile's been here? What 20 years?

25. 20.

25 years. Yeah, exactly. So it's been around. But yeah, you're right. And then there's, I think there's a lot of experienced folks that are feeling I'm not there with AI, I'm just dabbling around and I think a lot of people are feeling behind. Right. It's almost to tell people you're not behind. It's just we're all learning this together. It, I think it's just interesting. We have a lot of people presenting like how they do this. I'm like, you have a field study of about two months and we're doing, we're doing presentations on how good we are with AI. I'm like, you know, I've talked to some really thought leaders and big names in the performance testing and you know, I won't name their names but they've been plenty of times guests on your show multiple times. And even when I just sit and talk with them, like I haven't really, you know, I haven't spent a lot of time and I have a ton of respect for some of these folks like as automation architects and performance architects. They're folks I watch as well, you know, and just like all of us, I think we're learning this together.

Yeah, no, I agree. I mean this is once again I shouldn't say this. I think it was almost better when it was waterfall and I was the only person doing automation. And we had all these business analysts and testers that knew the application and they just focused on testing and then I took whatever they had, the test cases and I automated it much better then going in a sprint. I worked at a company that had eight sprint teams, six to seven people on each team, everyone contributing to the effort of automation. It was all garbage, it was all baloney and it was in a regulated environment. So it's almost like I can almost see AI taking this approach where we're kind of using that old model almost to start off again.

Yeah, agreed. And you know what, let me add another complexity on that. When we're talking AI, what are we talking? Should we go agentic? Should we go prompting? You know, and that that leads a whole nother field of area. And I in my mind, you know, I've been evaluated and I'm working on different projects where I'm looking at between the two. And then I finally came to a light. I'm like wait a minute, why not have a marrying of both? Like why don't I have. I'm kind of putting it in my mind where the agentic AI is building like 80% of what I need to do. Let the agentic take over. Like this. Exactly what you were saying the intern. Low level stuff. Run right through low level stuff. And maybe the stuff that it missed, not blame it to say or not put criticism on it to say it missed, missed 20% but it got 80. And now I can use my thought process. My brain is the one that's putting it into the prompt engineering and what are some good context. What, how do I, how can I build that out a little better? Basically it's just, it's relying on my knowledge and that should give comfort to people. Prompt engineering is relying on your knowledge of the system of the application. It's just clearly articulating in a prompting fashion. And then if we can take that prompt output, feed that back into the agentic AI. This is all theoretical. I feel like Sheldon Cooper on Big Bang Theory. This is theoretical physics. You know, this is all theoretical in my mind. But I, that's what I'm going to try to work on a model to almost say agentic do the heavy lifting, prompting whatever was missed. Let me put my key thoughts in there. Get that prompting output back into my agentic to build. This should be mostly it. I should have pretty good feel of quality because not only did it read and try to transmit all those stories, but it also took my input in a prompting fashion. That's what I'm gonna try. I don't know, we'll see if it works. You know, it's like all of it.

Absolutely. So Jim, it's a lot to talk about and get in in a half hour. So that's why I'm excited to make this huge announcement. I think AI has changed a lot of things. And one thing maybe I'm wrong. I think it's going to push people more to craving real world experiences again. And this leads into the big announcement. I saw you at Star east and I gave you an. I said, hey Jim, I've been thinking of doing this on site thing probably. I've been thinking about it for a year and a half. I'm not going to do it. And you actually forced me to do it. So you actually helped put me together one of the first ever Test Guild in the real, Real Life event in Chicago happening next month. So really excited about this idea. Why do you think real QA community events can help testers nowadays, especially in the age of AI?

Oh, we're back. And Joe, your community and what you provide to the community. You know, everyone, this is an unplayed plug, but I've been following Test Guild for a long time and I think what Joe has provided to the community. I pulled Joe to the back table aside, we had to talk. Mike. Joe, it's time to take this live. People want to see this. Like this is you bringing this to the community. I think is going to be outstanding. So now we get to talk non AI for a second, which is great. People are ready for live events again. People are ready to do. You know, I think you showed. I can't remember anyone else pre Covid who had a successful online system like you did with the Automation Guild. I don't now. Everyone's done it because of COVID but you were like saying, hey, you know what, I can do this. You can do this on your own time. But I think this is branching out, showing this. We're going to be going to Chicago September 18th. It's just going to be brought a live Test Guild event, you know, and in person. I have a presentation to do. Joe's going to be. Joe's going to. I'm going to talk about balancing thorough testing with the speed of releases and the speed of sprints. How do we, how do we capture that? Joe's going to be talking about the future of the test. Joe, I'll let you talk about what you're going to discuss.

Yeah, I'm going to just bring up maybe some observations I made and I speak with a lot of people on my podcast about what is AI, what's it really doing and how people can prepare for it. So I'm going to give some key insights on some, maybe three or four key areas they should be focusing on to really help them with their career going forward in the age of AI type deal.

And I think you talk to so many vendors, you talk to so many practitioners. You know, some of the. I give a Lot of credit to these vendors because they're looking on how to build this, so they're having to do a lot of research. You're working with these vendors to get some insight into that. I, I think you're going to offer to this Chicago community, or even if you're ready to fly in, I think you're going to offer insights that you're not going to hear anywhere else. So I encourage everyone, get out there, get to this event, you're going to start to see it promoted and the webpage is going to be available hopefully later today, very soon. So we're very excited about doing this. You know, like I said, we're going to have a couple of sponsors. It's going to be also an association with the Chicagoland Quality Assurance Association. So it's going to be, you know, we're going to be very, very happy with this and it's just going to be a great event for Test Guild.

And I just want to remind people, I'm still a big, big online guy. We will always do Automation Guild. That will be the flagship all online for around the world. I'm just dipping my toe in here just to see if I can expand a little, maybe meet people, because I've been doing this for 10 years with the Automation Guild, little more face to face. I'm very much an introvert, so this could be the last or the first of many, depending on how many people I can get to churn out and how well I actually do in the real world. So we'll see.

This will be the first of many and Joe's done that great. And I'm the other side that I can. I'll get a wall to start to talk back to me, you know, and I'll have conversations with, we'll strike up everything. So I think, you know, this is going to be great opportunity just to just bring it to community and so, you know, to the Test Guild community, I ask you to show up, show out, show Joe that this is worthwhile doing, because I'm, I'm convincing Joe that we want to do this again. So the only way I could do that is the proof is in the pudding. So I ask you, Community, please come on out, support this first ever. It is a free event. There will be food. So this first one is sponsored by Lambda Test, so we want to thank them as well, you know, providing some of the insights. We're going to have three different things going on there, guys. We got presentation, we're going to have my presentation. We're Gonna have Joe's presentation. We're gonna have a panel discussion where we're going to have some key leaders up there asking. We are going to have some food and we're going to have a raffle giveaway. And it's free.

And Jim, I think it's important to mention, yeah, it's free. You also created some space for community so people can interact with one another as well. So it's not going to be bang, bang, bang, pitch, pitch, pitch. Me and Jim not pitching anything. We are sponsored by an awesome vendor. And like Jim said, I love vendors because they stick to a lot of companies, a lot of different verticals, a lot of testers. They have a lot of knowledge that you may not have because you have blinders on and your little whatever you're working on. So they bring a lot of value as well. And they're not very pitchy either. Jim made sure of that also.

Right, exactly. So we will invite our vendors and our sponsors to just tell two minutes about themselves, but during the presentations. This is industry. This is tool agnostic. This is industry. Just thought leaders, regardless of tools.

So I have a bet going with Jim. He thinks it's going to do well. I'm like, we'll see. We have a goal of 75 seats to fill, so we'll see. Let us know if I'm right or if Jim's. If I'm wrong and Jim's right, I'd love to know. And you can find a link for that down below to register right now. If you're in the Chicago area, I highly recommend you do. And depending on that, you get to vote of whether or not you want to see us in other states. And then you can even probably tell us, hey, you should go to Dallas next or Nashville, which is close by. That would be cool also. All right, Jim, before we go, though, is there one piece of actual advice you can give to someone to help them with their automation efforts and what's the best way to find or contact you?

The best way is so as an independent consultant right now, jim.trentadooutlook.com but as far as automation advice, guys, learn different frameworks, learn different, and see how AI can help you with those frameworks, kind of accelerate those learnings. I've seen a lot of people right now that are very happy with Selenium, but they also want to dabble in some Cypress, they want to dabble in some pie tests, they want to dabble in some playwright. They want to experience what those are. You know, this is not. Selenium is still a foundational tool, but you know they're looking at other areas as well. Let AI help you kind of accelerate some of those learnings and even create some base level tests.

Awesome. We'll have a link for that in the comments down below. Thanks again for your automation awesomeness. The links empty we covered in this episode. Head on over to testguild.com a556 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. 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, test 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 test guild.info to explore how we can create transformative experiences. Together. Let's push the boundaries of what we can achieve.

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