architecture testing ibm

© 2012 IBM Corporation

Architecture TestingArchitecture TestingIntegration Testing virtualizationIntegration Testing virtualization

[email protected][email protected]

© 2012 IBM Corporation2

Accelerating Product and Service Innovation | Rational

Time

Standard Approach

% Q

ua

lity P

rove

n

Big Bang

Incremental Integration Testing

The % of quality proven decreases exponentially with

the Big Bang integration testing approach as the

number of permutations and combinations that require

testing increases exponentially.

Avoiding the big bangAvoiding the big bang



Incremental Integration TestingIncremental Integration Testing

Actual Service/App

Virtual Service/App

�Test Virtualization is an enabler for

continuous Integration Testing

�Services, applications, systems are

introduced into the continuous integration

cycle in a prioritized, controlled fashion.

From Test Virtualization to Continuous Integration Testing



Test Virtualization with Green Hat

� Virtual Services can be created from

– Service specifications or,

– From recording actual traffic to existing

services/applications

� Virtual Services can be further customized

– To simulate simple to complex behaviors

(e.g. negative testing)

– To simulate latency, performance profiles,

etc.

� Virtual Services are published for

consumption by developers, testers

– Testing can start earlier: Testers can now

create their tests against virtual services

– Systems can be incrementally tested as

sub-systems become available Virtual

Virtual



5

Supported Environments & TechnologiesSupported Environments & Technologies

• ActiveMQ

• Email (SMTP, IMAP)

• Files

• FTP/S

• HTTP/S

JMS (JBOSS et al)

IBM WebSphere MQ

• JBoss MQ

• SAP IDoc, BAPI, RFC & XI/PI

• Software AG’s IB & IS

• Solace

• Sonic MQ

• TCP

TIBCO Rendezvous, Smart Sockets

& EMS

• Custom

• CentraSite

• Oracle Fusion

• SCA Domain

• Software AG IS, BPMS

• Sonic ESB

• TIBCO ActiveMatrix

• UDDI

• Web Services

• WebSphere RR

• WSDL

• BPM

• Databases

• Log Files

• .Net Objects

• Bytes

• COBOL Copybook

• ebXML

• EDI

• Fixed Width

• HL7

• IATA

• Java Objects

• MIME

• OAG

• SOAP

• Software AG Broker Docs

• SWIFT

• TIBCO ActiveEnterprise

• XML (DTD, XSD, WSDL)

• Custom

Messaging Protocols SOA, ESB, Others Message Formats



Types of TestingTypes of Testing

Grey box – Using the logical relationship to analyze the

input\output of the program

Examination of logs, databases, message schemas, design

outputs etc.

INPUT OUTPU

TBlack box – testing concerned with

input/output of the program

White box – testing concerned with

the internal structure of the program



Modeling the system under test

� Architecture school defines the architecture of the system under test including services

component, as well as logical and physical resources



Multiple environment



Logical and Physical view



OATOAT

PerformancePerformance

UATUAT

Sys TestsSys Tests

Unit TestsUnit Tests

The Old WorldThe Old World

RequirementsRequirements Quality Gate

Big Bang

• Multiple defects introduced at

once

• More unknowables – greater risk

• More expensive



PerformancePerformance

The New WorldThe New World

RequirementsRequirements

Unit TestsUnit Tests

UATUAT

OATOAT

Integration TestsIntegration Tests Sys TestsSys TestsSys TestsSys Tests

• Accelerates testing

• Reduces costs

• Lower riskBig Bang



Why you need a performance toolWhy you need a performance tool

� Traditional performance testing happens too late!

� Individual component performance is important for service re-use and governance

� Realistic system performance testing is important to measure performance of full

environments on shared infrastructure

• Validate performance SLA’s

• Look in to the ESB find and locate

performance bottlenecks

• Monitor changes over time – validate

performance improvements

• Validate performance across multiple

operations concurrently

• Simulate conditions for capacity

planning

• High performance service simulation



Rational and HP IntegrationRational and HP Integration

�Link requirements to test assets

�Execute tests from test

management dashboard

�Leverage existing reporting

structures

�Raise defects directly into defect

tracking system; RTC, HP QC,

JIRA etc

�Embed deeplinks into defects



14

עלויות של סביבת בדיקות

בעלויות הקמת תשתיות לסביבות בדיקה90% צמצום של עד -

התקנות ( מהזמן הנדרש מבודקים להכנת סביבת הבדיקה 80% צמצום של עד -

)' וכו קונפיגורציה

אל מול חיבוריות צמצום ואף ביטול עלויות של בדיקות שנדרשות על מנת לבדוק -

מערכות צד שלישי

בדיקות וירטואליות משנות את כללי המשחק – לסיכום

יכולת לבצע קונפיגורציה לסביבת בדיקות בדקות במקום בשבועות -

אנשי בדיקות יכולים להתמקד בבדיקות במקום לבזבז זמן יקר בהתקנות -

לפיתוח בדיקות רגרסיה יכולים להתבצע באופן בלתי תלוי דרך ממשק גרפי במקביל -

למפתחים יש את האמצעים לבצע בדיקות אינטגרציה ברמת-

מאפשר לצוותי בוירטואליזציההפחתת סיכונים באופן דרמטי היות ושימוש -

רכיבי פיתוח לעבוד במקביל ולבצע סימולציה של האינטגרציה ולצפות כיצד

המערכת יתחברו בעתיד

מחזור חיים

סיכונים

Services / API



Learn more at:

•http://www.greenhat.com/

•http://www.ibm.com/

•[email protected]

architecture testing ibm

Technology