Test Strategy Document

Baywatch 1.0

Document Revision History

Date

Author

Version

Comments

17\5\2012

Shahid

1.1

Initial Draft

Document Status and Approvals

Name

Role

Responsibility

Status

Date

1: Responsibility is one of: (a) Sign-off, (b) Review TBD

2: Status is one of: (a) blank, (b) Reviewed, (c) Approved, (d) Rejected

CMG: I WOULD ADD MARK AND IMRAN AS DEVLOPMENT MANAGEMENT

AND CHANGE ME TO SOLUTION OWNER FOR CLARITY

Table of Contents
Document Revision History..................................................................................................... 2
Document Status and Approvals ............................................................................................ 3
Table of Contents ..................................................................................................................... 4
1

Introduction ........................................................................................................................ 5
1.1
1.2

Overview ....................................................................................................................................... 5
Project Scope ................................................................................................................................ 5

Test Categories ................................................................................................................... 6

2.1

Not Applicable Test Categories..................................................................................................... 6

3
4

Resources ........................................................................................................................... 7
Timelines ............................................................................................................................. 8

Artifacts............................................................................................................................... 9

Entry Criteria..................................................................................................................... 10
6.1
6.2

Entrance Criteria ......................................................................................................................... 10

Exit Criteria .................................................................................................................................. 10

1 Introduction
1.1 Overview
This is the Test Strategy for Baywatch. This document shall be completed and used by the
project test team to know how testing will be managed. Based on project priorities, test effort will
be prioritized and executed as defined in the Project Plan and Requirements Specification. This
document will be refined as the project progresses. The QA Manager, Program Manager, Project
Manager etc. shall review and approve the final version of the Test Strategy document.
Product:
BayWatch is a log management and analysis product, where the user will be able to pull in
Terabytes of data, and then search in that data to help in troubleshooting.

1.2 Project Scope

The testing approach for this release shall be done as per the requirement documents, as
Baywatch product is being developed.
Testing will be designed to encompass the following.

1.3

Collection engine
Search engine
Business Intelligence engine
Indexing engine
ElasticSearch
Service registry
Configuration database
Fronting engine
Collector agents

Testing Tasks

This project includes the following testing tasks:

module test
module integration test
system test
systems integration test
acceptance test

2 Test Categories
This section determines the test categories that are required for the release, and defines the test
approaches for those test categories that are applicable. Each section also mentions the test
complete criteria.
Category

Applicable?

Compatibility Testing
Feature Testing
User Help and Documentation Testing
Usability and Accessibility Testing
Response Testing
Stability Testing
Throughput Testing
Sizing
Installation,
Globalization Testing
Security Testing
Reliability and Recovery Testing
Load Testing
Performance \ Scale Testing
Defect Verification
Recovery Testing

2.1

Not Applicable Test Categories

Clearly state the test categories that are not applicable for this release.
Category

Applicable?

Storyboard Testing
User Help and Documentation Testing
Ad-hoc Testing
Globalization Testing
Migration
Backward Compatibility Testing

3 Resources
This section points the resources.
Name

Responsibilities

Prasad Sindkar
Shahid Jambagi
Supriya Raje
Megha Varshney

4 Timelines
Task

Date

Development
Beta Release
Release

May-Aug 2012
Mid Aug 2012
Oct 2012

5 Artifacts
This section points to the test documents repository. TBD
Document reference

Date

Version

Use cases
Requirement Documents
Test Cases
Test Management

File Location

6 Entry Criteria
The deliverables from each sprint will be defined prior to the internal release drop at the end of
each sprint.

6.1

Entrance Criteria

Entrance criteria are the required conditions and standards for work product quality that must be
present or met prior to the start of a test phase.
Entrance criteria shall include following:

6.2

Review of completed test script(s) for the prior test phase.

No open critical/major defects remaining from the prior test phase.
Correct versioning of components moved into the appropriate test environment.
Testing environment is configured and ready.

Exit Criteria

Exit criteria are the required conditions and standards for work product quality that block the
promotion of incomplete or defective work products to the next test phase of the component.
Exit criteria shall include the following:

Successful execution of the test scripts(s) for the current test phase.
No open critical, major, or average severity defects unless the issue is
determined to be low impact and low risk.
Component stability in the appropriate test environment.

10