SAP Test Automation Strategy

<Customer Name>
Table of Contents
Version history.................................................................................................................................4

Sign off..............................................................................................................................................4

1. Introduction...............................................................................................................................5
1.1. Document purpose..............................................................................................................5
1.2. Target audience...................................................................................................................5

2. Current SAP Landscape...........................................................................................................6

2.1. SAP Project Schedule.........................................................................................................6
2.2. Existing SAP Landscape.....................................................................................................6
2.3. Current Testing Strategy......................................................................................................7
2.4. Current Testing Team..........................................................................................................7
2.5. Current Tools Sets...............................................................................................................7

3. Future SAP Landscape...........................................................................................................10

3.1. Critical Areas.....................................................................................................................10
3.2. Recommended Automation Tools.....................................................................................10

4. Overall Automation Testing Approach.................................................................................12

4.1. Process Initiation...............................................................................................................12
4.2. Tools Implementation........................................................................................................13
4.3. Testing Center of Excellence.............................................................................................14
4.3.1. Evolution of testing services.....................................................................................................................14
4.3.2. Center of Excellence................................................................................................................................ 15

5. Automation Methodology.......................................................................................................16
5.1. SAP TAO Process Framework..........................................................................................16
5.1.1. Discovery.................................................................................................................................................. 16
5.1.2. Design...................................................................................................................................................... 16
5.1.3. Construction............................................................................................................................................. 16
5.1.4. Execution.................................................................................................................................................. 17
5.1.5. Analyse..................................................................................................................................................... 17
5.1.6. Optimize................................................................................................................................................... 17
5.2. SAP TAO Workflow...........................................................................................................18
5.2.1. Typical automation workflow....................................................................................................................18
5.3. SAP TAO Benefits & Limitations........................................................................................19
5.3.1. Automated Business Process Testing......................................................................................................19
5.3.2. Lower Risk................................................................................................................................................ 19
5.3.3. Lower Maintenance Costs........................................................................................................................ 19
5.3.4. Integration................................................................................................................................................. 19
5.3.5. Reuse....................................................................................................................................................... 19
5.3.6. Log Report................................................................................................................................................ 19
5.3.7. Easy Automation...................................................................................................................................... 19
5.3.8. Limitations................................................................................................................................................ 19
5.4. Test Deliverables...............................................................................................................20
5.5. Test Maintenance..............................................................................................................20

6. Governance Model..................................................................................................................22

7. Resourcing Model...................................................................................................................23
8. Roles and Responsibilities....................................................................................................24

9. Organization Structure...........................................................................................................26

Appendices.....................................................................................................................................27
Acronyms......................................................................................................................................27
Attachments..................................................................................................................................27
References...................................................................................................................................27
1. Introduction
<Company Name> current understanding of <Customer Name> automation testing
requirement are based on <Customer Name> SAP services direction to access the existing
automation process methodologies and standards to support the current and planned future
SAP landscape.
The key objectives of this initiative include the following,
 Support <Customer Name> in implementing and standardizing their automation
testing services for the SAP and Non–SAP applications
 To improve application quality through centralized automation processes and
methodologies
 To streamline the <Customer Name> SAP and Non-SAP automation teams on
testing methodologies.
 To substantially reduce the elapsed time in testing and meeting the release
deadlines

1.1. Document purpose

The purpose of this Test Strategy is to define the overall approach that will be taken by the
automation test team when delivering testing services to all of the projects within the
business.
The document helps to clarify the testing activities, roles and responsibilities, processes
and practice to be used across successive projects

1.2. Target audience

The automation testing strategy is intended for the following audience:
 SAP Service
 Solution Architects and designers
 Delivery Assurance Group
 Conversion and Interface teams
 Operations
 Other team members that may be involved in the testing
2. Current SAP Landscape

2.1. SAP Project Schedule

Project Name Abbrev. Applications Date

Enterprise Foundation ERP, PI, TREX, EP/KM, SolMan,

Project ERP iXOS Done

2.2. Existing SAP Landscape

 ERP (CORE)
 Supplier Relationship Management (SRM)
 Mobile Infrastructure (MI)
 Mobile Asset Management (MAM)
 Event Management (EM)
 Process Integration (PI)
 Business Intelligence, including Business Objects
 Customer Relationship Management (CRM)
 Enterprise Portal (EP)
  Search Engine (TREX)
 Solution Manager (SM)
 SAP GRC 5.3

2.3. Current Testing Strategy

Most of the SAP application testing is done manually by the functional team. Some of the SAP
modules with repetitive scenarios are identified for automation. Automation is done using HP Quick
Test Professional for regression testing and executed. Test scripts developed in QTP and stored in
Quality Center projects. Modular automation approach is followed to drive the entire show;
functional libraries and object repository are stored in the shared drive or in local drive to execute.
Entire test execution is done in Quality Center and the reports are generated to monitor the
progress of testing.

2.4. Current Testing Team

 Testing teams aligned by project, department, or business unit

 Varied methodologies, processes, tools, infrastructure and metrics across groups
 Test effort estimation is informal or mandated by top-down schedule/resource
constraints
 Scope for optimized management of resources
 Limited automation testing standards established across the enterprise

2.5. Current Tools Sets

<Customer Name> have implemented and utilizing the tools listed below,
 HP Quality Center
HP Quality Center is implemented in most of the projects in <Customer Name> to
maintain all the testing artefacts. Test cases and scripts are developed in Quality
Center Test Plan and controlled. Entire test execution is done in Quality Center for all
the cycles and releases. Execution and defect reports are generated and monitored the
 progress of testing. Defects are logged into Quality Center and tracked till closure.
Testing metrics are arrived from the reports generated from the Quality Center.

 HP Quick Test Professional (QTP)

HP Quick Test Professional is utilized in few SAP projects in <Customer Name> for
regression testing and for test data generation. The entire test scripts developed in QTP
is maintained in Quality Center projects. Test scripts are developed using modular
approach and data driven approach is incorporated. Java Add-in for QTP is not in place
and so Java projects are not automated. Framework in place has some highlights and
obstacles to implement in all the projects.
Highlights of existing automation framework
1. Quality Center is utilized effectively to store all the automation scripts and
artefacts
2. Quality Center is used to execute the automation scripts to monitor the progress
of automation
3. Test data required for both manual and automation is generated using
automation scripts
Obstacles of existing automation framework and scripts
1. High maintenance required
a. Due to storing all the functions as part of functional libraries (vbs
file) in local drive
b. Changes to the script can only be done by QTP experts or
resources with scripting experience.
2. No reusability
a. No proper documentations found in scripts to understand the flow
of business process to debug
b. Most of the scripts are data dependent in the environment and for
every time to execute the script requires data refresh
3. No user friendly
a. Framework is no user friendly to use by the non technical
resources
b. Naming standards are not consistently followed across the scripts
4. Reports
a. Reports are not detailed to debug or report defects

 HP Business Process Testing (BPT)

HP Business Process Testing is available in <Customer Name> and not utilized in
any projects.

 SAP Solution Manager

SAP Solution Manager is utilized to maintain all development activities like releases
and implementation details. Business blue prints for all the projects are developed
and maintained in the Solution Manager.

 SAP Test Acceleration and Optimization

 SAP Test Acceleration and Optimization is available in <Customer Name> and not
utilized in any projects.

 Open source tools like Cucumber

 <Customer Name> evaluated the open source tools available in the market and
utilizes the best suit tools for the respective needs. One of the open source tool
Cucumber is utilized for testing the non-SAP applications. Cucumber is also not
utilized across non SAP projects. Some of the other open source tools is also
customized according to the needs and utilized in some specific areas.
3. Future SAP Landscape
 ERP (CORE) - extended to current use
 Supplier Relationship Management (SRM) - extended to current use
 Master Data Management (MDM)
 Point of Sale (ePOS)
 ERP (Retail Industry Solution)
 SAP Net Weaver Identity Management
 SAP Human Capital Management, Payroll, EHS, MSS/ESS
 SAP Risk Management and Process Control (RM/PC)
 SAP Environmental Compliance (EC)
 Project and Portfolio Management (xRPM)
 Microsoft Outlook Integration (DUET)
 SAP CRM Customer Contact Centre (CCC)
 SAP Finance Program (SFP)

3.1. Critical Areas

ERP (CORE) and Supply Relationship Management (SRM) are significantly extended use
of both applications relative to current use. Extending the current modules will requires
more regression testing to make sure the extending features of both the modules should
not impact the active business processes. New applications integrating with existing
application for the business needs will require an amount of regression testing

3.2. Recommended Automation Tools

Long name Abbrev. Tools Recommended

Search and classification TREX Quick Test Professional

Enterprise Portal EP Quick Test Professional **

Knowledge management KM Quick Test Professional **

Business Intelligence BI Quick Test Professional

Enterprise Resource Planning ERP SAP TAO

Process Integration PI Quick Test Professional

Customer Relationship Monitoring CRM Quick Test Professional **

Industry Solution – Retail IS-R SAP TAO

Supply Chain Management SCM SAP TAO

Solution Manager SolMan SAP TAO

Development infrastructure DI Quick Test Professional

Business Objects BO Quick Test Professional

DUET DUET Quick Test Professional

Governance Risk and Compliance GRC Quick Test Professional

Livelink Enterprise Archiver LEA Quick Test Professional

Old Archiving Tool iXOS Quick Test Professional

Note: ** - a Webdynpro application requires Proof of Concept to confirm the level of

automation that can be performed
4. Overall Automation Testing Approach

4.1. Process Initiation

During this phase the <Company Name> team will work with <Customer Name> team to
understand the Resource Augmentation needs, the Application Landscape, the Targeted
Operational Efficiencies and testing scope. <Company Name> and the <Customer Name>
team will revisit the engagement roadmap and will finalize the headcount and the
infrastructure needs. During this phase the <Customer Name> and <Company Name>
teams will also finalize the SLAs, the communication/ escalation process, the overall
Governance for the engagement. Necessary nominations for the Steering Committee and
Working Committee will be also achieved during this phase.
Highlights:
 Understand the size and scope of <Customer Name> automation testing services,
along with timelines and schedules
 Understand <Customer Name> testing practices, infrastructure, delivery, test
functions, and inter dependencies among processes
 Obtain insights about the current challenges and risks in the project/services
offered
 Identify the key stakeholders and formation of the Project Governance Model
 Define general management processes that would include project monitoring and
control procedures, issue/risk management, billing and invoicing procedures.
 Define the roles and responsibilities for <Customer Name> and <Company Name>
 Planning and agreement on SLA’s
 Planning of Timelines and resource requirements for subsequent phases by
<Company Name>
4.2. Tools Implementation
<Customer Name> already has implemented market best leading tools like HP QC, HP
QTP, HP BPT, SAP Solution Manager & SAP TAO tools and utilization of these tools are
very less. Some of the tools are not utilized in any of the projects due to lack of resource
and tool knowledge e.g. HP BPT, SAP TAO. <Company Name> recommendations to
achieve better ROI are as follows,
 HP Quality Center
<Company Name> understands that Quality Center usage in <Customer Name>
can be extended to next level.
 Entire testing releases of the application can be maintained in Quality center
 Integrate HP Quality Center with Solution Manager to have to overall SAP
Implementation traceability
 Blueprints from solution manager can be moved into requirements of Quality
center to have a complete traceability of the testing from requirements to
defects.
 Implement Change Impact Testing to incorporate all the change request
implemented through Solution Manager to reflect in test cases
 Develop customized test reports to have more detailed test metrics.

 HP Quick Test Professional (QTP)

<Company Name> understands that, Quick Test Professional in <Customer Name>
is not utilized across the projects and the methodology is not consistent among the
projects utilized. <Company Name>’s recommendations to <Customer Name> to
utilize Quick Test Professional more effectively and to achieve best results are as
follows,
 Implement <Company Name> recommended QTP framework to reduce the
maintenance cost drastically, increases reusability, more reliability,
Independent from environment data and user friendly
 Follow consistent naming conversions across the scripts
 Develop the generic reusable scripts and utilize the scripts across the
projects
 Incorporate Keyword driven approach to make the scripts more user friendly
 Provide adequate documentation in the test scripts for clear understanding

 HP Business Process Testing (BPT)

<Company Name> understands that HP Business Process Testing is available in
<Customer Name> and not utilized in any projects. <Company Name>
recommends,
 Utilize BPT along with SAP Test Acceleration and Optimization to optimize
the SAP test automation
 Develop QTP scripted business components to generate test data for
manual and automation testing
 Utilize BPT with QTP to develop automation Scripts for Non – SAP
applications

 SAP Solution Manager

 <Company Name> understands that Solution Manager Usage can be extended to
testing for better traceability of project progressing. <Company Name>
recommendations are as follows,
 Solution Manager can be utilized to develop business cases and to report
the incidents
 Solution Manager can be integrated with Quality Center to achieve overall
end to end tracking in one tool
 Blueprints can be transferred to the requirements of the Quality Center and
the defects logged against the requirements and status can be synchronized
with the Solution Manager
 Solution Manager CHARM can be utilized for Change control tool to manage
all the change requests

 SAP Test Acceleration and Optimization

<Company Name> understands that SAP Test Acceleration and Optimization is
available in <Customer Name> and not utilized in any projects. SAP TAO works
with the best-of-breed products, including SAP Quality Center by HP, SAP Quick
Test Professional by HP, and bidirectional integration with SAP Solution Manager.
By leveraging these scalable testing solutions, <Customer Name> can ensure the
quality and reliability of your SAP applications. <Company Name> recommends,
 Increase test coverage by defining business process scripts earlier in the
development stage
 Use SAP’s Inspect technology to generate and update components
automatically based on your standard and customized transactions
 Easily maintain scripts by editing single components that automatically apply
the change to every script in your library using the same component
 Reduce the costs and risks of releasing new SAP software and patches into
production.
 Test your end-to-end enterprise, including SAP and other integrated systems

4.3. Testing Center of Excellence

4.3.1. Evolution of testing services

Evolution of Testing Services

Decentralized Centralized Testing

Testing Organization Organization
Very High
Strategic Objective
Failure Cost

Increasing User Business Aligned

Expectations
Limited / No Testing

Perspective
Operational

Shorter IT Aligned SLA-Based

Cycle Times
Management
Project-based mgmt Testing
Center of Excellence
More Complex &
Integrated Systems Aimed at Reduced Cost Higher ROI

Reduced SDLC
International
Competition Faster Time to
Market
4.3.2. Center of Excellence

 Testing team operates across the enterprise and supports individual teams/groups on a
scheduled work queue basis - Certified / Trained Test Professionals
 Consistent methodologies, processes, tools, infrastructure and metrics across groups
 Predictable and process-driven estimation over a period of time
 Leverage resources across teams/groups and manage work centrally.
 Shared Infrastructure and tools. Efficient usage of Automation tools and test processes
to provide high quality systems
 Cost effective solutions through test framework with repeatability and reusability
 Performance metrics measured throughout
Benefits of Testing COE

Industry COE
Norm Result*

COE - Key Benefits

“IT projects delivered late”
90% 40%
Aberdeen
High ROI

Quicker time to marked

“IT projects delivered over budget”
50% 20% Reduced Failure Cost
Gartner
Optimized Resource Usage

“IT projects failing to meet objectives” Knowledge Retention

50% 10%
Gartner Enhanced Productivity

Predictability
“IT projects cancelled prior to completion”
30% 3%
Alignment to Business
Gartner

* Source: Average results from sample Mercury BTO or COE customers

5. Automation Methodology

5.1. SAP TAO Process Framework

5.1.1. Discovery
During the Discovery stage, the test team works with the client to understand the
nature of the project, and establish an approach that ensures industry best practices
are being implemented. The team works to gather requirements that form the
foundation for a detailed test plan, which outlines the projects scope. Information on
requirements, business process, interfaces, and date setup is gathered and
analyzed to ensure that nothing is overlooked during the construction phase. At the
completion of this stage, the high-level test approach will be defined, a detailed test
plan will be approved by all project stakeholders, and the test environment will be
setup including all testing software and client applications

5.1.2. Design
The Information gathered during discovery stage will be utilized to ensure that the
testing approach covers the key components to the testing engagement, and to
create the folder structures in Quality Center to ensure that application is being
validated according to the correct business requirements

5.1.3. Construction
During the Construction phase, the team creates automated using SAP TAO. These
automated scripts form an automated regression library, which is used to validate
the application during the Execution stage.

During automated script construction stage the <Company Name> test team will
use SAP TAO inspect/UI Scanner to create components against the Transaction
Code. The Inspect/UI scanner will interrogate the application and automatically
create components which will then be uploaded into Quality Center including
screenshots and parameters. The components will be ‘dragged and dropped’ into
sequences that replicate the processes identified for testing. These processes will
be created from an end user perspective, interacting with the application

Each test case will have a spreadsheet, known as the input data sheet, associated
with the test case for parameterization (input, output and calculation) and the
<Company Name> test team will set up this initial data sheet. Test data must be
loaded or populated into the testing environment before automated script creation
can begin. Once the creation of automated scripts is complete, the test engineer
modifies the scripts to make them conform to the testing goals. Script debugging is
accomplished to ensure script integrity, and to verify that the scripts are ready for
full execution. During this process, it is important that no changes to the client
application occur. Any change to the application or application architecture can
cause the scripts to fail.
5.1.4. Execution
During the Execution phase, test scripts will be executed once for completeness
with report logs available for verification purposes. Logs will include ‘PASS’, ‘FAIL’
and ‘WARNING’ messages as well as execution time, elapsed time and
screenshots where relevant. These logs can be compared by business analysts to
verify the automated tests executed as expected against the application. As the
logs have an elapsed and execution time they can be used as benchmarks against
future test execution runs. All defects will be logged into a defect tracking
application and followed through to either a successful retest or a mitigation plan for
release. Once each test case has been executed it will be stored into a relevant
test set inside Quality Center for future execution.

Any tests that fail due to technical issues or data setup will be set up again and re-
executed. <Company Name> team needs the support to get the test data &
technical issues if any. This stage may not be completed in one testing cycle.
Often, new functionality is being testing in parallel to old functionality and defect
fixes are being applied. At the culmination of this stage the test team will have
satisfied all of the exit criteria and provide either a “Go” or “No-Go” decision.

5.1.5. Analyse
During this phase, the test team will gather the results from each test run performed
on the Application under test. A summary will be provided on defects found, defects
fixed, defects open, and defects pending.

At the completion of this phase, all test results will be presented to management
and disseminated to the project stakeholders for review and further action.

5.1.6. Optimize
The final phase in this process is the Optimize stage, during this stage the test team
will complete any manual test cases that were not automated previously due to new
functionality, application changes, or timeline. In addition, the team will also review
all automated test scripts and make updates accordingly to bring the regression
library up-to-date with the latest versions of the application.
At the end of this phase, the client will have a fully functional regression library
ready to execute against the current application version. The team will also set the
library up for long-term maintenance, or support the upkeep of the library depending
on the project scope.
5.2. SAP TAO Workflow
SAP TAO is an advanced SAP testing solution for Regression, E2E & UAT Testing. It
contains Inspect, Consolidator and Import & Export tools. TAO has pre built components
like, Save Record, Launch & Login. There are more than 300 business components are
pre-built and readily available as per the SAP standard regardless of the SAP module.
TAO Inspect tool help us to create the SAP components using SAP Screen number
automatically. This is the only tool having automation creation of components. It drastically
reduced the component creation time. As per the business process, we have to create the
SAP screen components using inspect/UI scanner tool.
To build scripts by drag & drop the Business components using BPT frame work.
Consolidator works on the performance factor. As per the BPT frame work, the test scripts
execution will be run by component and component. Consolidator helps us to consolidate
N number of components to one component. So that loading and unloading of QC –
component server time will be reduced as part of execution. Test scripts, Test Results and
Defect tracking are managed in the Quality Center and traceability from the requirements
to the defects will be achieved.

5.2.1. Typical automation workflow

 Discuss the process flow with the subject matter expert

 Validate the business process test case with detailed steps
 Run the steps manually within the test application to make sure the application
generates without errors or warning messages
 In the SAP TAO client, use the Inspector to specify the transactions that you
need to create a test script. Add other transactions as needed
 Open Quality Center to view the list of your selected components
o Drag and drop the transactions in the order that they occur in the
business process
o Quality Center includes a list of common screen commands, such as
Open, Enter, and Exit. Move the screen commands using drag and drop
as needed
 Parameterize the input data in the spreadsheet or in the Quality Center
database
 On SAP TAO, consolidate the data into a single component that consists of the
transaction code and screen operations
 In the Quality Center, create a new test and drag and drop the consolidated
business component
 Execute the test script and review it for any discrepancies
 Save the components in a directory that you can easily access when you need
to update a screen or a transaction
5.3. SAP TAO Benefits & Limitations

5.3.1. Automated Business Process Testing

 Accelerated way to automate business process testing
 Predefined components significantly reduces upfront development time
 Inspect Module creates the component against the screen automatically
 Easy Drag & Drop methodology of BPT will help the script as easy as possible

5.3.2. Lower Risk

 Lower risk after SAP Solution updates due to better testing coverage
 Increased capacity to manage change

5.3.3. Lower Maintenance Costs

 Component-based Test Cases allows accelerated update of damaged test
cases
 Greatly reduces ongoing maintenance due to rescanning capabilities

5.3.4. Integration
 Tight integration between SAP Solution Manager, SAP TAO and SAP Quality
Center by HP

5.3.5. Reuse
 Eliminates the need of create new tests whenever a SAP screen or business
process changes.
 If one component changes in a group of tests, just replace that component and
then re-consolidate the tests

5.3.6. Log Report

 Detailed log is created for each execution of the script with snapshot and all the
input data

5.3.7. Easy Automation

 Business Analyst/Users can easily create the business script and maintain the
same

5.3.8. Limitations
 SAP TAO is not an independent testing (i.e. works with only on HP tools)
 Not suitable for SAP Web/Portal Testing
 Conditional test case approach is limited
5.4. Test Deliverables
 Test Strategy & plan document
 Test Estimation & schedule
 Test procedures & scenarios
 Test scripts & components delivered in Quality Center
 Test Execution reports & Defect reports
 Test Summary reports
 Test Metrics
 Test progress & status reports (Weekly)
 Test closure & handover document

5.5. Test Maintenance

Since object repositories are not created as part of component building and screens can
be re-scanned, the maintaining of TAO components is relatively easy. Test management
tool Quality Center is used to maintain the entire components repository. All components
will be managed with defined folder structure for easy use. Predefined components are
uploaded using TAO and maintained. Business analyst can build their Test scripts and
execute. Test script maintenance of the all the releases and changes in the SAP
application is made simple since no programming skill is required. More often the change
to the scripts is due to the following reasons

 New feature added or existing features change in the existing screen

 New screen introduced in the business scenario

Using SAP TAO Inspect/UI Scanner, component creation for the existing screen or new
screen is few minutes maximum. Once component is created and made available in
Quality Center, we can just replace the existing old component to new component in case
of changes to the existing screen. If it’s entirely new screen drag and drop the new
component according the flow in the test and execute.
6. Governance Model
7. Resourcing Model

 3 Tier Resourcing approach would be followed to handle the ramp up / ramp down needs of
<Customer Name> applications automation testing
o Tier I resources will be the Automation Experts/SMEs assigned to projects
o Tier II resources will be the <Company Name> Automation Experts supporting other
projects within <Customer Name>
o Tier III resources will be flexible resource team (<Company Name> bench
resources supporting <Customer Name> on need basis)
 Any resource requirement for new projects/Applications sourced from <Company Name>
will be Tier I resources. Any additional requirement will be resourced from Tier II,
depending on the work load.
 Reallocation and mobilization of resources will be done within <Customer Name> for
resource optimization, depending on work load.
 Tier III resources will be utilized if the Tier I and Tier II resources are not available.
8. Roles and Responsibilities
Role Responsibilities & Skills

Project / Test Responsibilities

Manager
 Responsible for all deliverables
 Works with client on all project related issues
 Point of contact for Client management
 Drive & facilitate business process discussions from a testing
perspective
 Subject matter expert (SME) for all testing inquires
 Manage automation team
Skills Needed
 Strong test strategy and planning skills
 Expertise in test tools
 Strong written and verbal communication skills
 Experience with Test Automation and SDLC
 People and project management skills

Automation Responsibilities
Experts / Tool  Responsible for tools implementation
Experts  Responsible for technical training and support
 Build test infrastructure
 Design and create test data for automation
 SME for all technical testing inquires
 Creates automated test components
 Executes and debugs the components
 Analyze the test results and reports the issues
Skills Needed
 Excellent technical experience on Tools
 Strong testing Methodology experience & knowledge
 Good written and verbal communication skills
 People and project management skills

Responsibilities
Functional SME  Create Functional scenarios document
 Creates functional test cases
 Analyses the test results for coverage and completeness
 Execute automation tests
 Analyse automation tests and run reports
 Report issues and defects to integrator team
Skills Needed
 SAP Functional expert
 Good Experience with HP/Mercury testing tools
 Strong written and verbal communication skills
9. Organization Structure
Appendices

Acronyms

No Acronym Expansion

1 QTP Quick Test Professional

2 QC Quality Center

3 BPT Business Process Testing

4 TAO Test Acceleration & Optimization

5 POC Proof of Concept

Attachments

No Description Type File name

References

No Reference description File name File location