Objective:

A position which allows me to apply my software testing skills in an enlightened, dynamic and high paced environment.

Skill Set:

A. Testing
Manual Testing
Mainframe Testing
Performance Testing

B. Technical
Tools Used: Quality Center 9. 0, Performance Center 8. 1, Team Quest, VuGen 8. 1, Test Director
Databases: DB2, Sybase
Interface: RUMBA for Mainframe 7. 1. 1
Environments Used: Development, Integration, Acceptance

C. Domain
Knowledge of different Practices like DB, DC, H&I, Payroll, Retail.
Managing of Integrated Database (IDB) for the above mentioned practices.

Organisational Facets:

Currently working as an Associate Software Engineer in Reputed IT company, Bangalore, since July 2006 (1 Year 6 Months till date)

Key Projects Handled:

1. Project Name: HP Data Integration Project
Team Size: 4
Duration (in mths): 3
Tools Used: Test Director, Quality Center 9. 0
Databases: DB2, Sybase
Interface/ Platforms: RUMBA for Mainframe 7. 1. 1
Applications Used: DBCS (Defined Benefits Client Server), PSW - DC (Plan Sponsor Workstation-Defined Contribution)
FPRS (Fidelity Participant Recordkeeping System)
Environments Used: Integration, Acceptance
Description: This project involved removing discrepancies of indicative elements (like Name, DOB, Gender, Date of Termination, Adjusted Date of Hire Etc) between different practices like DB, DC, HW, PR for client HP. This was achieved by creating a nightly run program which used to go against the database which was changed recently, compare it with IDB and in turn change the values of other practices as per the new change. We were involved in creating test cases for the same, preparing test data and executing the test cases.
My Role: I was involved in preparing the Test Cases, preparation of data required, executing the test cases using Quality Center.

2. Project Name: Performance Testing - Kintana Load Testing
Team Size: 3
Duration (in mths): 1
Tools Used: Performance Center 8. 1, Team Quest
Interface/ Platforms: Windows
Description: Kintana is a defect tracking tool as well as time logging tool for Fidelity. Every Friday hundreds of users use this tool for logging time for the week, due to which the performance of that tool becomes very important when multiple users are using it simultaneously.
We performance tested that tool using the performance center for various scenarios which generally happen when multiple users use it.
Once the test was completed, we used to generate reports for that test using Team Quest which generated reports like Memory Utilization, CPU Utilization etc. which were then sent to the client for further analysis.
My Role: I was involved in modification of test scripts, executing the test using performance center tool, generating results/ reports using the performance center and team quest.

3. Project Name: Supplemental Wage Withholding (SWW) Project
Team Size: 4
Duration (in mths): 2
Tools Used: Quality Center 9. 0
Databases: DB2
Interface/ Platforms: RUMBA for Mainframe 7. 1. 1
Applications Used: FPRS (Fidelity Participant Recordkeeping System)
Environments Used: Integration, Acceptance
Description: This project involved calculating the Supplemental Wage for a particular participant and levying taxes as per new norms.
My Role: My role was to build the test cases for the same and creating test data in the form of 80 byte flat file, which in turn would be FTPed to Mainframe and executing the same.

4. Project Name: Performance Testing - Kintana Load Testing - Day Light Saving
Team Size: 3
Duration (in mths): 1
Tools Used: Performance Center 8. 1, Team Quest, VuGen 8. 1
Interface/ Platforms: Windows
Description: The test mentioned above was carried out again when the Day Light Saving was started. But this time around some more scenarios were added along with more number of VUsers. Also scripts were recorded using VuGen which were used in running the test.
My Role: I took initiative in recording the script using VuGen for the required scenarios, executing the test and pulling the reports/ results from the Team Quest and Performance Center.

5. Project Name: DC Only to SCF Project - FCDE System
Team Size: 3
Duration (in mths): 1
Tools Used: Quality Center 9. 0
Databases: DB2
Interface/ Platforms: RUMBA for Mainframe 7. 1. 1
Applications Used: FPRS (Fidelity Participant Recordkeeping System)
Environments Used: Integration, Acceptance
Description: This Project involved migration of DC Only Clients from FPRS to SCF System. Testing involved verifying that the DC Only Clients are being routed to SCF instead of FPRS and building test cases for the same and executing them.
My Role: I played a major role in the building of the Test Cases according to the requirements, creating test data, executing the test cases and verifying the results.