Hello all welcome back to the next one. In this one, we will see a couple of more attributes of the add a test annotation. So let's take a look. What I have here is new class test Angie underscore enable timeout. That's the one that I created. Let me maximize it.

So we have more viewing space. Inside it, we have one before class, and then one after class, not much. And then I defined couple of test methods. So at the rate test is method one and the retest test method two. Now let's imagine a scenario that for a timing, there is a bug that is identified. And because of that, one of the tests method is continuously failing.

So sometimes it doesn't make sense to run it always and let it fail because we have already caught the bug and we have already filed a bug and the test cases just failing, creating some nuisance in there. Report. So what we can do here is temporarily we can disable the test case. And how do we disable the test case? Let's take a look. So what we can do here is inside parenthesis, we can add an attribute enabled equals to false.

This guy will tell test NZ that this method is disabled, and to not run it. So we can add this attribute to any test method. If we don't want to run a particular test method, in case we don't want to delete it, there is always a way which we can use to not run the test case, right. Let me right click it and let me try to run it. So run as test in G test. What happened here is it only ran before class and then test method two and then after class so only one of the method is run, which is test method two and test method one is And it's not even skipped.

Basically, Destiny doesn't even show that it's skipped. It just ignores it. Basically, that's what we can say just ignore that it's not run. So the second thing that I want to take a look at right now is, so what we can do here is we can actually make it true also. So I want to tell you that the default value for enable is to that's why all the test methods are run, but we can make it false. So that's, that's how it works.

So the second thing we want to take a look here is timeout. So there is one attribute called timeout. And we can actually set the time out for our test method. So let's say my test method is kind of time sensitive. I want to make it that if the test method does not finish in this amount of time, then just fail the test case because maybe Maybe it's a performance issue that we don't accept any test method, which runs for more than five seconds. And if it happens, then I just want to fail it because we don't accept this slow performance in our product.

It just depends on product to product, it depends on features, it may not be applicable to all of you, but this is a constant that may happen in one of your project. So if there is a constraint, we can apply a timeout to the test method. And if the test method runs for more time than what We have provided here, then test nj will mark it as fail. Doesn't matter if the steps are going fine, but just because it has exceeded the timeout, it will mark it as fail. So what I'm doing right now here is just hundred hundred is actually in milliseconds. So which is actually very, very slow, very, very fast.

But obviously you can modify it like with just 10 seconds. 10,000. But for demo purpose, I'm using hundred milliseconds. So if this test method runs for more than hundred milliseconds, then this will fail. So what I'm gonna do here is I'm gonna say thread dot sleep. And I'm gonna wait for 200 milliseconds.

And it asked me to add a throws declaration. So we can do that. Now, this test method will obviously take more than hundred milliseconds, because we are waiting for 200 milliseconds. So test changes should fail this test method. And the first test method should not run. So let me just right click and run this test run as test in G test.

And here we go. We see the failure here. And now we should go to console. And it just says that at a out index out of bounds exception, which actually is not 11 we cannot find any relevant information because of that. But we know that this failed. Because we added more timeout timeout, we added a less timeout.

So now if I increase this to maybe 300, the timeout to 300, then it should be successful. Let's verify this run as test in G test. And it's all good. It's successful. And there is no no issue no complaints from test ng G, because we are only waiting for 200 milliseconds. And printing will not take hundred milliseconds, it is really quick.

So timeout would only occur after 300 milliseconds. So all good sir. And done. These are the two attributes that we wanted to learn in this lecture. And we have covered them. So please try to create a small file small test file and play around with these two attributes.

And let me know if you have any questions. So thanks for attending this one. And I'll see you in the next lectures guys, thanks