Hello all welcome back to the next one. We have learned all the kinds of listeners. But one thing is very important. Let's do a little bit of refactoring or maybe code cleanup kind of thing. We created three different listener classes custom listener, one, two, and three. But do we really want three different listeners in our test suite?

We probably do not want that. What we can do here is we can simply refactor it and put everything under one custom listener, and then use that custom listener in our test classes. That's very easy and simple to do, right. So what we're gonna do here is we are going to just create a new class and name it as custom listener, listeners, custom listeners, and click finish and more We're going to do here is we want to put everything under this. So I'm gonna open all the custom listener one, two, and three. And I'm gonna start from maybe one and start copying the code that we created.

So Command C, or Ctrl. C. And let's go to custom listeners. And then just paste it. Save it. Then let's go to custom listener to and copy the complete code. So up to here, copy, and let's go to custom listeners.

And paste it there. And then let's go to custom listener three and copy the code from here and paste it on custom listeners. And we are seeing a bunch of errors right now. In coppy properly. So we are seeing a bunch of errors in our custom listener class, right, the one that we created here, we are seeing a bunch of errors here. So how do we get rid of them?

The reason is because we have not added the implements here, right, so implement. And we can implement all of them in the same class. I'm just going to copy this. From here, copy and go to custom listeners and implements this thing here. Then, comma, and then from custom listener, to scroll up. Select, copy, implement this one and then comma.

Go to customers. Now three, select isolate listener and copy it here and then save the file. Now let's see what's happening. So it says import because we need to import these things right. Since we are copying it we are not typing and we are not importing, we are not letting Eclipse to do the magic, we have to go here and hover the mouse and select Import. So when every package is imported successfully, we can minimize this and we can see all the errors are gone.

Simple. This is our one stop file for the custom listeners. Everything is inside here. You can implement all the logic here. Everything will be done here. And then what we can do here is we can simply I'm just going to close all of the remaining files.

And in our test listeners, also we don't need to do anything just in our XML. While this one listener plays, we just need to replace with our new filename. So it says now custom listeners. And that's the name we gave here. So in our XML file, we just change the name of the listener. And I'm just gonna minimize these ones.

And I'm just gonna right click the XML file and run it. So basically, it's gonna run all the test methods, setup methods, everything from listener, test one and listeners to, and there's gonna be a lot of print statements. So let's run it as test in G Suite. And here we go. So it ran the complete suite listeners test suite. There were two test x application test one application test two.

Under that we had listener test one class listener test to class and test method one and test method right That's, that's all we had. Now let's go to console. And let's see on start before sweet starts, and this onstart is from test tag name. So this is for the test tag, it is the same name, but it's from different interfaces. Then this is coming from onstart we executed the logic for finding the method names all the method names inside the test ad. And before invocation, then code inside every method set up test method, one test method to clean up and then on finish, and then again on start.

So this on finish is from test tag. And this on OnStar is again from test tag, right. So basically the test tag ended here. Then again, the OnStar has started and it figured out the names of all the test methods. And finally we'll see there are two on finish one from the test tag and others From the test suite, because test suite, test suite, basically the complete suite, on start and on finish method for the suite will only execute once, right? So everything went fine, pretty good.

And we saw that how we can club all the listeners into one class and then just use that class. We don't have to wander around and type the functionalities in different classes, no need to do that. So that's about it. That's kind of small refactoring, and making the use of one class in our test engine listeners. Please let me know if you have any questions, and I'll see in the next lecture. Thanks for attending this one.