qa tester
Resume:
Kalpesh Parikh
Mobile: 513-***-**** Email: ************@*****.***
PROFESSIONAL SUMMARY:
• 8 + years of experience in Quality assurance and testing diverse applications on various platforms
• Strong expertise in testing Web-based/Unix based, webservices, XML based and backend testing’s in different environments
• Extensive experience in Manual and Automation testing of various applications on different environments
• Extensive experience in Agile and waterfall methodologies.
• Software Development Life Cycle and Test Methodologies from project definition to post-deployment documentation
• Extensive working experience in Financial, Mobile Testing, Health Care, Insurance, Banking domains
• Data Driven and Back end testing using QTP and SQL
• Expertise in Support and Testing of Telecom Customer Care, Amdocs - Telegence, Ensemble, Enabler and Billing System
• Experience in writing test plans, defining test cases, developing and maintaining test scripts from Requirements and Used Cases
• Effective Defect Tracking and Reporting using Quality Center.
• Manually performed Back-End testing by writing SQL queries and stored procedures
• Expertise in Black Box testing with a complete Quality Assurance cycle-from testing, defect logging, verification of fixed bugs.
• Experience in performing Functional Testing, System Testing, Integration Testing, E2E Testing, Smoke Testing, White box, Grey box, User Acceptance Testing and Database Testing using various tools.
• Good Understanding on AS400
• Extensive working knowledge in Unix and Windows platforms
• Experience in creating Requirements Traceability Matrices to ensure comprehensive test coverage of requirements
• Excellent communication and interpersonal skills, ability to conceptualize and learn quickly, good analytical reasoning and high compliance to new technologies and tools.
• Good team player with excellent written and verbal communication and interpersonal skills
TECHNICAL SKILLS:
WORK EXPERIENCE:
Client: T-Mobile, Atlanta, GA
Role: QA Analyst Jan 11 - Till Date
This is a testing project done for T-mobile in the process of Amdocs Ensemble system. The modules related to CSM, MAF, MPS (rating, guiding) billing, FBF were tested from Operational and functional point of view. Presently T-mobile is using MAESTRO Scheduler to run all the Production Billing, End of Job/Month, and Payments jobs for all Cellular Billing cycles.
Responsibilities:
• Prepared Test Plan, Test cases based upon Business, Detail and User Requirements using Quality Center
• Worked in Agile environment, involved in Project Effort Estimation, attended SUM and retrospection sessions.
• Involved in System Testing, Regression Testing and Integration, Functional, E2E and UAT test support.
• Reported bugs using Jira, verified fixes and closed bugs.
• Extensively involved in testing CSM module with activities like BAN creation, activate/suspend/cancel/restore subscribers, and A/R activities.
• Responsible for testing all new available Price Plans/Offers, Discounts, Promotions, Usage, PP Change, Pooling etc specific to Conversion etc.
• Involved in testing Billing module for Billing Jobs and running AR/Billing jobs for different Bill Cycles
• Performed web testing for this application to test HTTP links in all versions of Netscape and Internet Browsers.
• Tested Billing module from operational and functional point of view using a batch scheduler (MAESTRO) and also ran all billing jobs manually.
• Written SQL queries to extract the data from Oracle database for data verification.
Environment:
• Amdocs Ensemble, API’s, INTERFACES, Quality Center, Java, Oracle, UNIX, Windows XP/2000, XML, TOAD, SQL PLUS, Utilized Agile/Scrum, Microsoft Project, Jira, Web Services,
Client: SXC Health Solution Corp. Lisle, IL Feb 09 – Dec 10
Role: QA Analyst
Responsibilities:
• Analyzed Software Requirements documents and Business Requirements documents to get a better understanding of the system on both Technical and Business perspectives.
• Executed test plans, test scripts manually using Quality center.
• Planning and Estimating manual to automation transition effort for project especially in the area of Use case Identification for covering major functionalities.
• Responsibilities include acceptance testing, functional testing, Integration testing, System testing, performance testing.
• Documented baseline configurations.
• Managed Rational Functional and Performance Testing.
• Developed Integration Test Plans, System Test Plans and Performance Testing.
• Performed back end testing for data Integrity by writing simple SQL queries to JOIN queries in TOAD for database testing.
• Used IBM power system for accessing data tables.
• Maintained traceability matrix on SDRS, DRS, Test cases and Test results.
• Made extensive use of MS Office tools to create and maintain documents such as test plans, test execution and test results documents.
• Responsible for Actuate Report Server testing efforts to meet the reporting needs.
• Fully involved with Integration, Functional, System and user acceptance testing (UAT) of the application.
• Worked closely with development team in creating automated scripts for the application.
• Provided functional support to developers and QA Engineers.
• Used Clientele as Defect tracking system to report & track errors in the various releases of the application.
• Prepared status summary reports with details of executed, passed and failed test cases.
• Participated in daily calls with business users, developers and weekly status meetings.
• Provided a weekly project report that includes Test Metrics and status reports.
Environment:
• Java, Oracle, Unix, WinSCP, SQL, J2EE, Putty, Quality Center, SOAP UI, XML, TOAD, MS Office
Client: 1st Mariner Bank, Baltimore, MD.
Role: QA Tester Oct 08 – Jan 09
This was an Online Banking System. I worked as QA Analyst at 1st Mariner online Banking application that enables the bank customers to access their various accounts through the Web Site. It was a J2EE application and the backend was Oracle. Customers can track charges and payments before they receive their statements, Transfer the funds, Pay their bills, Stop payments and Review past statements.
Responsibilities:
• Analyze Business Requirements Document and System Requirement Specification to develop new QA procedures and recommend changes for the better performance
• Followed the UML based methods using Rational Rose to create Use Cases, Activity Diagrams / State Chart diagrams, Sequence Diagrams, Collaboration Diagrams
• Create Test Plans, Test Cases and Test Sets accordingly associated with each requirement using Mercury Quality Center for acceptance, functional and integration testing.
• Did functional testing manually & also used Mercury Quality Center it to track defects.
• Involved in all phases of testing like Smoke, Functional, User interface, and System testing.
• Developed the Positive and Negative Test Cases for various modules based on the business requirements, process flow, flow charts and program specifications.
Environment:
• UNIX, J2EE, Oracle, Quality Center, SOAP UI, XML, TOAD, WinSCP
CLIENT: BANK OF THE WEST, SAN RAMON Dec 06 – Sep 08
PROJECT – MOBILE BANKING
Bank of the West Mobile banking project focused on providing following services:
1. Text/SMS Message: Mobile Text banking gives customers the ability to send certain text message commands to Bank of the West using a shortcode ( a 5-digit phone number belonging to your financial institution) to obtain account balances, view account transaction history, or perform account transfers.
2. Mobile Web: Mobile Web is a website that is accessed through mobile device. It contains many of the features of Online Banking, just formatted and optimized for viewing on a small screen. By signing on to a mobile version of Online Banking, customers can view account balances, transfer funds, and find Bank of the West locations.
3. Mobile App: With the Mobile Banking app, registered customers can access important account information from your iPhone, Blackberry and Android phone. View account history, make transfers, get balances, and more. Using GPS capability, the app can even guide customers to the nearest ATM or Branch location.
ROLE & RESPONSIBILITIES:
• Created Test Cases as per requirement for multiple parallel releases.
• Involved in Gap Analysis Testing, Sanity/Smoke testing, Integration testing, Porting Testing, Localization Testing, Usability Testing, Performance testing, Regression Testing
• Performed Installation testing via OTA.
• Used Device Anywhere Test Center and Test Manager to perform testing of the chat conversations, Send Receive Picture messages, MMS, sending SMS from the chat, calling from the conversation
• Handled Certification tests for Java Verified.
• Automated few test cases for Image & text comparison through FoneMonkey tool.
• Bugs reporting on bug tracking tool &updating the status of the bugs.
• Conducted Defect Scrub meetings.
• Extensively used Performance Monitoring tools to analyze the System resources bottlenecks like Memory Leaks, CPU and Network Bottlenecks as well as problematic application and DB components.
• Conducted security testing.
• Provided testing Status Reports on daily basis.
ENVIRONMENT:
• iPhone OS, Android, Blackberry, J2ME
DEVICES: iPhone, Nokia, Samsung, Sony Ericsson, Motorola.
Client: MetLife Insurance, New York, NY Apr 05 – Nov 06
Role: QA Team Member
Responsibilities:
• Analyzed the user requirements by interacting with system architects, developers and business users.
• Creation of Test Cases and Test Director and executing the test cases.
• Functionality testing is performed manually.
• Involved in writing Test Scripts for the main application functionality such as validation, business work-flow.
• During testing life cycle, performed different types of testing like system testing, Integration testing and Regression Testing.
• Regularly involved in discussion with developers with the test results to improve the performance.
• Performed Manual Testing on different Modules of the Application.
• Investigated software bugs and maintained reports, tracked defects.
• Prepared detailed reports of Bugs and Defects, Pass/Fail reports and comparison analysis, and interacted with the development teams, application and data architecture team, migration and build teams and the DBA team to report and correct defects.
• Identifying bugs and interacted with QA Lead and Developers to resolve the issues of bugs.
• Worked on Test Director 7.6 for Loading, Executing and preparing the Test Results.
• Developed and conducted system and user acceptance test plans on completion of system testing before installation of the application on user environment.
• Created SQL Scripts to run against database testing and for populating, updating and deleting the data from the database.
• Used the Test Director as bug-tracking tool to centralize the bugs and also to follow up the bug status.
Environment:
• Java, SQL, Oracle, QTP, VB Script, Quality Center, UNIX, Linux, XML.
Client: Citibank, Columbus, OH July 03 – Mar 05
Role: QA Engineer / Developer
This software automates a banking procedure having different types of accounts namely Savings, Current and Recurring account. Interest on these accounts is calculated automatically twice a year. Each and every transaction is updated with petty cash master account. It will take care of maintaining minimum balance depending upon the account type and cheque facility. It also helps in maintaining the customer details like adding a new customer, deleting an existing customer, closing an account, modifying customer details etc., It also generates reports like account wise report showing account number and the last transaction with all details for a particular period.
Responsibilities:
• Based on the requirements documents and system specifications, developed Test plans and Test cases
• Performed GUI and Functionality testing of the application
• Documented Test cases, Test results and Test procedures
• Interacted with end users to obtain specific system requirements
• Reported Software bugs and interacted with developers to resolve technical issues.
• Manual testing was done for User Acceptance
• Presentation of recent changes in applications and database to users of various Departments.
Environment:
• Oracle 7.3, Windows 95, Visual Basic 6.0, PL/SQL and SQL* Plus.
Contact this candidate