1. Simulating back-end services
NetOcean
Simulating back-end services

2. Agenda Overview of Correlation Services
Correlation Services Technical Details
Correlation Service Demo 1 – On Line Order App
Auto record for services (online_order)
Data parameterization
Advanced features

3. Agenda Correlation Service Demo 2 – Account Balance Q&A
Add service manually
Parameterize using Index File Parameter
Test using Test feature
Dynamic responses based on user account number
Q&A

4. Why NetOcean ? Shorten release cycles:
Remove dependency on backend services
Availability, Scheduling, Cost …
Resource contention
Customize behavior to support test goals
Customize data based on business rules, boundary conditions
Simulate error conditions (item availability, system errors)
Programmable service times (simulate backend slowdown)
Unique feature to simulate network faults and latency
Eliminate delays due to data management, volatility
Credit backend service is often down
Consider relay option for runtime

5. NetOcean – test lab setup
QA Apps env.
Backend Systems
LAN/WAN
QA Apps env.
QA Eng, Agents
Replaced by
NetOcean
NetStorm, Virtual Users

6. Steps for Adding a Service
Add new service
Using Capture or Manually
Define parameters
Parameterize Response Template
Test using Test feature
Test with NetStorm Scenario
Test with real application if any

7. NetOcean - Overview All inclusive appliance UI based service setup
No software installation/setup
Each NetOcean Controller
Hosts one back-end environment
Can be managed independently
Multiple NetOcean Controllers can be hosted in an appliance
UI based service setup
Automated service recording for new services

8. Auto capture for services
How Capture Works
Auto capture for services

9. Test setup with NetOcean
Backend System
browser
Application
Current Test setup
NetOcean
Controller
browser
Application
Test setup with NetOcean
- How will this work/fit with Fitnesse
NetOcean
Recorder
Backend System
browser
Application
Recording Setup

10. Auto capture message flow
Application sends request to recorder
Recorder captures request and relays to backend service
Backend service responds to recorder
Recorder captures response and relays to Application
FedFil Host - FZ000XSWEB92 Port: 80, Search Params: <UPC_NBR> , <FDS_PREP_ORDER_NBR>, <TOTAL_SHIPPING_CHARGE>
Stop HPD. Local Service for test :80. User - / sai1995

11. “prepareOrder” response Example
Dynamic components
Order Number, UPC, Shipping Charge
Sourced from request
Reservation Number
Sequence
Item List
Repeated block based on item count
Includes other parameter values

12. Parameters & Response Template
Hold values needed for response generation
Source of values
Can be assigned from requests, HTTP headers, Query params …
Generated by NetOcean (e.g. system date, random number, counter…)
Loaded from datasets in files
Defines how response will be generated
Based on data (parameters) in specific request
Custom logic, if needed
- Bulk updates for response templates

13. Custom Data sets
Return response data (e.g. account balance) based on request (e.g. account no.)
Data set
Account Number: (Balance, Last Balance, Minimum Payment)
Test requests with different account numbers from NetOcean
xxxx4987 :
xxxx Password:123456

14. Q & A