Kevin Surace explains how GENIE automates large batches of manual test cases into scripts using AI. A team of 40 people doing manual testing could be replaced, and generated tests integrate into CI/CD pipelines in about an hour. GENIE handles bulk conversion of hundreds or thousands of cases, not just single recordings.
Questions this video answers
Hundreds or thousands of test cases in bulk.
About 40 people.
About an hour.
No — GENIE is intended for bulk conversion; for single-case recording he recommends using the existing recorder tool.
How many test steps or steps can be generated or how many test cases can be converted by genie? Yeah.
So depending on. So the whole system was designed to take in hundreds or thousands of test cases at once. So in bulk. Right. We designed it for bulk bulk because if I only generated one test case at a time to a script, and you had to then go check and edit the script, you might as well use the recorder again. We already have a tool for this. Just record. You don't need genie. You can just record it. If you have to go through every step and make sure it's right, just use the recorder because you're making sure it's right as you record. Right. So we already have a tool for that. This is different. This says, I've had these thousand manual test cases for five years. They haven't been touched. They still work. We send to the team. I'd like those 40 heads to be redeployed in the company, out of the company, not contracted, whatever the deal is. Right. So I'm going to replace those thousand manual test cases with test automation without ever hiring a test automation engineer to do it. I'm going to have GENIE do it. And Jeanne uses AI to convert them to test automation. You run that test automation to make sure it's all running against your production system. You check the box and you say, I'm done. And now I have them automated. I don't need the 40 people, I just need an hour in as part of my CICD process. Right. So part of my pipeline.
Yeah. So what you're. Just to clarify what you're expressing there is I can still go and write test scripts for use cases that weren't part of my original requirements. I can drop them in. And I don't have to necessarily write a test case and then generate a test script because I can still automate that entire process.
You can go record all the test scripts you want, but most test scripts are recorded from a test case. And that test case is the bible of what you are supposed to test and how you're supposed to test it. So mostly you have that. But I'll just say again, the vast majority of end to end test cases in the world are manual today. And they are written in a pretty relatively standard format. That's what makes this work quickly and en masse. Right. Because we know those are up to date or else a manual tester couldn't do them, couldn't execute.
