Hello all Welcome back. In this one, we'll take a look at dependent test cases. So basically, we can have test cases which depends on each other, right, we saw something a little bit in the lecture where we discussed about priority. But there could be an actual scenario where one of my test case is actually dependent on other test case to finish. And it only makes sense to run that test case if the previous test case is done completed, right? In those kind of scenarios, we can actually make a test case dependent on a different test case, and test center gives us that power and then test it we'll make sure that the dependent test case will only run if the previous test case is done executing.

So this gives us a very good option. Now let's take an exam look at the example I've created the file called test and j underscore dependent test. And then we have a setup, this is a before class. And then this is an after class. And I should just remove this is just from a previous class. So now we have these two classes, sorry, these two methods for before class after class.

And then we have four test method, test method 1234. Now, let's say my test method one depends on test method two. So by default, they'll run in the order of one test method 1234. But if my test method one depends on test method, two, and this method three depends on test method one, then I can actually make them dependent and let's test whether four is independent. It doesn't need any other test case to run. So we can actually leave it so we don't have to give priority to every single test method.

That's a very good option. We don't maybe I have hundred test cases and don't want to give to give a priority to all Hundred test cases like 01234, and all that. So what I can do here is I can only add an attribute for the test cases which are really dependent and I can leave everything aside. So other test cases would just run in any order. But my dependent test cases would be run in the order, not exactly the order, but they will run based on their requirement. If test method one has to be run before test method two, then it will run based on the dependent attribute that we will provide.

Now you remember that we had a class to test some class to test and now we already have the set of classes and everything before we were actually creating the object and every test method. So now what we can do here is we can actually create the objects in the before class, so we don't have to create object in every test method. What I can do here is, I can first I have to write the input statement. So game board, app code dot some class to test. And then I can create an object here. So some class to test, and then OBJ equals to new, some class to test now this is an object created.

So sorry, I should not be creating the object here. So I should only be defining it here. And then I should be creating the object inside the before class. And then this guy is setup. So I created the object and the before class. Now what I can do here is I can use that object and every method so I'm just going to call a couple of maybe one test here.

So maybe we will use end result, and we will call OBJ dot. Some numbers. This is the most simple one and I'm going Some one and two, so we expect an output as three. So let's do assert dot assert. Sorry, for the type of assert dot assert equals, and any type we're gonna do and expected three, actual three. So it should run a test case, sorry, I should just put the result here.

So expected is the result. And, sorry, actual is the result and expected is three, what I'm expecting is three. And result is going to give me the sum of these numbers returned from the method. So obviously, one and two, if the method is correct, it's gonna return one plus two is three. So this is just a sample test method. I have used it for a particular purpose that I'll show you.

So now let's make this method one depends on test method two depends on test method one. So what I can use here is that depends on methods. So this is the attribute that I can use and in curly braces, and we can use double quotes, we can provide the name of the method where it depends. So you know what actually, I should be doing the other way. So, I shouldn't make test method, one dependent on test method two, just to showcase that it is honored. Otherwise test method one is obviously going to run before test method two because of the name alphabetical order.

And let's copy these statements down to our test method two. So now we have it like this. So what we are Here is our test method one is dependent on test method two. And now let's make this guy test method three depends on test method one, which makes sense, right. So now test method should do should execute first then test method one and then test method three. So and test method four is independent children just wherever it feels like.

So now let me just right click, and run the code, run as test in G test. And everything is successful test method tour and first, then four, because four can take any place and then one so it doesn't have to run exactly after two. test method one ran after two in between any other method can execute. So four are executed then one got executed and three depends on one. So then three got executed. So test Angie on So, whatever we provided here, and it will make sure that the dependent test method will execute afterwards.

So one was dependent on two. So that's why it got executed afterwards. Now let's take a scenario what happens. So currently, everything was successful. Everything is green to four, one and three. And now let's make this also may be dependent on one.

So this guy depends on maybe three. So now this is gonna run at the last, so two, and this guy doesn't depend on anybody. And then this one depends on one and this one depends on three. Now let's make sure that test method two fails. Let's do it. So instead of three, I'm expecting let's say two and then it will fail.

Then let's run the test case then as a test engine test case and what happens so, this method got fail this method two is fail it is expecting to but it found three which is actually correct. And at the bottom we can say, we can see that test method one got skip test method three got skip, and test method for God skip because they were all dependent on each other. And if this method got fail, then the dependent method will be skipped. The dependent one is not failed, it's just skipped. And if I remove it from test method for let's say, just for fun, we remove it then we will see a different output. So now, what happens is test method four is executed it is passed because it was not dependent on anything.

Test methods always fail. Obviously we failed it intentionally. One is skipped because by is dependent on two and three escape because three is dependent on one. Finally, we can see here, four test methods were there, one failed and two escaped. That's what we can see here also. So this is the output.

Now, let's say that I still want to run my other test cases, I don't want to skip them, maybe let them fail if there is some issue, but I don't want to skip them. So what we can do here is we can actually use the always run attribute. So this is actually very helpful always run equals to true. So if I put always run for test method one, it is dependent on test method two, even if the test method two fails, it should run test method one. Let me just right click and run it. And now let's see the output.

So what happens is this method For a successful one still got executed. Because we say we still want to run it. Please always run, it doesn't matter if test method to fail, or it's successful, still run it. And since test method three was dependent on test method one, it's ran test method three also and finally test method to fail. And that's what we intentionally fail. So I wanted to show you two things here that we can make test cases dependent.

And if test method, the main test method fails, then the dependent test method will be escaped. But if we still want to run it, always, then we can actually use always done attribute. So that's about it. Please download the code, practice and let me know if you have any questions. I'll see in the next lecture, guys, and thanks for attending this one. Thanks.