Scribd
Upload
5 views22 pages

Lec10 Integration&SystemTesting

The document outlines software testing strategies, focusing on integration testing and system testing. It details various types of integration testing, including top-down, bottom-up, and big bang approaches, along with their advantages and disadvantages. Additionally, it describes system testing types such as recovery, security, stress, performance, and deployment testing, emphasizing their importance in evaluating software functionality and behavior.

Uploaded by

ayesha batool
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
5 views22 pages

Lec10 Integration&SystemTesting

The document outlines software testing strategies, focusing on integration testing and system testing. It details various types of integration testing, including top-down, bottom-up, and big bang approaches, along with their advantages and disadvantages. Additionally, it describes system testing types such as recovery, security, stress, performance, and deployment testing, emphasizing their importance in evaluating software functionality and behavior.

Uploaded by

ayesha batool
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 22

Software

Engineering
Week 12 Lecture 01
SOFTWARE TESTING
STRATEGIES
• A plan that outlines the testing objectives, methods, and
activities to be followed for a software project.

• Provides a roadmap for the testing process, ensuring that the


right types of tests are performed at various stages of the
SDLC.
Integration Testing
• A type of software testing in which the different units, modules
or components of a software application are tested as a combined
entity.
• But if they all work individually, why do you doubt that they’ll
work when we put them together?
• The problem, of course, is “putting them together”—interfacing.
Integration Testing [contd..]
• Example: Application has 3 modules say, ‘Login Page’,
‘Items’ and ‘Item details’ and each of them is integrated
logically.
• We will not concentrate on the individual page here (as it’s
already done in unit testing), instead we will check how
they are linked to each other.
Integration Testing [contd..]
Test Case ID Test Case Objective Test Case Description Expected Result
Check the interface link Enter login credentials
To be directed to the
1 between the Login and Items and click on the Login
Items
module button

Check the interface link From Items select the


Details of the selected
2 between the Items and Item Item and click a details
item should appear
Details Module button
Integration Testing [contd..]
Types of Integration Testing:
• Top-Down Integration
• Bottom-Up Integration
• Big Bang Integration
Integration Testing [contd..]
Top-Down Integration
• Testing starts with the highest-level components/modules and
progresses downwards.
• Stub or dummy implementations are used for the lower-level
components that are not yet integrated.
• Allows for early testing of higher-level functionalities and
facilitates early bug detection.
Integration Testing [contd..]
Top-Down Integration
High-level components Low-level components
Typically, closer to the hardware or Closer to the user interface or the
system infrastructure. application's main functionalities.
OR Modules with highest priority OR Modules with lesser priority
Database access layer or hardware User management modules or payment
interaction modules etc. processing modules etc.
Integration Testing [contd..]
Top-Down Integration
• Example: Consider a website with the following components:
4
• Shopping Cart Module 5
• Payment Gateway Module 2
• User Authentication Module
1
• User Interface (UI)
• Product Catalog Module
3
Integration Testing [contd..]
Products Catalog Shopping Cart
Top-Down Integration U-shop

U-Shop

Front page UI User authentication

Payment Gateway
Integration Testing [contd..]
Bottom-Up Integration
• Testing starts with the lowest-level components/modules as
clusters and progresses upwards.
• Drivers are used for the higher-level components that are not yet
integrated.
• Allows for early testing of lower-level functionalities and
facilitates early bug detection.
Integration Testing [contd..]
Big Bang Integration
• All the individual components of a system are combined
and tested together simultaneously.
• In this approach, the integration testing phase occurs as a
single event, usually towards the end of the development
process.
Integration Testing [contd..]
Big Bang Integration:
Consider an e-commerce website with the following components:
• User Registration Module
• Product Catalog Module
• Shopping Cart Module
• Payment Gateway Integration
Integration Testing [contd..]
Big Bang Integration:
• With the Big Bang Integration approach, all these modules
are developed independently and tested individually.

• Once all the modules are ready, they are integrated together
in a single event, and the entire system is tested.
Integration Testing [contd..]
Big Bang Integration:
Advantages Disadvantages
• Quick integration Late detection of issues
• Simplicity Limited visibility
• Flexibility
System Testing
• A type of software testing that evaluates the complete and
integrated system.

• Focuses on testing the system's behavior and functionality


against the specified requirements.
System Testing [contd..]
Types of system testing:
• Recovery Testing
• Security Testing
• Stress Testing
• Performance Testing
• Deployment Testing
System Testing [contd..]
• Recovery Testing is a system test that forces the software to
fail in a variety of ways and verifies that recovery is properly
performed.

• If recovery is not automatic and require human intervention,


the time is measured to determine if it is in acceptable limits.
System Testing [contd..]
• Security Testing validates the system's security measures
and identify potential vulnerabilities or weaknesses.

• This involves testing authentication, access controls, data


encryption, and protection against common security threats.
System Testing [contd..]
• Stress Testing executes a system in a manner that demands
resources in abnormal quantity, frequency, or volume.

• For example, input data rates may be increased by an order


of magnitude to determine how input functions will respond
System Testing [contd..]
• Performance Testing evaluates the system's performance
under expected workloads and stress conditions.

• This includes testing response times, throughput, resource


utilization, and scalability.
System Testing [contd..]
• Deployment Testing exercises the software in each
environment in which it is to operate.

• Because the software must execute on a variety of platforms


and under more than one operating system environment.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy