Let's go ahead and talk about the different types of testing. So we have functional testing that are more about those types of tests are more about how the product operates.
Nonfunctional tests might include things like how it handles stress and how it balances the load, which sort of capabilities the product has in certain environments. Then we have just other kind of more generic types of testing, like maybe user acceptance testing.
And then we specifically have a focus on security testing
how we protect against vulnerabilities. So when we talk about functional testing, several different types of tests fall under the category of functional testing and the first of which is unit testing.
Now unit testing is conducted by the developers. So this isn't something that Q. A is performing. This is where the developers air checking their own work, and this happens during the actual coding phase. Oh, Arthuis implementation phase of the software development life cycle. So we're producing code,
but we're also verifying and checking our own code
before we would ever send it to Q. A.
Basically, what we're looking to do here for a unit test is we're gonna take this software and break down this'll large software package into small units of functionality. And then we're testing each part separate from the hole. So ultimately, we're looking at individual pieces. Does this element do what it's supposed to do?
Okay, what about this element over here doesn't function properly.
We'll have this element, and in a few minutes, we're going to see specifically an integration testing. Okay, if each of the parts works, fine. When we bring them together is a whole Do they work? That's where integration testing comes in.
Another type of testing that will do is logic testing. Um,
one of the things about code that we probably all know is that code can be very poorly written and still run. So it's not always an indication of whether the code is well written, how it looks to the end user. So also, another type of testing from a functional perspective is logic testing
Is the code well written? Does it follow the structure and the logic, as it should? Um, really, we're just kind of testing for whether or not the code is well written, whether it's predictable and its behavior is gonna be
Integration, testing we've already mentioned it kind of takes the unit testing and pulls everything together so that we see the big picture. Then we also have regression testing.
Ah, sometimes software doesn't work as it was supposed to. What? We want to find out with regression testing. We want to make sure software that we install and that that we implement doesn't break any sort of pre existing elements on the network
that we don't call some other mechanism to stop functioning or that we don't compromise
the security of the network.