Hello friends and greetings for the day welcome back to another tutorial on istb Foundation level certifications we are in Chapter 2 talking about testing throughout the software development life cycle and continuing ahead with our second segment that is 2.2 test levels and test types and as a part of that as it is a big topic we are still continuing with 2.2.1 that is test levels and as a part of this tutorial we'll be picking up the next level of testing which is component integration testing so in the very new labus of istqb foundation level the
board has merged the integration testing level into two different parts that is component integration testing and system integration testing so don't be worried and don't be surprised that where is the integration testing level however in the reality also the integration testing is now being conducted into multiple levels like component integration or system integration and it's all about that so that's where in this new syllabus you will not find a topic called as integration testing but I will still give you a quick outline that what does that even mean but as of today's Trend we do
not have it uh as a standalone level it just happens at different further levels so today we are talking about component integration testing and component integration testing as the name suggests is all about inter interactions or interfaces or integration between two or more components within a same module sometime it can be between modules as well but as far as it is just limited to two particular components so in order to talk about component integration testing the synonyms what we use for Integrations are even called as interfaces interactions or Communications which are just another name for
integration testing so it is mainly to test the interfaces or interaction between the components of a system also component integration testing is heavily dependent on integration strategy approaches like bottom up top down or big bang approaches so first of all uh what could be a quick example to talk about what should I call it as in component integration now component integration as the name suggests it is more of like the interaction between two or more components which happens within an application so one of the right example is given on the screen right here and the
example here we are talking about a signup form or a form which allows you to register yourself on different websites and here if you notice we have got three important Fields what we are talking about that is country state or Province and city now we all have experienced filling up this form ourselves at some of the other time and we know very well that this particular option allows us to select a country first then after selecting a country then the the state list or Province list gets optimized or gets listed with those States and province
which are as per your country selected similarly if I continue further the states being selected after that the city list will be published and without that you cannot proceed ahead now even if you fill up all the three Fields And if you go back to the country and change the the value of the country then the other two fields that is state and city will be cleared and reset to select value now that totally makes sense and understands that what exactly interaction is all about between components so if I consider each of these drop down
Fields as an individual component I'm having some kind of interfaces some kind of interaction or some type of integration between these components that means they're not independent anymore but the other the one set of field depends on other set of fields value if the value is incorrect or value is not selected the other fields will not show show you any value at all and such examples what can be very well and easily referred to what is component integration testing but is that something which is mandatory to be conducted in all levels or all at all
type of applications answer is absolutely not it is not mandatory subjected your application or your system have such features embedded in it then you will conduct this level otherwise you will move to the integration level itself which is more of like the combination of two or more modules together but not the entire flow but just two or more modules maybe three or four and then try to test their Integrations or interactions yes that's a slight difference between component integration and integration testing the component integration testing is about interfaces between two or more components within the
same application or within the same module but integration testing in general is interfaces or communication between two or more modules of an application and in that context integration can also be conducted even if you don't have component integration testing the reason why istqb has decided to remove that level from our discussion because integration is just not one activity to be conducted it can be between components it can be between different parts of system or it can be within systems that means between systems so system integration will be the next level we'll be talking about and
Integrations can happen at many places not only that if I talk about web services like apis like rest apis or soap UPI apis which is like application programming interfaces now these are also interfaces thus integration testing is even conducted here and very well required to integrate to that of the application so that the right request has been processed and right response has been received and displayed on the application too so put together there are such things which we will be talking one by one keeping this this particular tutorial simple and to the point we just
limited to component integration the next topic will be talking about a system testing following that we will talk about system integration so that you can have a wonderful and very detailed explanation of each one of them 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 learning [Music]
