Rit 8.5.0 platform training slides

IBM Rational Integration Tester Platform Training

© Copyright IBM Corporation 2001, 2013

Intended audience
Primary target audience:
 Software testers
 Test managers

Secondary target audience:
 System architects
 Software developers

2


Prerequisites
This course assumes that you have taken the following
courses or have a knowledge of:
 XML or other message schemas
 Web services, JMS, or IBM® WebSphere® MQ

3


Introductions
Your organization
Your role
Your background and
experience
 Software testing experience
 Other testing tools

Course expectations

4

© Copyright IBM Corporation 2012

5


6


7


Types of testing
White box – testing concerned with the internal
structure of the program.

Gray box – using the logical relationships to
analyze the input and output of the program.
Examination of logs, databases, message
schemas, design outputs, and so on.

Black box – testing concerned with input and
output of the program.

8

INPUT

OUTPUT


Integration testing

9


Basic terminology
Message
 Unit of information sent or received

Schema
 Structure of fields, types, and values

Transport
 Method of communication between components

10


Build and send payloads 1
Payload

11


Payload
Formatter

12


SOAP

XML

Formatter

SWIFT

COBOL Copybook

Schema

DTD

XSD

WSDL

EDI

JSON

FIX

Text

MIME

Byte Array

Java Objects

Payload

SAP BAPI/RFC/IDOC
TIBCO ActiveEnterprise
webMethods IB and IS Documents
Others…

13


Payload
Formatter
Schema
Test Data

14


Payload

JMS

webMethods

Formatter

HTTP/S

FTP

NDM

Oracle/BEA

JDBC

Sonic MQ

TCP/UDP

PL/SQL

Flat Files

Shell commands

TIBCO EMS

TIBCO iProcess

Schema
Test Data
Transport

TIBCO Rendezvous
IBM WebSphere® MQ
Others…

15


Payload benefits
Concentrate on business data, not payload syntax
• Reduce errors
• Reduce complexity
• Improve productivity
Reuse the same skills with different payload types.

16


Levels of testing
COMPONENT
INTERFACE
TESTING

UNIT
TESTING

INTEGRATION
TESTING

Rational
Integration Tester

Rational
Integration Tester

JUNIT

E2E TESTING

Rational
Functional Tester
or Rational
Integration Tester

•
•
•
•
•

17

Unit testing
framework

•

Code branch
coverage

•

White box
testing

•

Security tested
at code level

GUI-less
testing

Simulated
services

•

Driven by
design outputs

•

Orchestrated
testing

Multiple
workstreams

•

Simulated
services

•

Passing values
between tests

Share design
outputs

•

Multiple
technologies

•

GUI and GUIless testing

•

Interface
performance
testing

Software Development Life Cycle
Requirements
Architecture
Infrastructure
Fitness for Purpose
Potential Reuse

Unit Test
Simulation
Build Server
Coverage

Design

Run
Diagnostics
Performance Test
Coverage
Production Data
Reuse

18

Build

Test

Regression Test
Functional Test
Integration Test
Simulation
Coverage
Performance Test
UAT


Positioning
Test
Management

UI Testing

Defect
Management

Source
Control

Data
Management

Continuous
Integration

Rational Integration Tester

BPM

19

Web
Services

TIBCO
RV/EMS

SOAP/XML
Over JMS

JMS

TCP
/IP

IBM
MQ

JDBC

web
Methods


OS support
Supported Operating Systems (Rational Integration Tester)






Microsoft Windows
Solaris SPARC
Red Hat Linux / SUSE Linux
OS X
AIX

Other Supported Operating Systems (Tools)
 z/OS ®
 zLinux

External libraries required

20


Preparation


Integration testing architecture
Rational
Integration Tester

Results DB

Rational Test
Control Panel

Platform
Pack

System
Under Test

Rational
Integration Tester
Agent
22


Before starting a project
There are a number of things that might need to be
installed or configured before starting a new project:
• Library Manager
• Project Location
• Results Database
• Rational Test Control Panel
• Rational Integration Tester Platform Pack

23


Before starting: Library Manager
Rational Integration Tester requires third-party libraries to
work with various transports or messages. These are set up
in the Library Manager.

24


Before starting: Library Manager
The Library Manager must be run on first install and
whenever new libraries are required. Rational Integration
Tester or the agent must be restarted after making changes!

25


Before starting: Project location

Each project is stored in its own folder; individual tests,
stubs, and other resources are stored as files in that
hierarchy.
If a project is to be shared, consider version control.
Rational Integration Tester supports Eclipse Team
Providers, allowing the use of a variety of version
control systems.

26


Before starting: Results database

A database is recommended for storing test
results. This will make it easy to:
• Review test results
• Share test results through the GUI or web server

One database can be used for multiple projects,
and by multiple users.

27


Before starting: Results database

To create a results database, set up a new
database and run the provided script. Upgrade
scripts are provided for any schema updates.
Supported database providers: Oracle, MySQL,
MS SQL, IBM DB2®

28


Before starting: Rational Test Control Panel
The Rational Test Control Panel manages:
• Proxies for recording HTTP/TCP/JDBC traffic
• Scheduling runs of tests or test suites
• Deployment of stubs within an environment
• A web interface to the results database

29


Before starting: Rational Integration Tester Platform Pack
Rational Integration Tester can interact with some
technologies directly – it requires help for some others.
The platform pack is a set of tools that can interact with
the system under test on behalf of Rational Integration
Tester.

30


Before starting: Rational Integration Tester Platform Pack
Platform Pack Components:
• HTTP(S)/TCP Proxy
• HTTP Proxy Configuration Tool
• JDBC Proxy
• IBM WebSphere MQ Exit for System z ®
• IBM CICS ® Transaction Gateway Proxy
• IBM CICS Transaction Server Proxy
• Java Virtualization Agent
• IBM Rational Test Control Panel ANT Client

31


Creating a new project


The initial screen
The initial screen of
Rational Integration
Tester provides fast
access to existing
projects, and the creation
of new ones.

33


Creating a new project

Creating a new project:
1. Name and location
2. Server Settings
3. User Permissions
4. Change Management

34


Server settings

1. Results
Database
2. Rational Test
Control Panel
3. Results Server
(legacy only)

35


Project permissions
User-based
permissions can be
set up for the
project using LDAP.
The project can be
restricted to certain
users, and different
users can have
different
capabilities.
36


Change management
Rational Integration
Tester projects can
have a connection
to change
management tools.
Using this
connection, you can
raise defects from
within your project.

37


The workbench
Main toolbar
Perspectives
toolbar

Current
perspective

Status bar

38


Perspectives walkthrough
Architecture School
Requirements Library

[F8]

Recording Studio

[F9]

Test Factory

[F10]

Test Lab

[F11]

Results Gallery
39

[F7]

[F12]


Lab: Creating the training project
Complete the following tasks:
 Module 3.3: Create a new project in
Rational Integration Tester

40


Modeling the system under test


Architecture School
In order to effectively test a complex system, we need
to understand how it functions and fits together.
Within the Architecture School, we define a model of
this system.
The model supplies Rational Integration Tester with
data that will be used as a foundation for building tests
and stubs.

42


Multiple environments

Environment

Development

Testing

Production

Queue name

queue.msg.dev

queue.msg.test

queue.msg.prod

User name

devuser

testuser

productionuser

43


Logical and Physical View

Logical View
provides an abstract
view of the system
under test.

44

Physical View
provides all physical
settings for
infrastructure.


Environments

45


Environments

Development

Test

Production

Environment
selects the physical resources corresponding to
the logical resource
46


AddNumbers – a simple example
Before we look at complex examples, we will build a
very simple example of a system model. This will cover
a basic web service that adds a pair of numbers.

47


Logical View
Logical View provides an abstract view of the
system under test.

Components, their dependencies, and
interface patterns can all be viewed here.
48


Service Components
Service Components expose one or more
operations to be tested. Service components can
be simple (no child components) or composite
(one or more child components).

49


Operations

Operations are interfaces that define a service
component’s functionality.
Each operation contains a Message Exchange
Pattern, describing how to establish communications.

50


Infrastructure Components
Infrastructure Components are named components
that can be bound to physical resources. Infrastructure
components do not expose any testable operations.

51


Dependencies
Dependencies represent a reference from one
operation to another, or from an operation to an
infrastructure component.

Outgoing dependencies are displayed in lavender,
and incoming dependencies are displayed in green.
Dependencies are only displayed for items in the
diagram that are selected.
52


Lab: Setting up the Logical View for a simple system
 Module 4.4: Build the Logical View
for the addNumbers web service

53


Physical View
Physical View describes all configurations of the
infrastructure that might be used by the system to
provide the functionality described in Logical View.

54


Physical resources
Physical resources are testable resources (such as
databases and web servers) representing a single
configuration of an infrastructure component.

55


Testing transports
After creating a physical resource for a transport, click
the Test Transport button. This checks:
• The correct settings have been entered in the
Physical View.
• The Library Manager has been correctly configured
for this type of physical resource.
• The resource is active, and Rational Integration
Tester can connect to it.

56



Environments let us choose which physical
resources to use within Rational Integration
Tester.
57



Environment

Development

Testing

Production

Queue name

queue.msg.dev

queue.msg.test

queue.msg.prod

User name

devuser

testuser

productionuser

Environments can also supply a set of
configuration settings in variables (tags).

58


Environments
A new project starts with no environment selected. A
new environment can be created through the menu
option Project > Create New Environment.

59


Bindings
The connections between logical and physical
components within each environment are defined as a
set of bindings.

60


Environments – Hints and tips
The current environment is displayed in the title bar.
Change the current environment by selecting
Project > Switch to Environment.
Hover over a logical component to see its current
binding.
Right-click a logical component and select Physical
Resource to jump to the corresponding physical
component.
61


Lab: Physical View and Environments
 Module 4.6: Build the Physical
View for the addNumbers web
service
 Module 4.8: Create the
environment and bindings for the
addNumbers web service

62


Message schemas
Once we understand the architecture of the system, we
need to understand how messages are used within the
system.
There are two parts to this:
• Setting up the message schemas
• Configuring message exchange patterns

63


Schema Library
The Schema Library provides all schemas in one place,
along with a preview of message formats.

64


Message Exchange Patterns
Each operation has a Message Exchange Pattern
(MEP) describing how it communicates:
• Message schemas
• Logical transport
• Transport settings

65


Message Exchange Patterns
Each MEP can be configured as:
• Request/Reply
• Publish/Subscribe
• Publish
• Subscribe
Use Request/Reply when the client determines exactly where
the message will be going (for example, using a web service)
Use Publish/Subscribe, Publish, or Subscribe when the client
does not know the final destination of the message (for example,
using a JMS topic)
66


Lab: Schemas and MEP
 Module 4.9: Import the message
schema for the addNumbers web
service
 Module 4.10: Set up the Message
Exchange Pattern for the
addNumbers web service.

67


In Rational Integration Tester, requirements are
messages.
Developers, analysts, and testers can create
requirements at the beginning of the lifecycle.
The messages can then be reused throughout the
lifecycle of the project.

69



Requirements
Library Tree
70

Message Editor

Message Editor

The Message Editor
provides editing of
messages in a tree
format, along with
validation and storage
settings.

72


Messaging actions
Value
 Provides a value when publishing a message

Filter
 Filters incoming data

Assert
 Validates incoming data

Store
 Saves data for later use

73


Creating requirements
There are several ways to create new requirements:
• Create a new blank message and edit



Apply a schema and edit further
Copy and paste a message from another source

• Use the MEP to create a request or reply message

74


Lab: Requirements Library
 Module 5.3: Build a requirement by
importing a message from an
external file
 Module 5.4: Build a requirement
using a schema
 Module 5.5 (Advanced): further
exploration of requirements

75


Recording system events


Recording Studio

The Recording Studio allows us to nonintrusively
review and record events sent to and from the
system under test.
These events can then be used as a source of tests,
stubs, and other interactions with the system.

77


Recording Studio
Event Monitors / Triggers

Event Monitor Properties
78

Events View

Message Details

Event Monitors

Transports and operations
can be selected for
monitoring in the Event
Monitors panel.
Event monitors can be
added or removed with
the and buttons.

79


Events View
Events View displays recorded events. These can be
sorted by the default fields, or by event-specific fields.

80


Supported transports
Recording is supported for a subset of the transports
available in Rational Integration Tester:
HTTP / HTTPS
TCIP/IP
JDBC (IBM DB2, Oracle, MS
SQL, MySQL)
IBM WebSphere MQ
JMS (Subscription only)
CICS Transaction Gateway
CICS DPL
81

TIBCO EMS
TIBCO Rendezvous
TIBCO BusinessWorks
webMethods Integration
Server
SAP IDOCs
FIX
IMS Connect

How does recording work?

Events are recorded in different ways for different
technologies. In some cases, we can read directly from
the transport; in others, we need some tools to help us.
For this example, we will look at how we record HTTP
traffic using the Rational Integration Tester Proxy.

82


Web services: normal operation

Client
application

83

HTTP

Web service


Web services: adding the proxy

Client
application

84

HTTP

Rational
Integration
Tester Proxy

HTTP

Web service


Web service recording

Client
application

Rational
Integration
Tester

HTTP

Rational
Integration
Tester Proxy

Web service

Control link

Recorded events

HTTP

Rational Test
Control Panel

Control link

85


Lab: Recording Studio
 Module 6.3: Record messages sent
to the addNumbers web service

86


Creating tests


Test Factory

Test Factory
tree
88

Editing panel

Test structure
Tests consist of 3 sections:
Initialise, Test Steps, and
Tear-down.
Test Steps should hold the
main body of the test.
Initialise and Tear-down steps
are best used for setup and
clean-up tasks, such as
clearing database tables or
moving files.
89


Test structure

Initialise and Tear-down
actions may only run once
(for example, in performance
tests).
Some test actions will force a
test to skip all further Test
Steps, and go straight to the
Tear-down section.
90


Tests

Tests can contain short
or long sets of actions.
These generally flow
sequentially, though
logic can also be coded
into the test flow.

91


Technical View and Business View

Technical View:
Pregenerated
description of each
action in the test.
Business View:
User-created labels
for each action.

92


Creating tests
1. New Test – creates a blank test.
2. New Test from MEP – generate messages based
on the Message Exchange Pattern (given in the
Logical View).
3. New Test from captured messages – create a test
using data captured in Recording Studio.
4. New Test from Template – use a preconfigured
template as a base for a new test.
93


Editing tests
New actions can be added
to tests from the context
menu and the Test Steps
toolbar.
Test steps can be
reordered by dragging and
dropping.
Each step can be edited by
double-clicking.
94


Lab: Test Factory
 Module 7.4: Create a test based on
messages recorded for the
addNumbers web service
 Module 7.6: Create a test based on
the addNumbers MEP

95


Running tests


Test Lab

Task Monitor

Console

Test Execution
Tree
97


Running tests
Run a test in the Test Lab by double-clicking in the
execution tree, clicking the Run button, or
pressing F5.
Extra options can be selected through the Run…
command. These include:
• Changing environment
• Scheduling test execution
• Deploying tests to other computers

98


Task Monitor
The Task Monitor displays each instance of a test,
showing a progress bar and the status (pass/fail) of
each completed test.

99


The Console

The console shows the execution status of the selected
test run. Logging information will be displayed here.

100


Lab: Test Lab
 Module 8.2: Run the tests that you
have created for the addNumbers
service.

101


Test automation


Test Suites
After developing tests, you can automate them, rather
than executing them manually.
To manage the execution of a group of tests, add
them to a test suite.

103


Scenarios
Test suites contain a number of scenarios. Scenarios
contain tests, performance tests, test suites, or other
scenarios.

Each scenario dictates how the tests will be run.

104


Lab: Test Suites
 Module 9.2: Create and run a test
suite using the tests that you have
created for the addNumbers web
service.

105


The Results Gallery displays an execution summary
and detailed coverage, error, and performance reports
for test suites that have been run in the project.

106


Results Gallery
Resource Type
and Name

Resource
Instance

Execution
Summary

Reports Viewer

107


Results Gallery
Results from test suites are stored in the project
database. Reports are generated from this data,
and are available through the results gallery.
Reports can also be managed in this perspective.

108


Notes
Test runs can be labelled for future reference, and
notes can be added.

109


Lab: Results Gallery
 Module 9.4: View your test suite
results in the Results Gallery.

110


111


Course legal notices
 The following paragraph does not apply to the United Kingdom or any other country where such provisions
are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.
 This information could include technical inaccuracies or typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.
 If you are viewing this information in softcopy, the photographs and color illustrations may not appear.
 Any references in this information to non-IBM websites are provided for convenience only and do not in any manner
serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.
 Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained
in other operating environments may vary significantly. Some measurements may have been made on developmentlevel systems and there is no guarantee that these measurements will be the same on generally available systems.
Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users
of this document should verify the applicable data for their specific environment.
 Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities
of non-IBM products should be addressed to the suppliers of those products.
 All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and
represent goals and objectives only.

112


Course legal notices (cont.)
 This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands,
and products. All of these names are fictitious and any similarity to the names and addresses used by
an actual business enterprise is entirely coincidental.
 This information contains sample application programs in source language, which illustrate
programming techniques on various operating platforms. You may copy, modify, and distribute these
sample programs in any form without payment to IBM, for the purposes of developing, using,
marketing or distributing application programs conforming to the application programming interface for
the operating platform for which the sample programs are written. These examples have not been
thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability,
serviceability, or function of these programs. The sample programs are provided "AS IS", without
warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample
programs.

Trademarks and service marks
 IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp.,
registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.
 Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
 Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
 Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
 Other company, product, or service names may be trademarks or service marks of others.

113


Rit 8.5.0 platform training slides

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (17)

Similar to Rit 8.5.0 platform training slides

Similar to Rit 8.5.0 platform training slides (20)

More from Darrel Rader

More from Darrel Rader (6)

Rit 8.5.0 platform training slides