Net. Ocean SIMULATING BACK-END SERVICES
Agenda Overview of Correlation Services Technical Details Correlation Service Demo 1 – On Line Order App Auto record for services (online_order) Data parameterization Advanced features
Agenda Correlation Service Demo 2 – Account Balance Add service manually Parameterize using Index File Parameter Test using Test feature Dynamic Q&A responses based on user account number
Why Net. Ocean ? 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
Net. Ocean – test lab setup QA Apps env. Backend Systems LAN/WAN QA Apps env. QA Eng, Agents Net. Storm, Virtual Users Replaced by Net. Ocean
Steps for Adding a Service Add new service Using Capture or Manually Define parameters Parameterize Response Template Test using Test feature Test with Net. Storm Scenario Test with real application if any
Net. Ocean - Overview All inclusive appliance No software installation/setup Each Net. Ocean Controller Hosts one back-end environment Can be managed independently Multiple Net. Ocean Controllers can be hosted in an appliance UI based service setup Automated service recording for new services
How Capture Works AUTO CAPTURE FOR SERVICES
browser Backend System Application Current Test setup browser Net. Ocean Controller Application Test setup with Net. Ocean browser Application Net. Ocean Recorder Recording Setup Backend System
Auto capture message flow 1. 2. 3. 4. 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
“prepare. Order” 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
Parameters & Response Template Parameters Hold values needed for response generation Source of values Can be assigned from requests, HTTP headers, Query params … Generated by Net. Ocean (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
Custom Data sets • • • Return response data (e. g. account balance) based on request (e. g. account no. ) Data set o Account Number: (Balance, Last Balance, Minimum Payment) Test requests with different account numbers from Net. Ocean
Q&A
Скачать презентацию Net Ocean SIMULATING BACK-END SERVICES Agenda Overview
e8d8df6e3626d2a85e746bac9b38087d.ppt