Hello, all welcome back to the next one. And this one will take a look at soft assertions provided by testan. g, it is really a very nice topic and very interesting. Let me just bring up Eclipse. And let's take a look. So what I did here is I just created a class called test Angie underscore soft assert.

And there's one test method which tests some. And it's printing something. And we created one class in previous lectures, which is some class to test. And what I'm doing here is I'm just calling the methods, some numbers from it and capturing the result. Now, we already learned, asserts the normal asserts, and that's how it works, write, test, assert dot assert equals, and these are the things we use. So let me just copy it here and be what happens with a cert is let's say this.

I use this code. Now, some numbers, I know one comma two will return me three, and I'm expecting three with the result, right? Let's say I am expecting to just to intentionally fail this test case. So it's going to fail the test case, right? And let's copy one more statement, and this one is successful. This is still expecting three.

So what I'm trying to say here is, imagine you have more than one assertion points in your test method. And if the first one fails, then your second assertion will not run because that's how asserts work. If any verification point of the assert fails, it assumes the test method is failed, and it skips out of the method it does not actually run the further lines at all. So this line is not even run in assertion. If we use assertions, let's actually just try to run this one and we will see it. You know what, let's add one print statement here.

And it will actually tell us that this is the line after assert one and we will copy one more. This will tell this is the line after assert. So if everything prints, then we know everything is getting printed, everything is getting executed. So run as test in G test. And it failed. What happened?

The test is failed, we know that we expected it. Only line that was printed is running tests to test some and then it just failed the test case. So the only line that was printed was this one. This assertion failed. So this line was not printed. And obviously, this line was not executed this line was not executed if I provide the correct expected result, which means I am now intentionally making the test case to pass, then everything will be printed, see, running Test, test some line after a third one in line after a third to.

So everything is printed here, everything was run fine. But that's not what I want, right? Maybe I might have a scenario where if my assertion the first assertion fails, I still want to run my code lines for in the test method. And I still want to see what happens to the second assertion and the remaining assertions. So at least we know, there are no other issues after the first assertion. Otherwise, what will happen is, we'll fix the first assertion we'll run the test again and then we figure out okay, there's again, there's again, an issue with assertion number 10.

So why don't we just have the capability to run everything at once and if Figure out where the issue is. So for that test, Angie has provided us soft assert. And I'm gonna remove this thing because it's already covered in the assert place. So we will import the soft assert. So I'm going to type or dot test and d dot assert dot soft assert. So this is the package that we want to import.

And we'll get rid of this line. And we'll get rid of this line. So it works a little different than normal asserts. What we have to do here is we will have to create an object for the softer cert so we can actually use it. So I'm gonna say soft cert and we'll give the name as S equals two New and soft asset. So this is the object that we created.

Now, what we will do here is we will do s a.us equals. So basically we have the same things available here. So our result is this and we are expecting to let's say we are expecting two because we want to fail this one. And this one, we know the output the output should be three, one plus two is three, but we are expecting two so we know that it's going to fail right. Now, let's copy this line, put it here and this time let's expect the correct output. And now let's run the test case.

What's gonna happen here is interesting. It ran the test case it says the test case is successful even though there is one failure right. And we know the failure. So running Test, test test some and the line after a certain one line after that, so everything is executed. Everything is executed, even though this assert should have failed, it did not fail the test case, and it executed all the lines from the code of this test method. and here also we see everything is successful.

But you must be wondering, even that is not good, right? It's good that it executed all the lines, but still, we want some way that should tell us that there is an issue with the test case. Otherwise, we would not know that there is an issue with the test method and we will never fix it. So for that, what functionality here is, we will say, as a dot, assert all this is the magic This statement is gonna do everything for us. what it's gonna do here is it's gonna run the complete code. And when it says a start all it's gonna figure out if any of the asserts from the test method fail.

And if there is even a single assert failure, then this method will fail. test method. So let's right click run as test in G test. And now we see the magic. So it ran the complete test case running test tests, line after assert one line after assert, which means everything is run. And then it tells us the following assert fail and be expected to but the actual result was three.

And from the logs, we can actually figure out where it fails. So it says test and soft assert dot java line number 20. And this line failed, right? This is coming from basically the Assad. So we know what happened. We figured out how we can fail the test case also.

And we figured out how we can run the complete test case also. So basically, test case test method is the same thing. So now with the help of soft assert, we can run the complete test method We can still know the output and the result of the test method. Right? So that's about it. Please download the code files practices as much as possible.

And let me know if you have any questions. I'll always be more than happy to help. And I'll see in the next lectures thanks for ending this one. Thanks.