Hello friends and greetings for the day welcome back to another tutorial on istqb Foundation level certification we are in Chapter 2 talking about testing throughout the software development life cycle and continuing ahead with our same segment that is 2.2 test levels and test type and as a part of today's tutorial we'll be jumping on to the next segment which is 2.2.2 that is test types and here we'll be understanding a lot of interesting facts and figures about testing so let let's look into that so when it comes to the first test types to talk about of course here we are talking about the various different testing types like what exactly are the different approaches which we can use throughout the testing in order to test our different parts of the application now of course how this is different from the testing levels people do get confused or when we say types of testing like static and dynamic are different from this of course the way we pronounce it it may look quite similar to each other for example types of testing is static and dynamic but when it comes to testing types we talk about functional non-functional white box black box and you know what not like retesting regression testing Etc so of course they do look similar to each other but of course they are categorized differently static and dynamic testing are two different ways to test uh different parts of the application like static is more of review of documentation and dynamic is more of execution but when it comes to execution we have further testing types that is white box and black box and then our levels of testing can be categorized into functional and non-functional so today in this particular tutorial we are talking about functional and nonfunctional and all we are trying to talk about is that how they are different from each other the very first and foremost important thing here is that these two are the categories of levels of testing I do have a number of different levels of testing that is if you just keep account probably we'll get around 50 plus levels of testing inclusive of very common levels which we know like unit integration system acceptance system integration component integration and then if you jump onto the non-functional side we do have performance security portability usability accessibility recovery you know fail over and what not there are so many ways by which I can test Dynamic testing so the only thing what we want to convey from this particular topic is that these levels of testing can be categorized into two categories functional and non-functional now to talk about how do you differentiate between functional and non-functional this topic will address all those query related to that so let's look at the functional first when it comes to the functional functional testing is all about testing the the core features of the testing and the functions are what the system does I think uh this is pretty much very very easy to correlate that when you talk about any particular product the base functionality the core functionality what you have to offer people for example if I talk about Google pay Google pay is an application which allows you to transfer money from one account to another account no matter you're making a bill payment recharging your cell phone or you're just trying to scan a QR code and making a payment for any of your shopping right altogether all you're trying to do is transferring money from one account to another account Now features are offered here like you know bill payment recharges and all other Etc and those are what we call it as the core functionalities of a product similarly if I talk about booking a flight or things like booking.com making my trip yatra.com these applications based functionality or core functionality ities to allow people to search flight book a flight cancel a flight modify a flight web checkin so all that menu option what you see is the base functionality as far as I'm able to complete this I can talk and say that my system is functionally ready makes sense right but when it comes to you know testing them I just call it as functional testing so testing the core functionalities what the system is expected to do the word what means the base features the core functionalities of the product without which it is not at all an application is what I call it as the functional functionality of the product and testing that is called as functionality so some of the common functional levels are very standard and specific functional levels are unit integration system and acceptance and as a subp part of that you have component integration and system integration for your kind information these are the only functional levels and everything else other than this what you know are called as nonfunctional level so let's talk quickly about the non-functional levels also and try to understand what exactly nonfunctionality on other side is so when it comes to non-functional testing of course nonfunctional testing is about enhancing the quality characteristics of the system and here the non functions are how the system works now that's a very common thing to understand there is other part of the application of course an application does not succeed in the mark maret just with the base core features that is functionality I need to certainly top it up with lot of lot of quality characteristics like performance security usability and whatnot on a very high level if I talk about a product being built and can be used only by one person it does not make any sense today right but of course my customer may demand that hey this product will be used by 10,000 people at the same time so in that context I'll go and conduct performance testing to make sure that when 10,000 people are working simultaneously it does not crash and the response time Remains the Same same way if the customer says hey I also want to make sure that this product is highly secure when it comes to the sensitive information or the pii that is personal identification information like phone number email ID and address Etc then I need to conduct security testing however security is not limited to that even protecting against hacking and unauthorized accesses of data is also called a security testing so but this is a topup without security also the product will function well same way without performance testing also a user can go ahead and use the product so these are add-ons it's not necessary and mandatory to conduct for every single application but if you conduct today you are defining quality by doing non-functional testing right so that's the reason the alternative name for nonfunctional testing is also quality characteristics or quality characteristics testing so this similarly there are many other level like user friendliness if you want to test you have usability if you want to make sure that this product is accessible to differently able user like color blindness and readability the font Etc you put it into accessibility If the product can be ported to different platform you talk about portability testing If the product can be integrated to another product interoperability testing so similarly there are different levels levels we have which we conduct here and some of them have been listed on the screen so we have uh some of them included as performance testing stress and load as a part of performance itself then usability maintainability reliability and portability testing but that's not the whole thing however we I told you we have 50 plus levels so there are many non-functional levels for different quality characteristics at the same time you do not have any non-functional testing levels in our syllabus so you don't have to even worry about their naming conventions or definitions to remember or answer them in the examination so just ignore that and that is all enough to take care of it so today we just covered functional and nonfunctional in the next session we will try to talk about the other two topics that is white box black box and retesting regression but I'll just try to see if it takes longer I'll take more time to give you separately so that you have a good understanding and knowledge all about it so that's all from this particular tutorial team should you have anything else feel free to comment below I'm always there to address your queries and answer them well till then keep learning keep exploring keep understanding the context thanks for watching the video team and happy [Music] learning