1. BHANU PRAKASH.S
E-mail: somavarapubhanuprakash@gmail.com
Mobile: +91-9844428081
SUMMARY
 Having 3.6 years of experience in Testing.
 Having 1.2 experience of experience in Automation Testing using Ascential Tool by
Zeenyx.
 Automated several orders in Siebel application for Automation environment using
Ascential Automation Tool.
 Executed Several Regression test cases by Automation Tool. Few Days I involved in UAT
Testing also.
 Involvement in Integration, Functional, System, Regression, User Acceptance Testing.
 Having good work experience in executing test cases and reporting defects.
 Good exposure to Bug Life Cycle using RTC & QC(ALM).
 Good knowledge in SDLC and STLC.
 Good knowledge on understanding Software Requirement Specification.
 Working as a Team member and activities involved in writing test cases.
 Participated in analyzing test cases and execution of test cases and status report.
 Good Functional Knowledge on SQL.
 Functional Knowledge on UNIX commands.
WORK EXPERIENCE
 Working as a Software Engineer in Quality Kiosk Technologies Bangalore from Dec-
2015 to till Date.
 Worked as a Software Engineer in IBM India Pvt Ltd, Bangalore from May 2015 to
Nov 27-2015.
 Worked as a Software Engineer Associative in Accenture Services India Pvt Ltd,
Bangalore from Oct 2012 to Mar 2015.
EDUCATIONAL QUALIFICATION
 M.C.A from JNTU Kakinada.

2. TECHNICAL SKILLS
Automation Tool : Ascential (by Zeenyx)
Languages : C, Zee Scripting.
Management tool : QC (ALM),RTC Tool.
Operating System : Windows 7, UNIX.
Project Details
Dec 2015 to Till Date
Project : CONNECT
Client : Toyota Kirloskar Motor Pvt Ltd
Environment : Web Based Front End Testing
Management Tool : RTC
Operating System : Windows 7
Data Base : SQL
Description:
Connect System introduces more effective risk management for dealers to create FI (Field
Information), FIFR (Field Information Feedback Report) and submit to TKM Users(CSD &
QA) in order to identify the Defective parts found while talking Job order from customers
and also later dealer can claim the money from TKM and TKM people can claim the money
from the supplier through TMAP HUB.
TFQS : Toyota Field Quality System is used by Dealer to create the FI for every one Job
Order(for one vehicle) so that TKM Users give feedback with FIFR , Then after TKM CSD
user create RCA and RCAR for supplier to send the failed parts and effected parts
information. TKM users can also create SPOC creation for Dealers.
Dealer Communication:
TKM Users can share servicing information and service Tax amount information related to
warranty through Dealer communication Module through TKM upload and assign bulk
documents to dealer and role TKM user can create documents and assign to the dealers and
corresponding roles.
Responsibilities:
 Understanding Functional Requirements.
 To perform functional testing to check if the business requirements are met.
 Performed Sanity, Functional, System and Regression Testing.
 Prepared and Executed Test Cases as per System Requirements.
 Performed various Black Box testing Methodologies like Functional Testing and
Regression Testing.
 Defect Tracking and Reporting using RTC.

3.  Functional Testing was performed to test the overall project functionality to meet the
requirements.
 Assist in the development and reviews of process test scripts; expand these scripts
during testing as necessary.
Project Details
May 2015 to Nov 2015
Project : Sprint
Client : Sprint
Environment : Web Based Front end Testing
Management Tool : QC (ALM)
Operating System : Windows 7
Data Base : SQL
Description:
Sprint, is an American Telecommunications holding company,that provides wireless services
and is a global internet carrier. It is the fourth largest network operator in United States.
The company offers wireless voices messaging, broadband services through it’s various
subsidiaries under the Boost Mobile, Virgin Mobile. Sprint operates second, third & fourth
generation mobile networks, allowing the customers to use GPRS,EDGE, UMTS up to HSPA
+ and LTE for data connections.
I was involved in Testing Activation Order, Usage Creation using 7KS application &
Verification in N8S and other web applications.
1. Perform Activation in any tool (according to test case)
2. Create usage in an automated usage tool.
3. Verify usage in any application used for account maintenance activities.
Responsibilities:
 Understanding Functional Requirements.
 To perform functional testing to check if the business requirements are met.
 Performed Sanity, Functional, System and Regression Testing.
 Prepared and Executed Test Cases as per System Requirements.
 Performed various Black Box testing Methodologies like Functional Testing and
Regression Testing.
 Defect Tracking and Reporting.
 Functional Testing was performed to test the overall project functionality to meet the
requirements.
 Assist in the development and reviews of process test scripts; expand these scripts
during testing as necessary.

4. Project Details
Oct 2012 to Mar 2015
Project : HanseNet
Client : Telefonica
Automation Tool : Ascential
Technologies : VB Script
Environment : Siebel CRM
Data Base : SQL ,UNIX.
Description:
Telefonica Germany operates second, third and fourth generation mobile networks, allowing
customers to use GPRS, EDGE, UMTS up to HSPA + and LTE for data connections. Most of
O2 plans are available both in pre-paid and post-paid version, including the all in one flat
rates called O2O and O2 on for enterprise customers. Together with Microsoft and Vision
app, Telefonica Germany provides a cloud service for Hosted Exchange
I have involved in testing Activation Order, Move Order, Change, Product Change and
Termination Order modules.
Activation: In Activation Order they are two types of customers 1.Residential & Micro
Business customers. Residential customer having two products, Analog & ISDN 2. Micro
business customers also have Analog & ISDN (Multiple DSL Numbers).
Change: They are two types of Change Order 1.Fast Change 2.Standard Change Order. In
Standard Change Order we can change the package, we can select option security values,
Prevention & detention, Promotions. In Fast Change Order we can select only Promotion
items, Option security items.
Product Changer: In Product Change Order we can change the product from Analog to
ISDN and ISDN to Analog. We can select the promotion items & Option security values &
packages, Prevention & detention.
Move: In Move Order we can Move from one area to another area. Based on the product
Termination: In Termination they two types. Termination Order & Termination request.
Responsibilities:
 Understanding Functional Requirements.
 Functional Testing was performed to test the overall project functionality to meet the
requirements.
 Developed and executed automated test cases and Scripts, validated the results using
Ascential.
 Developed and executed automated test cases and Scripts, validated the results using
Ascential.
 Performed Sanity, Functional, System and Regression Testing.
 Prepared and Executed Test Cases as per System/functional Requirements.
 Performed various Black Box testing Methodologies like Functional Testing and
Regression Testing.
 Functional Testing was performed to test the overall project functionality to meet the
requirements.
 Assist in the development and reviews of process test scripts; expand these scripts
during testing as necessary.

5. Project Details
Title : TTM (Trouble Ticket Management)
Client : Telefonica.
Technologies : Java.
Technologies : VB Script
Description:
TTM-TROUBLE TICKET MANAGEMENT is a system which will trouble shoot all the issues
related to customer, network. TTM will interact with third party systems like DIL and GTG to
complete all ticket related issues. In TTM, trouble ticket can be created in different ways by
using different systems like Excalibur, OrderBook and Manually. TTM will support all the
customers in German and Italian users related to Line Owner issues by creating tickets and
resolving them. TTM will act as middle ware system and interact with third party systems
and receives the requests from external systems as well.
Once ticket/issue has been resolved by customer support and those tickets can be closed by
customer. If user have the option to acceptance and he can reopen the same ticket.
Responsibilities:
 Understanding Functional Requirements.
 Performed Sanity, Functional, System and Regression Testing.
 Prepared and Executed Test Cases as per System Requirements.
 Functional Testing was performed to test the overall project functionality to meet the
requirements.
 Defect Tracking and Reporting.
I hereby declare that all the above stated information is true to the best of my knowledge.
(Bhanu Prakash)

6. Project Details
Title : TTM (Trouble Ticket Management)
Client : Telefonica.
Technologies : Java.
Technologies : VB Script
Description:
TTM-TROUBLE TICKET MANAGEMENT is a system which will trouble shoot all the issues
related to customer, network. TTM will interact with third party systems like DIL and GTG to
complete all ticket related issues. In TTM, trouble ticket can be created in different ways by
using different systems like Excalibur, OrderBook and Manually. TTM will support all the
customers in German and Italian users related to Line Owner issues by creating tickets and
resolving them. TTM will act as middle ware system and interact with third party systems
and receives the requests from external systems as well.
Once ticket/issue has been resolved by customer support and those tickets can be closed by
customer. If user have the option to acceptance and he can reopen the same ticket.
Responsibilities:
 Understanding Functional Requirements.
 Performed Sanity, Functional, System and Regression Testing.
 Prepared and Executed Test Cases as per System Requirements.
 Functional Testing was performed to test the overall project functionality to meet the
requirements.
 Defect Tracking and Reporting.
I hereby declare that all the above stated information is true to the best of my knowledge.
(Bhanu Prakash)