Hello all welcome back to the next one. And this one, we will, we will see how do we create our test class, we will create multiple tests and G test methods inside it. And we'll talk a little bit about method run ordering. And we will see these method run ordering later in more detail. But we'll just take a quick look. So let's get started with opening Eclipse.

This is the package that we have for test classes. Let me create one more package. And I'm going to say it as maybe app code. We will not be using it much but I'm just going to create a class which is under test. Usually when we are writing test cases, we are testing some class. If we are using Selenium WebDriver for web automation, then we do not have any class under test.

We just write test cases. For our webpages. So in that case, there is no class under test. But for any other testing, like APA testing, or back end unit test cases, for those kind of testing, we always have a class which we test using our tests and the test cases. So I'm just gonna take a, like make a quick class, which is not really significant, but just to have an example. So let's create a class here.

And I'm going to say it may be some class to test and click Finish. And inside it, maybe we can create the simplest method, like public and it made it an integer and some numbers so maybe it can add couple of numbers so in a and b. So what it's gonna do is it's going to take two integers and it's going to return Sum of A plus B. That's about it. We are not paying attention to writing our code here. So it's the easiest class.

And after that, we're going to create our first test in G class. So right click, go to new. Click other. And you will see an option for test ng g class. If you don't see, type it up here. So test a new class, click Next.

And package name. And we're going to give the name to our class as maybe test annotation. So this is the first thing we're going to see today. So test annotation. And we will not select anything from here right now. So just click Finish.

And as soon as we do that, it imports a package for us test annotation, and it creates a class and it creates a method public void, the name is F, we can change it. And there's a notation called Rate test. So what is this, this annotation? I can, this test annotation is something. When we add this to any method, it tells test engine that it is a test and the annotation. And by that it is a test and test case.

And by this only test Angie realizes that this is a test and a test case or test method and it runs that test method. So this annotation is really very important. So what I'm gonna do right now here is I'm gonna format a little bit so Ctrl A or Command A, and then Command Shift, and F on Mac and Ctrl, Shift and F on Windows. So the code looks better, they will be formatted and you can then save it. I'm going to change the method name to test method one and let's do nothing but print out something. So see so FYI, so and then control space.

It's gonna give us all the options. So, print this out. So hit enter, it's gonna give us System dot out dot print ln, in double quotes, I'm gonna say running test. And the name of the test is test method. One. So basically, there's gonna be some test code here.

And we are currently not using the subclass to test we will maybe use it later or we can use it right now also, but there is this thing going on. And we can have more than one test method inside a test in G class. So this is a test in G class. And inside it we can have any number of test methods as we want. So I can just copy this copy this, I can say this this test method two, obviously, the names cannot be same. So I have to rename everything.

So test method to test method three and update this print statement. Also. Save the file, we can actually create an object for some class to test but we'll have to first import it because it is inside another package. So what we can do here is import app, God dot star will do everything but dot some class to test is good enough. And here, some set controlspace and class to test, we can say object OBJ equal to new subclass to test. This makes the object of the class.

So usually this is how we test a class interest entry. So if this is the class to test, we need to create an object for this class. And after creating objects, we can access method that we want to test. So I can say OBJ, dot some numbers, and this is gonna give me the numbers now here I can provide maybe one and two So this will give me some result, right. And we need to save this result. And the result, the return type of this method is in.

So definitely, we want the variable of type end. And I can say result equals to OBJ. Some numbers. Now I have this end result, I can actually compare it and check if the method is working fine if it's returning the correct result or not. So basically, this is going to give us a result. And we want to verify that this actual result is expected or not.

So we have an expectation when we write test cases. And if the actual output matches our expectation, then the test case is successful. If not, then the test case is not successful. So that's the most important thing in testing automation, right? Currently, we are not doing anything so let's just keep it like that. Later.

We can verify those things. When we learn About a third. But for now, this is our test engine class with three methods inside it. And please pay attention to the import statement, it has to be test ng g dot annotations dot test, because sometimes by mistake, people import the J unit once and which is a completely different thing. So right now I'm gonna run it. So right click anywhere on the file, go to run as test in G test, since we have the plugin, and we have the jar files in Vail figured out and it will give you these options.

So do this. And we say this on the console. So it says running Test, test method one, two, and two because I think we didn't change the last one name. So three, let me just quickly run it so we have correct output. So test method, one, two and three. Were run it says all the three methods were successful because there's nothing wrong in them.

And it says three methods around there are zero failures and zero skips. And you can go to the result of running testan G. And here you can see that default suite is run. And test classes was the package dot test. annotation is the class name. And there are three methods test method, one, two, and three. And they all ran successfully.

Now we want to know, how does it decide which method to run first, and which is to run second, right? So currently, it's running test method one, two, and three, but it's not running in the order they are written. So I can actually type it at the end and save the file and right click and run it. And still it runs test method one the first time and then test method two, then test method three. So the default run order of test entry is by the test method. Name, it goes by natural order alphabetically.

So the names are pretty same, it has one so it executes first it has to execute second it has three it executes third. If the name of this guy starts with a, a appears alphabetically before tea. So I assumed that this method should run before test method one, and we can just right click and verify this thing. And now you can see it ran test method two before test method one. So the default ordering is by alphabetic order, but we will see how we can handle it and control the run order in future lectures. So that's about it for this one.

Thanks a lot for attending this one guys, and I'll see you in the next lectures. Please practice, please download the files or write the similar code and practice on your own. Thanks a lot.