Hello all welcome back. So in this one, we're gonna take a look at couple of more annotations. So let me just bring the eclipses there. So right click on the package, go to new. And we will create a new test NZ class. And I'll show you these things in this lectures.

So there are these annotations right before method after method before class after class, before suite after suite. There's one called before test after test also, we don't use these too much. So that's why we're going to focus on these six. In this lecture, we'll take a look at before method after method before class after class. And we will take a look at before sweet after straight later. And there's one called data provider which we will have a separate lecture for.

So right now I'm gonna do this thing. I'm gonna select this one, and this one from here and I'll show you that test. Angie crazy. The template for us if we select this, and I'm not selecting these because I want to type them and show you that it's not necessary to select from here, we can actually go ahead and type them all. So click Finish. And it created the class as new test because we did not change the name.

And what we can do here is we can select this right click and find refactor somewhere here, rename. And I'm gonna say as test Angie. And maybe I'm gonna say before class annotations. So just a meaningful name. And it's going to change the file name also here, it takes care of it. And now you can see that it created a test method with test annotation.

Then it created a before method and after method It added annotations here, and then you can see it imported the package is also on its own. Now we can select the code and do Command Shift F or Ctrl, Shift F, and it looks better aligned. Then what I want to tell you here is this before method name, this is not important. You can name it anything. The important part is this annotation. So the name could be anything, whatever whatever method has, this annotation will be in effect.

And what this means is, let's say we have multiple test methods. So let me just change the name test method one. And let me copy this one more time test method two. And now we have two test methods. Let me put it on the top before method. After method, so it's just easy to see what's happening before and after.

And at the bottom, we can take a look at what other tests doing. So let's just print out that the test is running. And maybe I can just copy it from one of the previous test that the sprint line. So let's put it here. Running test, and this is test method one. And this is running test.

This is test method two. So let's assume a scenario where we have some common steps that we wanted to execute before every test method starts. And then there are some common steps that we wanted to execute after every method ends. So we don't want to put those repetitive steps here in Every test method right. Instead of that what we can do here is we can put those steps in before method and after method. So, if we put any step here, that will be executed before any test method is executed.

So, I am going to put this thing here and modify this maybe. So, we will say this runs before every method and we'll copy the same thing from here. And this runs after every method, right, same thing exactly same so before method, it will run once before every method and after method, this method this will run Once after every method, so let me save this file and run it, and I'll show you the output. So, you can see here, this once before every method, then it runs the test method one, then the after method was executed. This runs after every method. Then again before method is executed this once before every method because it has to run test method two, then it ran test method two, then it again ran after method and prints the line this runs after every method.

Well, the tests are successful because we are just printing out some values. So that is the use of before method and after method. It's very handy very useful. If we want to run something common before and after every method, every single method we can do that. Now we will take a look at something called before class and after class. I'm just going to type public void And maybe we can name it as setup.

I'm begging just name it anything. And then here the sky. And let me just copy this thing, and I'll paste it again. And instead of setup, I can type in hair cleanup. So why I'm doing this is because in setup, I will say add the red before and hit control space, it will give me all the options. I'll select before class from or dot test ng g dot annotations please do not confuse these with J unit.

I'm saying it again and again because I've seen a lot of errors around this time. And this one, we can just simply type something. So this runs once before all methods so it not all basically this is gonna be confusing before I can just simply say before class and we can just copy this from here, paste this guy here. And here we need to use the annotation called after control space and after class. So this is how we can create these methods by typing also we don't have to necessarily select from there. So, we can say here this runs after class.

Now let's execute this class and we will see the output and just a second. So, what does it show now it says this runs once before class, and then the before method executed, then the test method executed, then after method executed, then again the before method executed, then the test method, then after method and then finally, the cleanup after class. So, you'll notice that the difference is the before method is executed once before every method after method is executed once after every method, but before class is executed once at the beginning, then it will run all the test methods and then after class, this is executed once after all the methods are executed. So, this is before class and after class and before method and after method, they are really very handy, very useful. So, please go ahead, practice around it just create your classes. You can also use this code and I'll see in the next lecture.

Thanks for attending this one. Thanks a lot.