Vous êtes sur la page 1sur 11


Tell us about your most recent assignment

or current job position?
Ans: Note: In this case resume has multiple projects at latest client , thats the reason we are
explaining about 3 projects performed at client site.
First of all I would like to explain about my projects before jumping in to responsibilities I
performed. In this Tenure with StateFarm I have been working Couple main projects and
multiple infrastructure projects, there is some overlap between projects I got situation to work
on multiple projects simultaneously for specific duration.
Project 1:
Project 1 is Policy Administration, Which is Statefarms Policy Administration, Underwriting
System for Auto/Property/Life policies which are under Personal and Commercial Lines of Auto.
Let me explain about the project first , From the Project wise it has Drivers, Vehicle,
Discounts ,Coverage ,Risk Analysis and Quote&Bind modules.
Almost worked on all modules but deeply involved in Coverages Module. Constructing
coverages and limts/deductibles accordingly for auto coverages like...
Comprehensive Coverage, Collision Coverage ,Bodily Injury Liability, Property Damage Liability,
Medical Payments Coverage, Uninsured Motorist Bodily Injury, Underinsured Motorist
Coverage, , Uninsured Motorist Property Damage, Rental Reimbursement Coverage? And
Emergency Road Service (ERS)
I worked for Product Service Releases of : 3.1, 3.2 and 3.2.1 under this Policy Administration
From the Role wise I worked as Business Analyst (minor role)and Quality Analyst (major role).
Project 2:
Enterprise Claims System, Which is Statefarms biggest Effort to build End to End Claims
Systems which costs 4 billion dollars , Approx 1400+ people worked on that project. This
Project has modules like First Notice Of Loss (FNOL),Claims Management, Claims Performer,
Bill& Payments , Financials and Reporting.
This System handles flow starting from when Customer Representative receives call from Policy
Holder about Accident, Create claim in FNOL with all available details at the time accident
( Named Inusred Driver, Vehcile, Claimant Driver, Claimant Car , Accident Time & date) and
allocate all reserves in Claim Management Module.
Received Auto Bills/Medical Bills from external Vendors, Validate Bills and make EFT and Non
EFT payments. Take Reports and sending to the Medical Providers (Hospitals) and Auto Repair
Vendors (Auto Repair Facilities) .Close the claims
Tested application by logging in Roles like Claims Processor, Claims Manager etc.
Project 3: Infrastructure Projects WebSphere Migration from 6.0 to 8.5, JBOSS Migration from
4.1 to 7.1 and Windows xp to Windows 7 Migration
StateFarm uses JBOSS and Webpshere as Application Servers
JBOSS is Application Server, Claims project and Policy Administration Projects deployed on
this JBOSS Version 4.1 Now they upgrade JBOSS to later Version 7.1.
So Claims and Quotes Projects need to be tested as following:
Regression testing:
for that Select some main flows from Policy Adiminisration and perform regression testing.
Performance testing:
Run existing scripts to make sure performance is not degraded due to the change (Server
upgraded from jboss 4.1 to 7.1).
WebSphere is also application used by Statefarm , all Agent Quote/Social Networking
applications are deployed on this server.
So regression testing need to be performed on Agent Applications

Regression testing:
for that Select some main flows from Agent applications and perform regression testing
Performance testing:
Run existing scripts to make sure performance is not degraded due to the change (Server
upgraded from Webpshere 6.0 to 8.5).
Thats all about Project wise.
from responsibilities wise
For Project 1 :Policy Administartion:: Worked as BA in Inception and Elaboration phases of
Rational Unified Process At initial phases of Business Analyst.
Role starting with Interviewing Business Clients using Techniques like face to Face Sessions,JAD
Sesisons and Use case Sessions. Preparing Questions befoe interview and discuss questions in
the meeting, Note down all requirements , Performed Requriement Analysis and have
sequence ( remaining Questions) and follow up meetings (to clarify questions on contradictory
and wage requirements.) prepared Business Requirement Specification , Functional
Requirement Specification , Use Cases, Use Case diagrams, Class diagrams, Activity diagrams
and Sequence diagrams
Majority of time I worked as Quality Analyst on this project. Starting from In Test Planning
Phase: helping out team lead in laying out Test Strategy and Test Plan Documents,
In Test Development Phase:Later going through Business Requirements
Specification,Functional Requirements Specification, Use case Specifications and understand
the Application Behavior and created Positive and negativeTest cases Review the Initial
Version of Test cases Prepare Test Data as per Test case Decide Test Cases for Automation
Testing Participating Test readiness Meetings to get updates on Test Case,Test Data and Test
Environment Readiness.
In Test Execution Phase , Make sure Pre-Condition and Post Conditions of Test cases are in
place. Executing Test steps as per Instructions.
As Part of Result Analysis if Test Step Actual Result is different from Expected result
make sure test environment is fine, test data is fine and confirm that failure is from
application side.
As Part of Defect Tracking, Created Defects for failed tests, update severity/priority in Defect
Tracking Tool and attach Defect Snapshots, Defect Log files and expected result document to
the defect.
Involved in Defect Status Meetings and helping out developers to explain the Defect ReCreation Steps.
From Reporting Side. Created Test Case Results Document, Defect Reports and Test
Coverage Metrics Documents.
I Performed Functional, Regerssion, Browser Compatibility Testing ,System Testing.
From Automation side, Selected Test Cases for Automation, Record navigation and Enhance
Script by performing Parameterization of the script, adding Data tables, adding Checkpoints ,
adding Reporting Functions using VB Scripting.
Was reponsbile for Execution of Automated Scripts.

2. What was most challenging about that


Challenge 1:

Requirement were not properly documented for one of the Financial projects due to huge
changes to the requirements at last moment. So situation is need to test the application
without Business Requirement Specification
How Overcame this Challenge:
Testing this functionality was a challenge. So we adopted exploratory testing approach.
As per the Process Participants are
Business Analyst or SME (Subject Matter Expert)
QA Tester
Schedule an Exploratory Session Meeting: Define Exploratory Charter (Topic for meeting)
Ex: Exploratory Charter: EFT Consolidated Payments
Pre-Condition for Meeting: BA and SME should brush-up their knowledge in EFT Payments.
QA would be ready with Test Data for the meeting.
In the Meeting,
1. BA or SME would create scenarios based on Exploratory Charter
Institutional medical EFT Payment ( Payment to Hospital)
Professional EFT Payment ( Payment to individual doctor)

Based on guidance provided by the BA/SMEs, QA tester will write down steps for
each scenario with positive and negative
Execute steps with Test data
Result Analysis: If any mismatch between expected and actual result , BA or SME
would confirm whether defect must be created or not.

After Meeting., QA will rise defects for all failed steps.

Challenge 2:
This challenge is from the Process wise, we created test cases but we are not sure Are we
covering all functionality?
How to Over came this Challenge?
Requested Lead to intiate requirement Traceability matrix, every time some test case is written
we need to enter which requirement is covered maintain separate Requirement Traceability
Mapping : Business Requirement Test Case Ids which covers that requirement.
When all requirements are covered in our test cases then we make conclusion Testing covers
all Functionalities.
3. Explain your Guide Wire Experience:
I worked on Guidewire Policy Center

3. What is Automated Testing and Advantages

of Automated Testing:

Reliable: Tests perform precisely the same operations each time they are run, and never
forget to record detailed results.
Repeatable: You can test how the software reacts under repeated execution of the same
Reusable: You can reuse tests on different versions of an application, even if the user
interfaces changes.
Better Quality Software: Because you can run more tests in less time with fewer resources
Fast: Automated Tools run tests significantly faster than human users.
Cost Reduction: As the number of resources for regression test are reduced.
In one of my project, We created automated Regression test suite which is targeted to run after
each build is deployed which saved 3200 manual testing hours for entire product release.
The following areas must be automated first
1.Highly redundant tasks or scenarios , Ex: Created claim is the starting points for all claim
application testing so create a claim need to be automated first.
2. Repetitive tasks that are boring or tend to cause human error , Ex: Verify all links on each
3. Well-developed and well-understood use cases or scenarios first
4. Relatively stable areas of the application over volatile ones must be automated.

4. Have you ever used LISA, Test Partner/

Version/ How you used Lisa/test Partner?
Yes, I did use for one of my project<mention project name> to create automated
Regression test suite (couple years back) along QTP. Management wanted to migrate
from QTP to Lisa.
Rating: 1 to 10 Scale:
Lisa: 8
Which version of LISA do you have experience with?
Ans : Lisa 5.0.22
How have you used LISA?
Yes. I have exp using Lisa to automate regression testing.
I used to Create automated test scripts in Lisa Workstation. For web application I used to
record the scripts using HTTP Proxy Recorder and DOM Events Recorder.
I added data sets if required and perform parameterization of Test flow.
And added filters to output values , added page load verifications using Assertions . i.e Also
build some basic Java assertionsfor verification of field properties like its length, existence of
field, its label verification
I used ITR (Interactive Test Run) mode to Playback the recorded/created script.
Inserted failure logs into my script, so that I can inform to my team or open a defect based on
the priority when bugs are found
I also used to configure my script to run in different Environments by setting all environment
properties under Configuration files
I used to develop Test Suites by group of 2 or more test cases
Do you have any experience with LISA VSE (Lisa Virtualization)?

Dont have real time experiencebut have knowledge on Virtual Service Environment.
Have you used data driven automation? Tell us about that experience.
Ya I did, that is one of the main thing in automationAll of the post parameters are
parameterized with column name from the datasetthen we need to set up dataset in a
fashion thatIt will either execute until end of data means all rows.or it will pick up rows
randomlyand execute scripts.
When first iteration was running..it will take first row of data from the datasetwhen running
second iteration it will execute second row of data from the dataset.
So data will be driven from dataset which is called DataDriven.

5.Familiar with Iterative and/or Agile

I am familiar with agile methodology, In my recent assignment at mercury and farmers
insurance, we followed agile .
Our sprint used to be 4 weeks , My project contained 18 sprints
NOTES about Agile: Daily Scrum Meeting, Sprint
Agile software development is iterative method of development and delivery process, each
iteration is planned for 3 or 4 weeks which is called Sprint.
Daily 15 min meeting will be there and we use to update our last 24 and next 24hrs of work
which is called SCRUM.
The developers and end users communicate closely and the software is built. Smaller teams
work in the project room, we had peer reviews , customer reviews for test scenarios and we
had daily stand up meetings to discuss the status of the project and to see if there are any

6.about Guide Wire Experience.( Any

Question about GuideWire Experience)

Explain I worked on Guide wire policy Center in Mercury Insurance; they overwrite their
existing policy administration system with guidewire policy for personal and commercial lines
guideWire Version:
Extesnively worked on work flows like Submissions/ Policy
Verified Policy Center integration points: Claims System/Billing System/Rating Engine/
DMV(Department of motor vehicles)/VIN Service/Vendor Management System/Address
Normalization Services/credit rating System.
Following information is just to have some idea. Its not necessary to explain following content
in the interview.

Policy Flows:
Policy Submissions
The goal of the submission process is to create a policy and have the policyholder accept it. After entering the
policyholders information, the producer gives a quote. If the policyholder agrees and accepts it, then the producer
binds the policy and sends it out with the accompanying documentation. The producer also forwards the billing
information to an external billing system (not shown in the diagram).
Policy Changes
Any changes to a policy can require additional evaluation on the part of an underwriter and result in a change to the
premium. A typical change might include additions to the policy (such as adding drivers or cars) or changes to coverage
limits and deductible amounts.
The normal progression just before a policy expires is to renew it for another period of time six to 12 months is
typical. After PolicyCenter renews a policy, it returns the policy to maintenance mode until the policy changes, expires,
cancels, or renews again.
Cancellations and Reinstatements
You can also cancel policies. Before the cancellation processes completes, a cancellation can be rescinded. An example
is a producer mailing a cancellation notice for non-payment to a policyholder. If the policyholder corrects this by
submitting payment before the cancellation date then the policy can be rescinded with no break in coverage.

Reinstatements go hand in hand with cancellations and are a type of policy change that returns a canceled policy to inforce status. The policy is in-force as of the reinstatement date. The reinstatement removes the cancellation from the
policy period since the period is no longer canceled. The expiration date remains the same.
When there are many errors are on a policy, it becomes necessary to rewrite it. Policies must first be canceled before
being rewritten.
The audit job lets the carrier verify information about the policyholder so that they can determine the accuracy of
premiums paid.

Policy Center integration points:

Billing system When a user creates a policy, PolicyCenter exports billing information.
PolicyCenter also sends and receives information as the policy changes.
Claims system Information is sent to and from claim systems. The claims system can
send information about the number and type of claims against a policy. PolicyCenter sends
policy data to the claims system, such as policy effective dates which answer the question,
Was the policy in-force when this accident occurred?

Rating Engine The system that rates a policy and sends the quote information back to
PolicyCenter. It also calculates the estimated annual premium in audits.
Department of Motor Vehicles When you integrate with this system, agents can request
and send driver information to the regulatory body.
VIN (Vehicle Identification) Service Use this system to look up VIN information. The
default configuration contains a demo plugin.
Address Normalization and Validation services Provides normalization and validation
against information provided by the United States Postal Service (USPS). The USPS provides
standardized abbreviations such as ste for suite and ln for lane. It also lists the complete range
of numeric addresses per street, street addresses per ZIP code, ZIP codes per state.
Credit Rating system A policy administration system may periodically request
information about an
insured. An example of a credit rating system is Dun and Bradstreet.

Closed AR Closed AP(Accounting functions) after Policy and Invoice

generations how u did that?

6. How created the policies/invoices/adding

accounting and servicing functions
7. Tell about Policy Billing Integration Testing:
7. web services testing using itko lisa and soap

7. Database testing using itko lisa or QTP

QTP : Using ADODB Object.Providing Database Connection String, Record Set Array.
Microsoft ADO (ActiveX Data Objects) is a Component object model object for accessing data sources.The ADO
Recordset object is used to hold a set of records from a database table. A Recordset object consist of records and
columns (fields).
In ADO, this object is the most important and the one used most often to manipulate data from a database.

Srvname is a connection string.if u already installed oracle in your system using that path u can connect oracle
database...if u dont have oracle give the connection string path ,whatever connection string created used in database
checkpoint by default
set conn=Createobject("ADODB.Connection")
Srvname="Driver={Microsoft ODBC for Oracle}:Server=DBserver,UID=Sa,Password=sa" username,pwd of Databse
to be connected
conn.open Srvname
Set Rec = CreateObject("ADODB.Recordset")
SQL="select * from Users"
Rec.open SQL ,conn Passed Database Connection details and execute SQL Query
Username=Rec.fields("employee name") Store Query out put of Employee_name column in username field.
Msgbox Username

LISA: using JDBC Step

(Types of Steps in LISA)

8. Challenges faced in Automated Testing

Primary challenge is Consistent object changes in one of our project which makes
existing automated test scripts not running and require lot of maintenance. We overcame

that challenge by inserting Descriptive Programming Functions in to the Framework

If any property changes of a particular class we can update the appropriate function in the
library instead of updating these objects in all test scripts.
9. Frameworks used in Automation:
Go through Recording: https://transformtoit.webex.com/transformtoit/ldr.php?

Framework Architecture

Environment files:
These files contain client information like login details, account information etc which is used as input for
functionality testing. This information is being invoked by the driver script and passed to the main test
Initialization Scripts:
Settings in the initialization script are going to remain fairly constant throughout the project life cycle, but
may change occasionally. These scripts load environment files and invoking browser and url etc.
Driver Script:
This is the script that coordinates test activities by calling other scripts. The driver is used to drive the input
parameters from the environment file to the main test script, and also it maintains the sequence of the
Function Library:
The Function Lib (function library) is a set of functions used in the test suite. It is
normally loaded at the beginning, and functions are called from it throughout the test run. This will
decrease the redundancy of the script.
There are some basic types of functions that will, without a doubt, be used
throughout the automation effort, and should be created prior to the creation of
automated tests. These function types are as follows:
i)Login functions
These are the functions that login and logout of the AUT, and other supporting applications. The login and
logout processes are going to executed several times during a test run, and are composed of very basic
ii) WebObject Action Functions:
Creating the functions which simulate actions of different web objects on AUT.
Like click_link(str_link_name) : if name of the link is passed as parameter to this function, that particular
link will be found and clicked. These functions are used as part of descriptive programming in QTP,which is
not dependent on the object repository.
iii) Business Logic functions:
These functions are created to simulate the business logic that can be run independent of the input values
and object repository.These functions contains critical logic as the development of the application.
For example:
Split the pin and enter the particular pin digits like 1st digit, 4th digit and 2nd digit in three different edit
iv)Error handling functions
Error handling functions are functions created to deal with certain unexpected events that may occur
during testing. If nothing is set up to handle these events, they could kill automation run completely.
Internet applications have a fairly standard set of events that occur regardless of the application. The list of
events includes popup security windows,
information windows, and error windows, along with the page cannot be found frame. Good portions of the
events that will have to be handle require nothing more than clicking an OK button to close the popup
window. Many of these events can be turned on and off in the browser, but some cant be. For those that
cant be turned off, routines
should be created to handle them.
v) Miscellaneous verification functions
Although most automation tools have built in checks that can be used to verify certain application
attributes, there are times when user defined checks are much more efficient.
Generally these functions are used to check the content which is between dynamic left and right
boundaries on the web page.
Ex: i) Window check
ii) Page Heading check(Text check )..etc
Result gathering functions:These functions drive the output of the test cases to the Result sheet, and
also log the errors occurred in the run. These functions can create output log file as per the requirements
Displaying result cell in green color if the result is PASS
Displaying result cell in red color if the result is FAIL
Displaying the Reason of failure if the test case is FAIL
Displaying the time of execution etc.
Test Scripts:These are the components that actually perform tests, and verify that the AUT works as
desired. The two actions listed in Example 1 is a representation of a test script. Test scripts perform actions,

Explain running Automation scripts execution after each build?

As a test lead what are your responsibilities in ur current project at NJM ? (if there
in resume as a Lead)
How you managed the offshore and onsite team, meetings/KT sessions on Insurance
What type of reports can be generated using LISA while functional and performance

9. Miscellaneous Questions:
a. Is the assignment complete? If not, when will it be complete? Or Why are you wanting to
leave it or wanting a different job?
Its almost came to an end and in Stabilization period.
b. Tell us about your working style.
Structured , Results Driven and Time Driven:
My working style as structured as possible, Day Started early morning Layout all
tasks for that day assign priority and deadline of each task. Jump on it. If any other high
priority task comes up I do restructure my plan accordingly.
Quality Concern: Ensure 100% quality in all my assignments , so perform very precise
Proactive in taking assignments and proactive in contacting other teams to resolve
issues/concerns in quick way.
c. Project Teams how large are the teams you worked on?
Ans : I was working in a project where we were 12 members in total.in which we were 4
testers including the lead.
d. Do you prefer working on teams or working independently? Why?
Ans: I can prefer both..
I prefer to work in a team as we get many more new ideas for testing, and like if I am struck
somewhere I can take help of others and the same way I can help others, but if I have to work
independently then also I can manage to do that.

Work Environment
Are you okay with working in a project room with other People? Privacy is limited and there
can be distractions. Are you able to work in that kind of environment?
Ans: Actually in my previous project, complete team use to sit in a room that helped us a lot in
like if I found an error, then n there I use to ask my developer and find out if thats an valid
defect or no, instead of raising a defect which is invalid and takes a lot of time to come back
again to me.
f. Are you planning to relocate here or are you going to commute?
Ans : Yes. I am ready to relocate to Madison.
g. Do you have any Mentoring experience?
Yes. I do. Whenever my lead went out he asked me to get the status from my team other test
members. I took status from team and assign the work where ever needed and send the report
to my lead.
h. Availability
I can join as soon as possible, able to join date mentioned in requirement.
j. Do you have experience with the coordinator, test manger and simulators on servers?
a. Looking for answer around setting up a test environment outside of their local pc (NO).

8. Do you want to say anything else which we

havent covered? Or DO you have Questions for me?
Ans: Yes. Looks like u covered everything as for as my qa experience.
**Ask following Questions to interviewer: one after another
I would like to know about project?
Technologies used in Project?
Which SDLC they Used for this?
QA Team Strength?
After completion of these questions
Thank you very much for giving an opportunity to have this interview.