Greg Paskal
Yeah, well, actually, that's a second class I taught. Let me tell you about the first one. And then I prepped for T3 because it's a very interesting follow up to it. Now I teach T3 now. First now knowing what I knew, but I began really teaching the ladies in Rwanda a test automation. That was a a great class because imagine your employer saying, for the next 3 to 4 months, all you're going to do is be learning about becoming a great automation engineer. That's what we get to do with these ladies. They don't work regular hours. This is what they do eight hours a day is they study engineering. They study the craft of software testing and then automation and development. So it's amazing I have this time with them. Oh, and I did the first cohort, if we could call it that, from December to around February or so we wrapped up. That was with four different ladies. I've actually included a picture of them and even their graduation if we get a chance to put that in. I think that'll be great. But what I learned through this process was that, being a test engineer first, I really wanted to instill great test engineering skills. So I kind of went back and said, well, what would be foundational tests engineering skills I would teach these ladies as well, especially now that I had four graduated automation engineers. And Joe, no kidding, these are some of the best automation engineers I've trained. They're that good. And I think it's because they're that dedicated to really studying the craft of it and doing it well. I always talk about locators and synchronization. We just hammer on those so they can do those almost in their sleep. They know those well. I always look at those as kind of the part of the secret sauce to great automation. Once we graduated that class, I started doing this T3 class, and I had this thought, what would happen if we trained test engineers and coupled them along with automation engineers and created these little mini teams, a team of three. That's how I came up with the T3 idea, and that's turned out to be a hit. And I tell you, I've now finished two cohorts. I've trained 12 ladies in this process about between that and the two automation cohorts, about half a company now, I've done training four, including even some leadership training, the T3 concept, I could teach anywhere. It is a no brainer. Imagine a four week course. It's like the automation course. This is all they do for a month and they learn again the fundamentals of test engineering. These are people who did not go through the automation training. But as you know, many people get into the work of QA and testing kind of just they get dropped in and they're like, well, start clicking away and looking at stuff and figuring it out. And it's there's more to that. And you know. Randy and I, this is one of the things I love working with Randy Rice is we both have really deep roots in training and teaching. I'm a big ISTQB, .... fan, although, I study all kinds of testing methodologies out there. But being intentional, especially that first week teaching the fundamentals of test planning, for instance, or how to write a test case, you'd be surprised how many people have never learned those basics. Most of the time, a test engineer hearing the idea of a test plan, they turn around and run away because they think, oh my gosh, I'm going to be writing a 50-page word document. And we really tell them this is a really different approach. And so this is where METS comes in. And I begin to teach from the METS concepts about identifying an application in the high level categories of it and functions, and then to break those down into tests that are prioritized from critical, high, medium, and low. That's the basics of METS. It's not that hard to learn. So they have that. They learn how to write test cases with granularity so that anybody could pick them up. And guess what? As soon as you're done with that, the automation engineer has everything they need to do their automation planning. They work really well together. And in the course of this one month class, the first week is kind of more. I learn everything about testing by the time we're done with it, the engines kind of moving forward. And by the time they've completed the fourth week, they've worked with 3 to 4 kind of fake companies. I've become the Mr. Bob or whatever they call me, Mr. Bob or whatever. They think of me as the client. And I say, okay, hello. Muraho testers, it's good to have you work for us. I want you to see my new e-commerce solution. It's for sportswear, and I kind of play that role. They ask me questions and they go off and they begin to build their METS, their test cases. And would you believe it? In most cases in a week, one week's time. I've never seen a product. They have usually a couple dozen test cases done and usually about a dozen automated test cases working in a week. Not only that, they're providing dashboarding, so I'm teaching them how to communicate. Everything from how you interact on camera, how you work with a microphone, and how they interact with a client that might be from the West or Europe or someplace like that. They're prepared to do this well. As you can see, hopefully, it's a great joy of mine to watch them excel. By the end of this class, they've just been knocking it out of the park.