1. CURRICULUM VITAE
Sudha Akshaya Mobile: 9900349583
Email:sudha.akshaya6@gmail.com
OBJECTIVE
Aspire to achieve the best standards in the field of software testing in the corporate
sector through a continuous process of learning, innovation, integrity, determination and
hard work with a view to contribute to the success of the organization
Experience Summary
Having 3.5 years of experience in Software Quality Control
Testing Skills
Extensive knowledge in Software Development Life Cycle (SDLC) and Software
Test Life Cycle (STLC) and Test Methodologies.
Preparation of Test Cases by using Test case design techniques.
Extensive work experience in different types of Testing: Smoke Testing, Functionality
Testing, Integration testing, System testing, Regression testing
Experience in Identifying Test Scenarios.
Having work experience in writing Test cases by using Test case design
techniques
Having work experience in reviewing and execution of Test case.
Having experience in documenting reports like Test Execution Report, Defect
Report.
Having Experience in Defect Tracking & Reporting
Participating in all levels of Reviews, Peer Reviews.
Ability to understand Functional Specification documents and Requirement
Specification
Expertise in writing Test Cases by applying Test Case Design Techniques
Involved in preparation of Requirement Traceability Matrix.
Performed database validation writing SQL queries.
Working experience in Test Management Tool QC.
Writing Test Scripts for the identified Test cases using QTP tool.
Executed the automated scripts for regression testing using QTP.
PROFESSIONAL EXPERIENCE
Working at Itechnosphere pvt limited Sept 2012-Jan 2013
Worked at IBM for Melstar information systems as Test engineer from Jan
28 2011 –Sept 2011.
worked at QZensoft solutions as test engineer from April 2009-Dec 2011
2. Education Qualifications:
Masters in Computer Applications from Madurai Kamraj University.
TECHNICAL SUMMARY
RDBMS : Oracle 11 g
Mobile Handsets tested : Kyocera M2000, Samsung S2410, Samsung R460
Monitoring tools used : Winscp, PuTTy, QPST, QXDM.
Functional Tools : QTP 9.2
Defect tracking tool : QC 10.0, Bugzilla 3.4.6
PROJECT DETAILS
Project # 1
Title : Payroll & Personnel Add on
Client : Bank of western Australia
Role : Manual Test Engineer
Team Size : 1
Project Description:
Double entry book keeping system calculates the credits and debits of the system for
each transaction. In the asset module mainly covers the capital appreciation of the
company, revenue earned the stake holdings of the company.Regular report generation
is facilitated by data management units in coordination with networked application.
Responsibilities :
Tested the prototype of the application using static testing.
Writing of test case using use case.
Review test cases
Execution of Test cases
Report Bugs/Defects and perform defect analysis.
Regression testing is implemented in various phases of development and test
cycle
Performing sanity,smoke testing ,functional testing,Intergration
Interacted with development team in analyzing defects
Involved in writing and excecuting the test cases for various testing module.
Good knowledge and understanding of Business rules and application.
Understanding V& V model of software development life cycle
3. Project # 2
Title : Ariba V9
Client : Walmart
Role : Automation Engineer
Team Size : 4
Duration : Jan 2011 –Nov 2011
Environment : Java ,jdbc server,jsp
Testing Tool Used : QTP 10.0
Project Description:
The system generates the punch-in URL and credentials for a supplier contact when the
supplier registration form is submitted.There are many modules in ariba like upstream and
downstream modules based on the various kinds of users. Buyer Users are internal users of
ariba buyers. They have access to all approvable documents and they are grouped into roles
to help legal approvals and rejection of contracts and other related issues. Supplier Users
are external users who can punch into ariba buyer to do collaborative invoicing.
Responsibilities:
Writing Test Scripts for the identified Test cases.
Involved in writing Navigation part of Driver script.
Generated automated test scripts based on Project requirement using QTP
Testing the different screens and the business rules for the application
Executed the automated scripts for regression testing using QTP.
Writing Test Scripts using VB scripting for the identified Test cases.
Involved in writing scripts using descriptive programming
Initially used the Business Process Testing approach to write Test cases.
Reported bugs in the newer version of the modules.
Reviewed Test cases.
Implemented regression testing in various phases of development and test cycles.
Interacted with the team in analyzing defects and issues.
Modified some test cases as per newly added customer requirement.
Tested various screens and business rules of the application.
Executed test cases.
4. Project # 3
Title : Springboard-ETL
Client : cricket communications Inc, US
Environment : Java SE Environment, version 1.6.0.-01, ApacheTomcat
Java servelet API 2.5, oracle JDBC driver 11.1.0.6.0
Role : Manual Test Engineer
Team Size : 5
Duration : Nov 2009 –Dec 2010
Project Description:
The data is extracted from various interfaces so that an updated data is maintained .This
module facilitates various scheduling of the transactional activities .It becomes a tedious
task to extract data from the data base and regularly keep track of important volatile
data. As a result spring board has enabled ETL services to keep track of the following
The following transaction data is made available:
• Purchase and download transactions
• Widget usage
• Idle screen usage
• SPRINGBOARD transactions
Responsibilities:
Testing the different screens and the business rules for the application.
Performing Sanity/Smoke Testing, Functional Testing, Integrationtesting
Regression Testing.
Modified some Test Scenarios and Test Cases as per newly added Customer req
Involved in reporting bugs using Bugzilla.
Involved in weekly status reporting and official meetings
Report Bugs/Defects and perform defect analysis
Performed database validation writing SQL queries.
Testing the different screens and the business rules for the application.
Involved and designing Test Cases based on Requirements.
Executions of Test cases and prepare the Defect reporting.
5. Regression Testing is implemented at various phases of the development and test
cycles
Project # 4
Project Name : Rdvr
Client : Cox u.s
Environment : Java SE Environment, version 1.6.0.-01, Apache Tomcat
Role : Manual Test Engineer
Team Size : 6
Duration : April 2009-Nov 2009
Project Description:
The purpose of this application will provide cox subscribers the ability to view their specific home
TVlistings. The rdvr scheduler is one such application which interacts with the server for its
operations. Cox wireless software allows subscribers to view their tvlistings and record television
programs or series without having to be in front of their television sets. The client and server are
limited to the functionality.
Responsibilities
Involved in writing and executing the Test Cases for various testing modules
Performing Sanity/Smoke Testing, Functional Testing, Integration testing
and Regression Testing.
Modified some Test Scenarios and TestCases as per newly added Customer
Requirement.
Involved in reporting bugs using Bugzilla.
Involved in weekly status reporting and official meetings
Report Bugs/Defects and perform defect analysis
Performed database validation writing SQL queries.
Involved and designing Test Cases based on Requirements.
Executions of Test cases and prepare the Defect reporting.
Regression Testing is implemented at various phases of the development and test
cycles.
Interacted with development team in analyzing the defects.
6. Involved in writing and executing the Test Cases for various testing module
Good knowledge and understanding of business rules for the application
Understanding of V & V model of software development life.
7. Involved in writing and executing the Test Cases for various testing module
Good knowledge and understanding of business rules for the application
Understanding of V & V model of software development life.