Test Plan

Automation Test Plan for <Project Name>

Confidential Page 1 of 9
Test Plan

Table of Contents

INTRODUCTION.........................................................................................................................................3
PURPOSE OF THIS DOCUMENT.........................................................................................................................3
Intended Audience..............................................................................................................................3
APPLICATION OVERVIEW.................................................................................................................................3
TEST OBJECTIVE...........................................................................................................................................3
ABBREVIATIONS.............................................................................................................................................3
SCOPE OF TESTING.......................................................................................................................................3
Inclusion..............................................................................................................................................3
Exclusions...........................................................................................................................................4
LIMITATION..................................................................................................................................................4
SCENARIOS TO BE TESTED...............................................................................................................................4
ASSUMPTIONS.........................................................................................................................................4
FEATURES TO BE TESTED......................................................................................................................4
TEST APPROACH......................................................................................................................................4
TEST PHASES..............................................................................................................................................5
TEST MANAGEMENT.......................................................................................................................................6
TEST EXECUTION CYCLE.........................................................................................................................6
CYCLE I: ....................................................................................................................................................6
Objective.............................................................................................................................................6
Entry Criteria.......................................................................................................................................6
Exit Criteria.........................................................................................................................................6
Build Frequency..................................................................................................................................6
TEST SUSPENSION AND RESUMPTION CRITERIA................................................................................7
TEST DELIVERABLES...............................................................................................................................7
TEST DOCUMENTATION...................................................................................................................................7
TEST ENVIRONMENT................................................................................................................................7
HARDWARE CONFIGURATION............................................................................................................................7
Computer Name - DSKBLRPC83.......................................................................................................7
Computer Name - DSKBLRPC70.......................................................................................................7
Computer Name - DSKBLRPC71.......................................................................................................8
Computer Name - DSKBLRPC95.......................................................................................................8
Computer Name - DSKBLRPC134.....................................................................................................8
SOFTWARE..................................................................................................................................................8
TEST DATA.................................................................................................................................................8
TEST SCHEDULE AND RESOURCES / RESPONSIBILITY......................................................................9
TEST SCRIPT PREPARATION............................................................................................................................9
APPROVALS..............................................................................................................................................9
CONTACT...................................................................................................................................................9

Confidential Page 2 of 9
Test Plan

Introduction

Purpose of This Document

This document will be reviewed and accepted by the client (technical contact) and it specifically covers
the following areas:

1. The scope of testing

2. The various phases and types of testing required for product documentation
3. Description of the test environment
4. The test data requirements
5. Resources and schedules
6. The test management and process controls
7. The test documentation to be produced for this project

Intended Audience

The test plan will be used to bring the entire team including the technical, administrative and business
team members to the same level of understanding.

This document along with any further updates will be sent to:

1. Client Technical Contacts

2. Test Automation Engineers

Application Overview

The application under test is the product document.

Test Objective

The objective of this testing project is to automate the testing of product documentation links (both in
Online document and CD document) using Mercury-HP QuickTest Professional.

Abbreviations

AUT Application Under Test

PDF Portable Document Format
CD Compact Disc
TOC Table of Content

Scope of Testing

Inclusion
I. Two product document formats
1. CD Document in PDF format

Confidential Page 3 of 9
Test Plan
2. Online Document
II. Automation of testing links up-to one level in the product document
III. Links include Bookmarks, TOC (both at the start of the document and in pages inside)

Exclusions

I. The project scope does not include testing links beyond one level

Limitation
No none limitations exist at this point of time for executing this project.

Scenarios to be tested
Business Scenario 1: Broken Links

Assumptions
Testing is done based on the premise that the title of the link clicked when found on the target page
proves that the link is accurate.

Features to be tested
1. Testing Bookmarks
2. Testing TOC at the beginning of the document
3. Testing TOC like links in pages

Test Approach
The test assets will be created based on Hybrid Framework which includes Functional Decomposition and
Data Driven approach.

Using Functional Decomposition method, the application functionality will be divided into fundamental
tasks like
 Navigation (Reusable Actions),
 Business Process (Reusable Actions),
 Subroutines (.vbs file) and
 Utilities (.vbs file)

These functional components can be reused to build several test scenarios which are called as “Main
Scripts”.

The test data is maintained in an excel sheet which is used to data drive the test.

Any changes to the data require a change in the excel sheet only and any change in the application (UI or
functional) require modifications in the corresponding Reusable Actions/Subroutines.

Confidential Page 4 of 9
Test Plan

Hybrid Framework

Functional Data Driven

Decomposition Approach

In this scenario a main script will be created for each and every page which verifies all the links in that
page. The test data for each main script will be created as an external worksheet with all the link names
and corresponding expected data.

Test Data - Worksheet

Main Script Test Result - Worksheet

Re-usable Actions
Subroutines
Utilities

Test results will be created as an external worksheet for every main script. Test result looks similar to
input data table with an additional column called “Status” which indicates “Pass/Fail” for every link in that
page.

Note: Naming convention and coding will be standardized in lines with the industry best practices.

Automating the testing of document links offers the following advantages:

 Comprehensive testing
 Avoidance of testing errors due to the stereotypical nature of testing links
 Documents can be tested overnight while the results are available the next day for meaningful
actions to be taken by the technical writers / documentation specialists
 Easy maintenance of the test automation setup with just modifications to the test data worksheet

Test Phases

Confidential Page 5 of 9
Test Plan
No Phase Outline Entry Criteria Deliverables Exit Criteria
1 Analyze Product Feasibility Report Submission of
Requirements and Documentation Feasibility Report
Feasibility Study available for Analysis
2 Prepare Phase 1 completed Automation Test Plan Acceptance of
Automation Test Document Test Automation
Plan Plan
3 Design and Phase 2 completed. Test Assets, Data Acceptance of
Develop Test Test Environment is sheets & Design Test Assets
Assets stable and ready Document
4 Execute Test Phase 3 completed Test Manual (for Defect Report
Scripts and Report execution) Defects created and sent
Defects Report for client review

Test Management

In order to avoid last minute surprises the test assets (including test scripts, test data sheets, framework
details, test automation documentation, function libraries) will be shared with the client technical contact
on a frequent basis (which at this point of time has been set to thrice in a week).

The local support will help the client technical contact with implementation support and also to
compensate for the time zone issues. The local support will be available for client visits if the situation
warrants.

The team (offshore and local support) can be made available for a conference call to ensure that all the
concerned parties are in the same page of understanding.

A weekly status report with cumulative status information about deliverables will be sent to the client
contact(s) to track the project progress.

Test Execution Cycle

There will be one cycle of test execution at the end of this project and the same will be demonstrated at
client site in the client’s test environment.

Cycle I:

Objective
To test the product links using the developed test assets at client site.

Entry Criteria
All test assets developed and approved by the client technical contact

Exit Criteria
Test execution completes successfully and the result is reported

Build Frequency
Not Applicable

Confidential Page 6 of 9
Test Plan

Test Suspension and Resumption Criteria

Suspension
If the product documentation made available for testing is unstable and cannot be opened using the PDF
reader (Acrobat Reader 7), the testing will be suspended till the AUT is made stable.

Resumption
The testing will be resumed as soon as the AUT is stable enough for testing to continue

Test Deliverables
1. Test Scripts
2. Test Automation Function Library
3. Test Data Sheet

Test Documentation
1. Feasibility Study Report
2. Test Automation Plan
3. Test Automation Design
4. User Manual

Test Environment
Workstations and one server will be allocated for this project and the same will be made available to the
team members on the first day of the project. A secured communication method will be established to
receive/send project assets.

All test assets will be version controlled using a configuration management tool (SVN in this case) and a
daily backup of the test assets will be done to prevent data loss due to disk crashes, user errors, etc…

The test assets will be checked against Acrobat Reader Version 7.x and support for Acrobat Reader 8.x
will be provided.

Hardware Configuration
The computer hardware used for testing is detailed below…

Computer Name - DSKBLRPC83

Processor: P4 2.93GHz
RAM: 512 MB
HDD: 80 GB
NIC: Realtek RTL8169/8110 Family Gigabit Ethernet NIC
Other Storage:

Computer Name - DSKBLRPC70

Processor: P4 2.93GHz
RAM: 512 MB
HDD: 80 GB

Confidential Page 7 of 9
Test Plan
NIC: Realtek RTL8169/8110 Family Gigabit Ethernet NIC
Other Storage:

Computer Name - DSKBLRPC71

Processor: P4 2.93GHz
RAM: 512 MB
HDD: 80 GB
NIC: Realtek RTL8169/8110 Family Gigabit Ethernet NIC
Other Storage:

Computer Name - DSKBLRPC95

Processor: P4 2.93GHz
RAM: 512 MB
HDD: 80 GB
NIC: Realtek RTL8169/8110 Family Gigabit Ethernet NIC
Other Storage:

Computer Name - DSKBLRPC134

Processor: P4 2.93GHz
RAM: 512 MB
HDD: 80 GB
NIC: Realtek RTL8169/8110 Family Gigabit Ethernet NIC
Other Storage:

Software
Operating System: Windows XP / Windows 2003
Database Server(s):
Other Tools: QTP 9.0, Adobe Acrobat 8 Professional.
Application under Test: CD Document

Test Data
After reviewing the test data requirements, the team found that the test data can be automatically
generated by parsing through the product document’s Bookmarks and TOC (for PDF). The team will start
by working on a manually generated test data sheet and eventually provide the support to automate
automatic generation of test data.

The test data will be in the form of a spreadsheet and the same will be used as an input by the test
scripts.

Confidential Page 8 of 9
Test Plan

Test Schedule and Resources / Responsibility

Test Script Preparation

Broken Links Testing

Week Feature Sub-Feature
Week 1 Bookmarks
Week 2 CD DOC TOC
Week 3 Links in pages
Week 1 N/A
Week 2 Online Document N/A
Week 3 N/A

Test Execution Schedule

Test Execution Schedule

Week Test Execution Cycle Duration
Week 4 Cycle I 2 Days

Approvals
All test assets and technical documents will be approved by the client technical contact during each
phase. All non-technical (administrative/business) approvals will be made by the client administrative
contact.

Contact
The point of contact for various aspects of the project is established and the same has been documented
below. Any changes to this may be communicated to our local support in-charge.

Confidential Page 9 of 9