insurance case study testing

8/6/2019 Insurance Case Study Testing

1/18

Case study forLarge Insurance Systems

TestingUsing Onsite / Offshore

Model


2/18

2Cognizant Case Studies, 2004

US Locations

Des Moines, IA

Denver, CO

Boston, MA

Los Angeles, CA

Moosic, PA

Jersey City, NJ

Offshore Location

Chennai, India

Client Institutional business (IB) CentralQuality Group

Clients IB Testing Services mission is to provide End-to-End testing solutions to our customers and

to exceed customers expectations by delivering greaterQuality, on budget ,on Time


3/18


QA Testing Engagement Types

Requirements Gathering

Test Case Creation Product specific

Functional Test Execution

Regression Testing

Test Automation

Integration Testing (Scenario Testing)

Documentation Testing

Compatibility Testing

System Testing in Production Environment


4/18


QA Functional & Technical Spectrum

Functional areas

Agent Management, Licensing and Compensation

New Business Application and Client Acquisition

Policy Administration

Annutization and Accumulation

Accounting and General Ledger

Statements

Platforms

WIN NT / WIN 2000 / WIN 98 / WIN XP / WIN 2000 Server

IBM Mainframes

Tools

Test Director, WinRunner and LoadRunner


5/18


Client Cognizant+ Cognizant

Sponsors

Overall Program

Coordinator

Test Manager

Client Manager

Account

Manager

ClientTest LeadCognizant Test

Coordinator

Client Team (s)

Developers

SME

Testers

Testers

Business Analysts

TestersTesters

Client Support Team

Quality, Training

Network, DBA

Support Services

Quality

Network

Client TestingCore Team

Domain Experts

Automation ToolExpert Team

TechnicalArchitectureTeam

Test Coordinator

Cognizant Test

Analyst

Test LeadCognizant Test

Lead

Team Organization


6/18


Core Testing

Team

Prod

uctM

gt.

Trainin

g

Customer

Acquisition

SMESMES

ME

SME

SMESME

SME

SME

SME

SME

SME

SME Agency

Managem

ent

E-C

omm

erc

e

PolicyS

ervice

Un

derwri

ting

SME

SME

SMEs from different business user groups are

a part of the requirements management team

which interfaces with the Core testing team

SMEs from different business user groups are

a part of the requirements management team

which interfaces with the Core testing team

Team Organization (cont)

Actuary

SME

SME


7/187Cognizant Case Studies, 2004

Knowledge

Repository

Start- UpObjectivesUnderstand Client IBproducts andproprietarytechnology

Knowledge Transition

Understanding ClientIB testing processesand procedures

Establish AcceptanceCriteria

Conduct Sample TestRuns

Establishengagementmanagement &CommunicationStructure

ObjectivesTransition knowledgegained offshoreEstablish processes and

procedures in line withthe clients IBrequirementsSet-up Offshore TestEnvironmentProvide proof ofconcept and achieve

sign-off as perestablished Acceptance

Steady State

ObjectivesProvide flexibleResourcing options tomanage testing peaks andtroughsFine tune test processes

and proceduresDeliver test casepreparation and scriptdevelopment services asper Client IB requirementsConduct Test Execution

and AnalysisProvide timely test resultsand recommendations

Transition

Knowledge Transition & Management

Critical Success Factor



Functional Testing On-site Offshore TouchPoints

Test Planning Test Case

Generation

Script

Generation

Offshore Review Offshore Review

Sign Off

Onsite Review(Business

Analyst, QA

Lead, AD Lead)

Sign Off Sign Off

Development Team

Defe

ctReports

Test

Logs

Statu

sRepo

rt

Rele

aseReport

DefectReports

TestLogs

TestPlan

Test

Cases

Test

Scripts

Execution

Fix

es

Changes due to Bug Fixing

Onsite QA Team

Offshore QA Team

Onsite Review(Business

Analyst, QA

Lead, AD Lead)

Onsite Review(QA Lead)

Onsite Acceptance(Business Analyst,

QA Lead, AD Lead)



Planning & Execution

Ensure QA Leads with similar prior experience (in relevant line of business)

are involved from the requirements phase

Individual product owners coupled with multiplexing of resources

Ensure core team (BA, QA and Dev) has unified view of the system

Clean handshake with IT and BA

QA team delivers ambiguity review reports that can be turned over to IT and BA

BAs collaborate with QA in preparation of test strategies / plans and test cases

Requirements prioritization

Clear segregation of must have from nice to have for Risk Based Testing

Use customized templates for data and test scenarios preparation

Multiple shifts in on-site / offshore model to increase throughput

Tap offshore testing pool for ramp up in support for peak release cycles



Planning & Execution (cont)

Testing early in the life cycle to save cost and time

Instantiate requirements with specific real life business scenarios and validate

Ensure all alternate flows and exceptions scenarios are captured

Use hand calculations & rule sheets for up front scenario validation

Get the QA team to review and sign-off on requirements document

Good test for effectiveness of requirements documentation - Requirements

should be testable, if not, it is not a requirement

Ensure test cases have one to one mapping with requirements

Test Approach and acceptance criteria defined before the actual test cycle

start date

Develop system test cases early in the life cycle and get sign-off from BA/IT

Walkthrough final document with ALL stakeholders to ensure sign-off

Sign-off for Test Strategy, Test Plan, Automation Design and Test Logs



Tool Based Test Management

Tracing Defects through Requirements for efficient Root Cause Analysis

and Process Improvement

Integration of Test Cases with Automated Test Suite for efficient tracking

and scheduling in an unattended mode



Test Director

Log Bugs

Log Bugs

Testing Team

Client Environment

Direct Bug to Development Team

Yes

Replicate Build

System

Test

Code

Bugs?

No

Replicate BuildAcceptance

Test Code

Bugs?

Move To Production

No

Yes

Development Team

Request for Testing

Transparent 24x7 Web-based On-site /Offshore Defect Management


13/18


14/18



3tiered Organization

Tier I - Generic tester pool Shift around based on work requirements to handle ramp-ups and ramp downs

Tier II - Dedicated test analysts oriented around business communities and

sound automated tools knowledge(e.g., underwriting, claims, etc.)

Deep SME expertise in specific areas

Excellent Automation Tools Knowledge

Tier III Test Architects, Data Managers, Domain Experts

Plan and integrate execution with upstream business, downstream IT and

program management (PMO)

Review, mentor, guide and lead testing teams



Test Automation Best Practices

Decide to automate after, Documenting current testing process and benefits

Assess areas of improvement, modules to automate and finalize automation

requirements

Evaluate and finalize automation option

Cost / Benefit Analysis

Automation using WinRunner, Certify, QTP, etc. to ensure efficient

execution of large number of test cases

Parameterize the scripts to achieve re-usability across different builds



Key Test Automation PerformanceMeasures

Goals:

Increased Test Effectiveness

1. Test Coverage

2. Test Efficiency

Reducing Cycle Time

1. Manual Versus Automation

Reduction in Cost

Productivity

Defects found

Defects found due toimproper Test Cases

Defects due to

misinterpretation of

requirements

Customer Reported

Defects

Effort Variation

Schedule Variation

Size Variation

Load Factor

Automation Trend

Key Metrics

Manual Vs Automation Effort

Test Coverage through

Automation

Causal Analysis

(For Process improvement for the next

cycle)


18/18

insurance case study testing

Documents