Hello all welcome back to the next one. In this one, we'll take a look at one more Lesnar from testan G, and that is I sweet listener. So we looked at I invoke method listener, we looked at I test listener, since we had things on methods and test level, we should have something on the level of suite as well, right? Because there might be stuff that we want to run and execute before and after suites. So what is a test suite? We all know in our XML files, we have a suite tag, and under that we have multiple test tags.

So this is the suite level. What I've done here is I've just made a small change that here I'm running test listener, test one, and here I'm learning running test listener, sorry, listener, test two. And then I have two classes here. The first one was using customers. Number one, the second one was using custom listener to, we will actually change both of them to use custom listener three. So let's go ahead in our listeners package, rb one of them and create a custom listener three class.

And let's open it. I'm going to delete the custom listener one stuff. And I'm going to delete this interface as well. So now we will use ice sweet. And then control space I sweet listener from our dot test. And now let's implement the unimplemented methods.

So click on this and it's a very easy one. So there are only two methods inside it. On start and on finish, and we got the imported statements here, right. So always make sure we have correct import statements. Then it is very easy, right? We can just tell by name also OnStar is when the sweet start the suite level and on finishes when sweetens, right, so let's write the comments here.

When sweet tag starts. And same thing when sweet tag completes. That's about it. So this is very easy. Let's write couple of print statements to understand it. So this is coming from onstart.

And this is coming from on finish. Let me just write it So let's write it maybe when, okay, I have to write it within the double quotes. So before sweet starts. And we can just write the same thing. Here after sweet completes. That's it.

Now, what I want to do here is I want the same listener in both these classes. We have one more way to use listener, instead of importing the listener package here, and providing the listener annotation here, we can actually do the same thing directly from our XML file. And it's very easy because then we do not have to change it or add it separately in every class file. So let's see how we can do it. I'm just gonna Delete. Or maybe you know what, let's not delete, let's comment out the things.

And I'm gonna comment out the import statement as well. And this one, I can come delete, because we're not using the custom listener here. The same thing I'm going to do here, let's comment out. Let's comment out this listener as well. And let's delete the custom listener. So now we have both the classes all said and done, but we need to tell them some way that please refer to custom listener three when you are running.

So we will go to our XML file, and we can see we have both the test tags in the suite level before the test tag itself, we can just mention it here. So I'm going to start this and listeners. So here inside it, we can add a listener. So listener, and that's done now We need to tell which listener we want to use. So I'm gonna, I want to use custom listener three. So let's copy the package name, and then the class name here, because we always have to tell the package name.

What's gonna happen here is destiny is gonna notice this thing. And it's gonna figure out that this sweet listeners test suite, it uses a listener with the name, custom listener, three, and all the test tags, all the classes inside it will use the same listener. And that's pretty interesting. Right? And it's pretty easy, because then now we don't have to add them here in every test class. That's done all surrender.

Now let me just go ahead and right click the XML file and run it. So run as test in G Suite. And here we go. Failing one method because we already know we're failing one method intentionally. So, the first thing that happened was on start executed before so it starts all the methods executed from both the classes. So from listener test one all the methods executed then from listeners to all the methods executed.

And then on finish executed at the sweet level. So after sweet completes, that's about it. This sweet listener is very simple, very easy to understand, very easy to learn. So guys, please go ahead and download the code file, practice it and let me know if you have any questions. I'll see you in the next lecture.