Unit Testing with examples in Software Engineering

Dear Students, Welcome to Gate Smashers. In today's video, I am going to explain unit testing in software engineering. So guys, all the important points related to unit testing, I'll explain in this video. So like the video immediately. Subscribe to the channel, if you haven't done it yet. Even if you have done it, you can get other devices subscribed to it, share it Subscribers are very important, so let's go. Let's start unit testing. Or we also call it Tier One Testing. You can also say level one. because this is the testing that is done first.

That means, So first of all, the testing that happens on the stage, that is unit testing. So many times the question comes in this way. We have studied testing in many ways that there is unit testing. Integration testing, alpha testing, acceptance testing, Regression etc, but the first of these testing is done, that's the unit testing. The second question comes here. Who does this testing? So look here. Unit testing is done by the developers, which means people who are developing the system, and software. the same people doing the test. And the third thing comes here. What does unit mean? Unit means individual part means,In the software, there are a lot of modules, There are a lot of functions, Procedures & control statements. We are testing each part of them. And we try to test it before integration. That means if you integrate the system, make it bigger, then there will be a problem. As I tell you in a small example.

Let's take the example of a car Now, whenever the car is built. Whatever the unit is, When a car is built in
the manufacturing unit. There are a lot of different systems in the car, which are made in different ways. This means the engine is being made separately. The braking system is made separately, the fuel system is made separately. The ignition system
is made separately. Locking system, body all these systems are developing separately. Now if they are developing separately. So when they are assembled, they are added. So if we do testing after that, then if there is a problem. So the ignition man would say that fuel, is your fault. The fuel man would say that the engine, is your fault, I did the right thing. It will be very difficult to catch the mistake at that time.

So what to do? All these units should test their things once at their level and then what to do after that, Assemble it. But this does not mean that when it has been assembled, it has been integrated, so now there will be no problem.Guys, there are many dependencies between them. There is a lot of coupling & cohesion between them. So somewhere between them, because of the dependency. I will tell you that further. But yes, the problem can still come. So that's why we say, the problem of unit testing is undecidable. It is not that if your unit testing has been passed. So, it doesn't mean that there will be no problem in the future. Remember these points too. Then, this is a simple definition, unit testing is the process of checking small pieces of code to ensure that individual parts of the program work properly.

The same thing I have explained to you has been defined. Unit testing is used to test individual blocks or units of functionality, the same thing I told you. If it is Procedure language. So we will call the entire procedure, a unit. If there is object-oriented programming, so every object, like a class, is an object, then what would we call it? We call it a unit. So, It is very important to test every part, before its integration. We apply data to it, make different test cases and test them. So that we can check how it is behaving, how it is giving output. Thank you..