Hello all welcome back to the next one. In this lecture, we'll take a look at how do we group test cases using test NC. So let me bring up Eclipse and I'll follow through a scenario. I have created a class called test in G underscore grouping dot java. And I have is before class, after class and then few test methods. The test methods are test BMW xx, test, Audi s6, test Ninja, and test Honda CBR.

I may have a scenario where I want to run test cases which are related to each other. Maybe there's a sanity check or maybe there's a particular feature smoke test suite or something like a particular feature regression test suite, where I really want to run all the related test cases and they could be in the same test class file. So how can we achieve those kind of things? Maybe I just want to run all the test cases which are related to BMW. I mean, currently, I only have one. But this is just an example, you may have a lot of test cases related to one thing.

Or maybe just all the test cases related to Audi, or ninja or Honda CBR. This could be one scenario. The other scenario could be like this is an SUV car. So maybe I want to run all the test cases related to SUV car, maybe I want to run all the ones related to the sedan car, and these two are motorbikes. So maybe I want to run all the test cases, which are related to motorbikes, nothing else. So destiny provides us a very powerful way of grouping test cases.

In add a test annotation, we can add attribute for groups, and then those test cases will be logically landing into a group. So let's see how we can do that. How we can make use of it. So we'll put a parenthesis here, and then groups. And here equals, we'll use curly braces. And inside this we can mention groups.

So like BMW xx is a car, I'm logically assigning it to a cart group. I can assign more than one group to a particular test method, there is no limitation. So maybe let's assign one more. I'm going to assign one as a CV since it's an SUV car. This is to classify what we are doing right? It just depends on what our test cases are, you might have a completely different feature.

So you are the best person who understands your application and you will have to figure out how you grew up your test cases. So like, this guy, already, it's again, this guy is also a car, but it's not SUV. It's a sedan so we can just say it belongs to a certain group. Right? Now we have test ninja. This is only a motorbike.

So let's say we create a bikes group. And we don't want to have a second group to this, we can only have one group also right. So let's have only one group. And the same thing applies to Honda CBR. So I'm going to add one thing over there as well. So now I have defined, what I've done is I have copied the whole thing.

So let me just copy this part only. Now it's all good. So now we have defined the groups we have categorized our test cases, and it all looks good. The important part here is to see how we use that. Let me just right click and run it and the test engine test case and it runs everything. So what is The use of defining groups, the key factor is to use our test ng g dot XML file.

What I'm gonna do here is I'm gonna open this guy and maybe make a copy of this and rename it to something like just mg dash groups dot XML. And now we have this file. So we will use this file, the key factor is to use XML file. Now let's see how we can modify this. I'm going to rename this maybe instead I will say groups demo. So just to make it relevant to our lecture, and inside the test, we will have to define groups.

Under groups, we will add a tag called run And inside the run tag we will include we need to add a tag called include. And the name we give to this include tag should be matching name to one of the groups. So let's say if I include maybe bikes only here. And that's it. If I include only bikes, and now I have a group and I run this XML file, it should only run the bikes group test cases. First of all, I need to fix errors and it affects the name of the test class that I'm running.

So this test classes also under test classes package which is good, but the name is different. So the name is test Angie underscore grouping. So I should have dated and Please make sure these things are correct, guys. Otherwise, you may just run this file and you may not see anything, right. So it's important to fix everything in these files. That's why I create a new one.

So I have a different one and a cleaner picture here. So everything is all gone and said there, let me just right click it and run as a test in G Suite. And here we go. So it runs the group's demo, test classes dot test and G underscore grouping and test Honda CBR. Test ninja only two methods are run right? and nothing else.

And it says something here, it is strongly recommended to add this line at the top of your file. Otherwise test engine may fail or may not work as expected. So actually, this is a good thing. I wanted to remind this as well. So let me just copy it for from here. And what it's saying is just put this file at the top of your destiny.

Document. That's about it. And it's really important. Yeah. So it's good that it showed us the warning. And it's good that I had a fortunately to show it to you right away.

And now if we run this, we should not see that warning. Also, it's actually just a warning, because you can see my test cases were running, so there was no issue. So it was just a warning that there may be an issue. So it's still it's good to add. So let's run the suite. And now we don't even see the warning also.

It's all good. It ran two test cases and all fine. One thing here we noticed is it's very important to pay attention to this thing. We ran this and in the output bc only two test cases ran. It's fine. We then want to run the other test cases, but what about the before class and after class?

We still want to run before class before method and these ones right? Why they did not because they did not belong to any group. So what we can do Because we don't want to include them in any group, these are some things that should always done. So what we can do to overcome this thing here is we can in the parenthesis we can add one more attribute called always run equals to true. Once we add this attribute to both the before class and after class, and now we use our test Angie groups, right click run as test in G Suite, we should see them running. So now you can see before class, first test method, second test method and after class, right.

So this is fairly important, we were able to run only test cases which belong to a group. And we were able to figure out that there is a key word or attribute called always run, which can forcefully run any method. So that's about it. Please practice it and let me know if you have any questions. Thanks for attending this one. I'll see you in the next lecture.

Thanks