JORIZH & GHILYN CO

SYSTEM INTEGRATION TESTING

7 S T E P S T O I N C L U D E
 JORIZH & GHILYN

Whether you're adapting a new electronic

health record (EHR) solution in a hospital, or
replacing the billing system behind your
online commerce site, a key set of best
practices can help your team avoid
common challenges and conduct a
successful system integration test every
time.

THIS CHECKLIST WILL HELP ENTERPRISES ESTABLISH

BEST PRACTICES FOR CREATING A SYSTEM
INTEGRATION TEST PLAN.
JORIZH & GHILYN

Create a separate test environment that mirrors

1. CREATE A TEST ENVIRONMENT the production system. This gives you more
THAT MATCHES YOUR PRODUCTION control and allows you to make adjustments
ENVIRONMENT without taking the production system down while
you make changes.
JORIZH & GHILYN

2. IDENTIFY DATA IN/EXPECTED

DATA OUT

Poorly written or vague test cases won’t help

you validate system requirements. You can
only know if a SIT is successful by identifying
what output to expect from the test data
being input.

Specific expectations generate good test

data. And this also positions you to be able to
automate basic regression tests and drive
test harnesses.
 JORIZH & GHILYN

3. HAVA A RESET

Along with good test data, you

want to be able to reset the test
01
systems to some known Resetting a virtual
starting point. If you can control
the starting conditions, issues
machine.
are more likely to be
reproducible.
03
02 Deleting directories
Dropping database and their contents
tables and running from servers, and
create-and-load restoring files from a
scripts. source code control
system.
JORIZH & GHILYN
4. ESTABLISH A COMMON REPOSITORY

A brief description of the Who is currently

# issue. Who found the issue, # responsible for issue
and when. resolution.

Steps to reproduce Issue status (open, blocked,

# (steps from the test case or # in progress, resolved).
the specific actions and
data that resulted in the
issue).
Affected component or Fix priority. Environment
# subsystem. # and build information.
JORIZH & GHILYN

5. DEFINE AN ISSUE
An effective triage process can save you many headaches.
And it includes a triage schedule, identifies the team
member who owns triage, and lists all participants. These
TRIAGE PROCESS elements will help you balance the demands of decision
makers, ensure high priority issues are fixed first, resolve
priority conflicts, and maintain a history of issue fixed for a
release.
JORIZH & GHILYN

THIS IS HOW A TRIAGE PROCESS CAN PROVIDE A

FLEXIBLE, GROUP-BASED APPROACH TO ISSUE
PRIORITIZATION:

01 02
Decision-makers can Moderators can view
quickly find issues and priority conflicts and
assign a priority. resolve them with the
appropriate decision
makers.
03
All team members will have a clearer
picture of the work to complete before
a product release, which helps ensure
high priority issues are fixed first.
SALFORD & CO.

6. ESTABLISH A
COMMUNICATION PLAN

A plan for communicating between teams

is a good idea in any scenario, but it’s
critical if your testing team includes
remote, temporary, or inexperienced
testers.

At the very least, your communication

plan should ensure that testing is
conducted in the right order. Identify how
testers will be notified when their part is
ready for testing, and how the team will
manage handoff notifications.
SALFORD & CO.

7. SIMPLIFY REPORTING
As deadlines approach, you’re expected to
deliver results. If you don’t have proper
reports set up, it can take a lot of time to
answer a simple question like, “How did
testing go today?”

Automated reporting is the most efficient way

to show what you did and how it went. That
way you don’t have to track down information
that management needs.
JORIZH & GHILYN CO.

What Is Integration Testing?

Why Perform Integration Testing?
What’s the Difference Between Integration Testing and System Testing?
Guidelines for Integration Testing
Regarding Various Integration Testing Techniques
 JORIZH & GHILYN CO.

WHAT IS INTEGRATION SYSTEM

Integration testing is known as the second level of the software testing process, following unit testing. Integration
testing involves checking individual components or units of a software project to expose defects and problems to
verify that they work together as designed.

As a rule, the usual software project consists of numerous software modules, many of them built by different
programmers. Integration testing shows the team how well these disparate elements work together. After all, each
unit may function perfectly on its own, but the pressing question is, “But can they be brought together and work
smoothly?”
 JORIZH & GHILYN CO.
ADVANTAGES OF INTEGRATION TESTING

Integration testing ensures
that every integrated module
functions correctly.
Integration testing uncovers
interface errors
Testers can initiate integration
testing once a module is
completed and doesn’t
require waiting for another
module to be done and ready
for testing
Integration testing provides
testers with a comprehensive
analysis of the whole system,
dramatically reducing the
likelihood of severe
connectivity issues
 JORIZH & GHILYN CO.

WHY PERFORM INTEGRATION TESTING?

Incompatibility between software modules can cause errors. Developers must

confirm that every software module can interact with the database

Requirements change, thanks to client input. However, maybe those new

requirements haven't been thoroughly tested yet and should be

Every software developer has their understanding and programming logic.

Integration testing ensures that these various units function smoothly
There may be potential problems with hardware compatibility. Modules often
interact with third-party APIs or tools, so we need integration testing to verify
that the data these tools accept is correct
 JORIZH & GHILYN CO.
CHALLENGES OF INTEGRATION TESTING
If testing involves dealing with two different systems created by two different vendors,
there will be questions about how these components will affect and interact with each
other.

Integrating new and legacy systems demands many testing efforts and potential
changes. Integration testing becomes complex due to the variety of components
involved (e.g., platforms, environments, databases)

Integration testing requires testing not only the integration links but the environment
itself, adding another layer of complexity to the process
 JORIZH & GHILYN CO.

GUIDELINES FOR INTEGRATION TESTING

First, don’t initiate integration testing until each module has

undergone functional testing first
Module testing should follow an accepted sequence not to
overlook any integration scenarios
Agree on a test case strategy to prepare and execute test cases in
conjunction with the test data
Study the application’s architecture and structure, identifying the
most important modules to be tested first. Also, identify every
possible scenario
Design test cases that will create detailed interface verification
Input data is vital to conducting reliable integration testing, so
choose test case execution input data wisely
Generate reports on any bugs found. Send bug reports to the
developers, have them fix the errors, then conduct testing again
 JORIZH & GHILYN CO.
HERE ARE THE SIX MOST POPULAR FORMS OF
INTEGRATION TESTING.

Big Bang Method

01 This method involves integrating all the modules and components and testing
them atonce as a single unit. This method is also known as non-incremental
integration testing.
Bottom-Up Method
02 This method requires testing the lower-level modules first, which are then used to
facilitate the higher module testing. The process continues until every top-level
module is tested.
Hybrid Testing Method
03 This method is also called sandwich testing; It involves simultaneously testing top-
level modules with lower-level modules and integrating lower-level modules with
top-level modules, and testing them as a system.
 JORIZH & GHILYN CO.
HERE ARE THE SIX MOST POPULAR FORMS OF
INTEGRATION TESTING.

Incremental Approach
04 This approach integrates two or more logically related modules, then tests them.
After this, other related modules are gradually introduced and integrated until all
the logically related modules are successfully tested.
Stubs and Drivers
05 These elements are dummy programs used in integration testing to facilitate
software testing activity, acting as substitutes for any missing models in the testing
process.
Top-Down Approach
06 Unlike the bottom-up method, the top-down approach tests the higher-level
modules first, working the way down to the lower-level modules. Testers can use
stubs if any lower-level modules aren’t ready.