ISTQB FOUNDATION 4.0 | Tutorial 16 | Test Levels | System Integration Testing | CTFL | TM Square

Summary

This tutorial delves into the ISTQB Foundation Level certification, focusing on system integration testing within the SDLC. It explains the importance of testing interfaces and communications between systems, emphasizing the necessity in today's applications that often combine multiple systems. Examples like Zomato integrating Google Maps and Amazon's use of external payment gateways illustrate the concept. The video also highlights the need for suitable test environments resembling operational settings for effective system integration testing.

Takeaways

• 😀 System Integration Testing (SIT) is a level of testing that focuses on the interfaces and interactions between two or more systems.
• 🔍 SIT is not mandatory for all applications, especially simple ones that do not combine multiple systems into a final product.
• 💡 Modern applications often consist of combinations of applications, making SIT a relevant and necessary process in software development.
• 📍 SIT is concerned with the communication between the system under test and external systems or services, including those from different vendors.
• 🌐 An example of SIT is the integration of Google Maps within food delivery apps like Zomato, which is not a product of the app itself but is essential for order tracking.
• 🛠️ Suitable test environments that closely mimic the operational environment are preferred for SIT to ensure the functionality of the integrated systems.
• 🚫 SIT cannot always be conducted in the actual production environment due to cost, convenience, and the necessity of testing prior to release.
• 🔄 System integration can occur in various combinations, including software-software, software-hardware, and hardware-hardware integrations.
• 🛒 The script uses Amazon as an example of software-software integration, where Amazon integrates with external payment gateways to facilitate transactions.
• 📱 Embedded products such as smart devices and appliances represent software-hardware integrations, where software controls the hardware functions.
• 🏗️ Heavy machinery and amusement park rides exemplify hardware-hardware integrations, where different mechanical components work together to create a functional system.

Q & A

What is the main focus of the tutorial video?

The tutorial video focuses on explaining the concept of System Integration Testing at the ISTQB Foundation level, its importance, and how it is applied in different scenarios.

What does System Integration Testing involve?

System Integration Testing involves testing the interfaces of the system under test and any other systems or external services that it communicates with, ensuring they work together as expected.

Why is it not mandatory for every application to go through System Integration Testing?

Not every application has to go through System Integration Testing because not all applications are a combination of multiple systems or have integrations with external systems or services.

What is an example of System Integration Testing in a real-world application?

An example of System Integration Testing is Zomato integrating with Google Maps to track the delivery of orders, which is a combination of two different systems working together.

Why is it important to have a test environment similar to the operational environment for System Integration Testing?

A test environment similar to the operational environment is important for System Integration Testing because it helps ensure that the final functional product will work correctly in real-world conditions.

What are some of the challenges in using the real environment for System Integration Testing?

Some challenges in using the real environment for System Integration Testing include the inability to test before release (as it would require testing in production), and it may not be cost-effective or convenient to set up the real environment for initial levels of testing.

What are the three different combinations in which System Integration Testing can occur?

The three different combinations in which System Integration Testing can occur are software-software, software-hardware, and hardware-hardware integrations.

Can you provide an example of software-software integration in System Integration Testing?

An example of software-software integration is Amazon's e-commerce platform integrating with various payment gateways like Visa, MasterCard, and net banking services from different banks for processing payments.

What is an example of software-hardware integration in System Integration Testing?

An example of software-hardware integration is the combination of software with hardware in embedded systems such as smart appliances, smartphones, or IoT devices.

What is an example of hardware-hardware integration in System Integration Testing?

An example of hardware-hardware integration is amusement park rides like roller coasters, which are combinations of various mechanical and electrical components from different manufacturers.

What is the significance of System Integration Testing in the context of modern applications?

The significance of System Integration Testing in modern applications is that most applications today are a combination of multiple systems or services, and ensuring they work together seamlessly is crucial for the application's success.

Outlines

00:00

🔍 System Integration Testing Overview

This paragraph introduces the concept of system integration testing within the context of the ISTQB Foundation Level certification. It explains that system integration testing is not always necessary for every application, but is essential for applications that are a combination of multiple systems. The paragraph emphasizes the importance of testing interfaces, interactions, and communications between systems, including those with external services. It uses the example of Zomato integrating with Google Maps to illustrate system integration in practice. The need for a suitable test environment that closely resembles the operational environment is also highlighted, as it is crucial for testing the final functional product effectively.

05:01

🛠️ Examples of System Integration Testing Scenarios

The second paragraph delves into various scenarios where system integration testing is conducted, focusing on the combinations of software and hardware that can be integrated. It provides three main examples: software-software integration as seen in e-commerce platforms like Amazon, which relies on external payment gateways; software-hardware integration in embedded systems such as smart devices and appliances; and hardware-hardware integration in heavy machinery and amusement park rides. The paragraph clarifies that while these combinations are tested to ensure seamless integration, the testing is conducted to avoid issues in the final product before it is released to the market. It concludes by encouraging viewers to continue learning and exploring the subject matter.

Keywords

💡ISTQB Foundation Level Certification

The ISTQB Foundation Level Certification is a globally recognized qualification for software testers. It signifies that the individual has a fundamental understanding of software testing principles and practices. In the video, the tutorial is focused on this certification, specifically discussing testing concepts within the context of the software development life cycle (SDLC), which is a key part of the certification curriculum.

💡SDLC

SDLC stands for Software Development Life Cycle, which is a process that software goes through from its inception to its retirement. It involves stages such as planning, requirements, design, implementation, testing, deployment, and maintenance. The video script discusses testing throughout the SDLC, emphasizing the importance of testing at various levels to ensure the quality of the software being developed.

💡Test Levels

Test levels refer to the different stages or phases of testing within the SDLC. The script mentions system integration testing as one of these levels. Test levels help in categorizing the testing activities based on the scope and depth of testing, ensuring that all aspects of the software are thoroughly tested before release.

💡System Integration Testing

System integration testing is a phase where individual software components, which have been tested separately, are combined and tested as a group to ensure they function together as expected. The video script explains that this level of testing is crucial for applications that consist of multiple systems working together, such as the integration of Google Maps in a food delivery app.

💡Interfaces

In the context of system integration testing, interfaces are the points of interaction between different systems or components. The script highlights that testing focuses on these interfaces to ensure proper communication and data exchange between integrated systems, which is essential for the overall functionality of the application.

💡External Services

External services are third-party applications or systems that a software product interacts with to provide additional functionality. The script uses the example of a food delivery app using Google Maps as an external service for order tracking, which necessitates system integration testing to ensure seamless integration.

💡Test Environments

Test environments are the settings in which software testing is conducted. The script mentions that system integration testing requires test environments that are as similar to the operational environment as possible. This helps in identifying issues that may arise when the software is used in real-world scenarios, ensuring reliability and performance.

💡Operational Environment

The operational environment refers to the actual environment where the software will be used by end-users. The script emphasizes the importance of having test environments that closely mimic the operational environment to ensure that the testing is as realistic as possible and to identify potential issues before the software is released.

💡Cost-effectiveness

Cost-effectiveness in the script refers to the balance between the cost of setting up test environments and the benefits of having a close-to-real testing scenario. While the script mentions that it is ideal to have a test environment that is as close to the operational environment as possible, it also acknowledges that this may not always be feasible due to cost constraints.

💡Embedded Products

Embedded products are devices or systems that have software embedded within them to perform specific functions. The script provides examples such as smart appliances and IoT devices, which are controlled by software but are essentially hardware products. System integration testing is important for these products to ensure that the software and hardware components work together correctly.

💡Hardware-Hardware Combination

A hardware-hardware combination refers to systems that are made up of different hardware components working together. The script uses the example of amusement park rides, which are combinations of various mechanical parts from different manufacturers. Although these systems do not involve software, they still require system integration testing to ensure that all components function harmoniously.

Highlights

Introduction to ISTQB Foundation Level certification tutorial, focusing on testing throughout the SDLC.

Exploration of Chapter 2.2, discussing test levels and types, specifically system integration testing.

Explanation of system integration testing as a process involving the integration of two or more systems.

Clarification that not all applications require system integration testing due to their complexity.

Discussion on the prevalence of applications as a combination of multiple systems in the current tech landscape.

Importance of testing interfaces, interactions, and communications between systems in system integration testing.

Use of Zomato and Google Maps integration as an example of system integration testing.

Requirement of suitable test environments for system integration testing, ideally similar to operational environments.

Challenges of using real environments for system integration testing due to cost and convenience.

Different combinations of system integration testing: software-software, software-hardware, and hardware-hardware.

Example of Amazon's integration with payment gateways like Visa and Mastercard for e-commerce transactions.

Explanation of embedded products like smart devices and appliances as examples of software-hardware integration.

Illustration of heavy machinery and amusement park rides as examples of hardware-hardware integration.

Emphasis on the necessity of system integration testing for end-to-end functionality in complex systems.

Invitation for viewers to comment with queries and continue learning about system integration testing.

Closing remarks encouraging continuous learning and exploration in the field of software testing.

Transcripts

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 sdlc and continuing ahead

with 2.2 the test levels and the test

types also moving into the next segment

which is 2.2.1 test levels we are still

continuing with that and today we'll be

talking about system integration

testing

[Music]

so far we have discussed about some of

the functional levels like component

testing component integration system

testing and today we'll be talking about

the next level which is system

integration testing now system

integration testing as the word suggest

the terminology talks about it is more

about integration between two or more

systems however it's not mandatory that

every single application has to to go

through this particular level because

not all simple applications have

combination of multiple systems put

together to be called as end product but

as far as we talking about the trending

tech technical factors today we see most

of the applications are combination of

two or more applications as end product

and certainly there are certain

embedding which happens as a part of it

which makes it mandatory enough for the

team to conduct system integration level

now here we talking about interfaces

interactions and Communications between

two or more system now what could be

that which defines the basic

fundamentals of system integration

testing and then we'll take up a quick

sample example to understand more about

it so system integration testing focuses

on testing the interfaces of the system

under test and any other system and

external Services which are

communicating with it so it's just not

limited that it should be only external

systems but some some time within

internal itself you may have parts of

different systems which are connected

together to call it as a single product

and most of the time you would see the

your system being interacting with

another set of systems which might be

from a different vendor and put together

to be called as an end product in simple

words if I talk about zomato having an

embedding of the Google Maps in order to

track the order or deliver the order you

do see the tracking option where you can

see the map and directions of the

delivery boy coming to your place or the

Del delivery boy looking at the map to

reach your location is again a system

integration because Google Maps is not a

product of zamato sui or food Panda or

any other such applications that's what

we call it as system integration testing

also to add here that system integration

testing requires suitable test

environments preferably similar to the

operational environment because uh when

it comes to system integration you're

talking about final functional product

testing and the more we are close to the

Real Environment the much it is better

but why don't we always hardcoded say

that we need Real Environment to conduct

this level because of course we cannot

do this in production that is after

release we have to conduct these levels

before release or prior to releases and

second important thing sometime it's not

cost effective or convenient enough to

afford the real environment for initial

levels of testing so we just try to be

as close as possible to the Real

Environment as much as possible now

let's talk about some quick examples

that what could be the different ways by

which system integration testing can

happen in the world today so we have

three different combinations which can

be achieved as a part of today's

technical factors and Technical traits

number one system integration is

possible in the following combination

that is software software software

Hardware Hardware Hardware so if I take

a quick example example of Amazon you do

understand that there are applications

like Amazon which are shopping

e-commerce website and they help you

shop products but did you know that

Amazon doesn't have a payment option yes

if you're talking in India you may talk

about Amazon pay which is an inbuilt

wallet where you can make payment from

there but other than that they just have

cash on delivery that means they do not

have any payment options now hold on you

might be thinking that hey isn't he

talking wrong we do have visa and you

know American Express credit card debit

card net banking and okay hold on you

understood yourself when you're are

saying that they do not belong to Amazon

right the net banking are the ownership

of the banks the credit card and debit

cards are the ownership of the card

provider things like Visa Master diners

MX which is American Express and so on

that means none of these belong to

Amazon so Amazon goes and requests them

that hey Visa can you give me your

payment Gateway so that my consumers can

go ahead and make the payment on this

same way Amazon request different banks

like IC bank or Indian overseas bank or

any other bank whatever you might be

having respectively in your countries

they reach out to them that do you want

me to give your payment Gateway so that

I can allow my consumers to have the

convenience of making payment from net

banking and that's how the banks also

make money from these transactions so

they will happily give it it's not that

they have to beg them to give give them

the payment Gateway they of course sell

it as one of the services or one of the

CTS that is commercial of the self

product right commercial of the self

product simply means that they are not

generally available as an a standalone

application but they can be seen in many

other applications so net banking is a

carts which means it's not a standalone

application but can be used with many

other applications same way if I talk

about the credit and debit cards the

bank are not the owners of that the Visa

Master MX mestro these other people who

are owning that card so they have to

reach out to Visa they have to reach out

to American Express they have to reach

out to master to ask them for the

payment gate fees and in order to test

all these things we conduct system

integration testing now in this scenario

we pretty much understood that it is a

combination of two softwares that is

software and software put together in

order to get the end product so that the

shopping experience can be done end to

endend not just adding to the card the

second example here is software hardware

and certainly software Hardware could be

seen as your embeded products today like

any kind of appliances what you might be

using on your day-to-day life be it your

cell phone smart watches airpods

elevators or any other equipment and

appliances like laptop refrigerator and

all they're all controlled by a software

but they are actually Hardware right so

as we talk about embedded Sciences we

are talking about connecting software to

that of Hardware to make it as end

product so all those iOS and uh sorry

not iOS the iot internet of things all

the devices and equipments or any other

appliances what you might be using today

is a very good example of the software

Hardware combination and yes we do

conduct system integration testing on

these products and the last example is

Hardware Hardware combination which

simply means that if you talk about

heavy machineries like heavy Earth

Movers JCB cranes and even if you talk

about amusement parks in amusement parks

you do have roller coasters and jumbo

rides and whatnot and they are all just

Hardware Hardware combinations that

means it's just combination of

hydraulics and pneumatics where it works

on different components being connected

together but there is no software

concept but of course different parts

are from different companies and they

make it a very interesting thrilling

joyful rides for you and that's what is

is like roller coaster which is a good

combination of Hardware Hardware

together right so put together this is

what in detail I could explain you that

what system integration is all about and

I hope you got a good understanding of

that 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]