Narayana.

Mobile: +91-9916553161 mqc.narayana@gmail.com

EXPERIENCE SUMMARY:

Having 3+ years of Experience in Software Testing on Web based application, ERP and Windows Applications. Involved in all levels of Software Testing Life Cycle (STLC). Good exposure to all stages of Software Development Life Cycle(SDLC) Good Experience in Oracle EBSuite Applications R12 Testing. Worked on various modules(Manufacturing & Project,AR,OM). Expertise in testing product and project. Involved in client interaction. Performed all phases of Testing Methodologies that included Functionality Testing, Sanity testing, Regression Testing, Integration Testing, System Testing, Interface Testing and End to End testing. Good experience in design of Test Cases and Executing Test Cases. Strong experience in Quality Centre and Bugzilla. Good experience in UNIX, Sql testing. Well versed with all the Testing concepts and Methodologies. Good experience on Bug Life Cycle. Excellent problem solving skills, good interpersonal skills and good communication skills. Flexible and versatile to adapt to any new environment and work on any project.

PROFESSIONAL EXPERIENCE: Working as a Software Test Engineer in Intelligroup Asia Pvt Lmt, Bangalore since August 2009 to April 2011. Worked as Software Test Engineer for Accenture Pvt Lmt, Bangalore from June 2007 to July 2009. EDUCATIONAL QUALIFICATION: B.Tech. (Electrical & Electronics) from JNTU Hyderabad. TECHNICAL SKILLS: Operating Systems : Windows 2000/XP , UNIX Testing Tools Test Management Tools Languages Databases : : : : Manual Testing Quality Center , Bugzilla,, BPT in QC C, HTML MS Access, SQL

PROJECT PROFILE: Project # 1: 1

Project Name : COSMOS Client : ALMAC - UK Role : Software Test Engineer Environment : Oracle Apps R12, Windows 2003 Server Modules : Distribution, Manufacturing and Project,AR,OM Duration : December 2009 Till Date Company Profile: Almac has the most comprehensive range of integrated drug development services available to the pharmaceutical / biotech industry. The privately owned company employing 2,500 dedicated professionals is headquartered in Craigavon, Northern Ireland and has extensive facilities in the UK and US. Over 600 companies worldwide, including all the market leaders, use our services, testament itself to the quality, innovation and efficiency of our business. Responsibilities: Understanding the business requirements from Client. Developed Test cases based on the Functional requirements. Involvement in Test Excution and Defect Reporting using QC. Performing Sanity, GUI, Functional and Regression Testing. Involved in Regression Testing for each modified build of the application. Preparing and reporting the daily status report worked by team to the Client. Guided the new team members in QC test cases creation and execution. Reviewing Test conditions, Test cases and Test data. Execution of Test cases manually from Quality Center. Analyze the test results, documented and reported through Quality Center. Defect Report, Defect Tracking and Analysis by Quality Center. . Project #2: Project Name : OB system Client : Fleet Bank, Boston, MA Environment : Java, Windows XP, Oraclr10g Testing Approach : Manual testing, Mercury QC. Role : Software Test Engineer Duration : August 2009 to December 2009 Domain : Financial Services - Banking Description: Web Based Banking Application at Fleet Bank. This application is designed for the customers of the bank to manage their finances through Online Banking. The customer through Internet banking can access his accounts to view transactions, pay bills and transfer money, loans/mortgage being a part of the application. This application has different modules like Online Banking/Web Banking and Online Mortgage. Each of the modules stated above gives different facilities to the customers of the bank as well as to the non-customers. Non-customers can apply for and get the rates of any type of insurance given by the bank and also apply for the Home Mortgage. Any one can know about the rate of interest for the Home Mortgage before getting the mortgage approved.

Roles & Responsibilities: Understanding the BRS and SRS. Involvement in Test Design with respect to Test Plan and using Black box Testing Techniques . Involvement in Test Execution and Defect Reporting using QC. Performing Sanity, GUI, Functional and Regression Testing. Involved in Regression Testing for each modified build of the application. 2

Defects were raised in Quality Center and maintained to keep track of the bugs for re-test and close operations. Used Quality Center as the test repository for executing test cases, generating various reports and graphs for further analysis Involved in test case review meetings Communicating with other teams members (Development Team, Technical Support, Business Support) in order to resolve the issues

Project #3: Project Name : PaymentNet4 Client : JP Morgan Chase, USA Environment : Java, Windows XP, Oracle10g Testing Tool : QC Role : Software Test Engineer Duration : August2008 to June 2009 Domain : Financial Services Banking Description: PaymentNet4 is an online GUI application which uses web service and batch processing to allow JPMorgan clients to manage their employees Commercial Card spending. Some of the general functionality is included below: Allows JPM Administrators to setup client organizational information for initial client setup. Allow organization administrators to setup and manage their organization configurations including: roles/hierarchy, employees, accounts, merchants and more. Allows cardholders and order requestors to monitor, query and track their orders, transactions, payments, statements including reporting functionality related to these modules. Allows import and export of various functional modules based on defined configurations. Roles & Responsibilities: Understanding the BRS and SRS. Involvement in Test Design with respect to Test Plan and using Black box TestingTechniques . Involvement in Test Execution and Defect Reporting using QC. Performing Sanity, GUI, Functional and Regression Testing. Involved in Regression Testing for each modified build of the application. Defects were raised in Quality Center and maintained to keep track of the bugs for re-test and close operations. Used Quality Center as the test repository for executing test cases, generating various reports and graphs for further analysis Involved in test case review meetings Communicating with other teams members (Development Team, Technical Support, Business Support) in order to resolve the issues

Project #4: Project Name Client Environment Testing Approach Role Team Size Duration Domain

: : : : : : : :

BT E2E Trouble to Resolve British Telecom, Uk Windows XP,Siebel, UNIX, B2B, SQL QC Software Test Engineer 4 June2007 to July2008 Telecommunication 3

Description: British Telecom is one of the worlds largest telecom companies offering telephones all over the UK both hard lines and mobile services. We mainly deal with their call centre application called the one view. My Modules: Trouble to resolve deals with the trouble shooting activities for BT while the sales is on and post sales (Value for money service) Testing the End-to-End scenarios provisioning orders made by the advisor. Common Terminologies: Faults: A fault is defined as an issue with the customer telephone/ BB line resulting in no service or poor quality of service. Complaints: Customer unhappy about the way things are handled, be it fault resolution or order handling or be it to register about mishandling done by BT. Escalations: Self explanatory can be done for an order or a fault or a complaint if the customer service is not provided on time. Compensation: Customer service disruption leads to payment o compensation to customer, normally preceded by a fault or complaint Roles & Responsibilities: Understanding the BRS and SRS. Designing Test Cases, Execution of the test cases and Reporting Bugs. Involved in functionality testing, user interface testing. Involved in Regression Testing for each modified build of the application. Defects were raised in Quality Center and maintained to keep track of the bugs for re-test and close operations.