-1Software Requirements Document

www.amazon.com

TABLE OF CONTENTS 1.Introduction 2.Scope of Testing 2.1 Test item 2.2 Features to be tested in scope 2.3 Features not to be tested in scope 2.4 Types of Testing 2.4.1 Functional Testing 3.Test plan 3.1 Risk associated with plan 3.2 Test approach 3.2.1 requrement Analysis
Batch ID : CHN11TA025

4 4 4 4 5 5 5 5 6 6 6
www.amazon.com

Page 1 of 18

-2Software Requirements Document

3.2.2 Test Plan 3.2.3 Test Design 3.2.4 Test Execution 3.2.5 Test Closure 3.3 Risks of this Approch 4. Test Schedule 5. Roles and responsibility in System Testing 6.Test environment 7.Entry Criteria for Testing 8. Exit Criteria for Testing 9.Suspension Criteria and Resumption Criteria 10.Test deliveries 11.Test reporting and tracking 12.Assumption and Dependencies 12.1 Assumptions 12.2 Dependencies 13.Risk and Mitigation 14. Version log 15 12 13 7

7 7 7

7 8 8 9 10 11

14 15

15 15 16

Batch ID : CHN11TA025

www.amazon.com

Page 2 of 18

-3Software Requirements Document

1.0 Introduction:
This test plan document is intended to provide a standard test plan for developing a website for Amazon.This document provides the detailed information about the Scope of Testing, Approach of testing, Test management, test environments, defect management, entry & exit criteria of testing with the assumptions & dependencies, risks and mitigation, issues and contingency of this project

2.0 Scope of Testing:

2.1 Test Items:
The business requirement document which is considered for the Amazon.

2.2 Features to be tested in scope:

The following modules are in scope 1. Application should be hosted by the URL: www.amazon.com 2. Registration for new users 3. Sign In for existing customer. 4. Search for products 5. Shop all departments 6. Adding to Cart

Batch ID : CHN11TA025

www.amazon.com

Page 3 of 18

-4Software Requirements Document

7. Make money 8. Accounts 9. Recent purchase history 10. Help 11. Signout

2.3 Features Not To Be Tested [Out Of Scope]

The features that are not considered in the In scope are considered to be out of scope in this document.

2.4 Types of Testing:

2.4.1 Functional Testing: The objective of this is to cover the functionalities mentioned in the requirements document. Testing of all features and functions of a system to ensure requirements and specifications are met. Smoke Testing Sanity Testing UserInterface Testing System Integration Testing

3.0 Test Plan

We perform functional testing to check if the requirements are covered Cycle-1 Cycle-2 100% of the test cases designed will be executed. Defect retesting which are raised in Cycle 1. ST Cycle Start Date Cycle 1 Cycle 2 16 Dec 2012 17 Dec 2012 End Date 16 Dec 2012 17 Dec 2012

Batch ID : CHN11TA025

www.amazon.com

Page 4 of 18

-5Software Requirements Document

3.1 Risks Associated with Plan:

The system has a limit over the number of user having access to the application. When the limit is exceeded there is a possibility that the application fails.

3.2 Test Approach:

The Testing of Amazon shopping application will contain the following 5 phased approach for testing: Requirement Analysis Test planning Test design Test Execution Test Closure Each of these five phases is elaborated in detail below

3.2.1 Requirement Analysis: The testing team would work with the Business Analysts to understand the testing requirements. The team will understand the QC items that will be tested. The project documents (Signed-off functional specification documents) will be used for the study, to accurately understand and analyze the requirements for testing. The testing team will also work on collating the testing artifacts such as requirement specifications and defect specifications. These interactions and artifacts will form the base from which the testable requirements will be collected so as to formulate a testing plan.
Batch ID : CHN11TA025 www.amazon.com

Page 5 of 18

-6Software Requirements Document

3.2.2 Test Planning: The testing team will work with test coordinators to develop a Test Plan that will be applicable across different types of testing that would be conducted under Project Name Amazon shopping project. Key activities such as Effort estimation and resource loading required for this Project are performed. Testing approach and scope for each type of testing is determined. All potential risks and mitigation plans are identified during the test planning phase. 3.2.3 Test Design: This phase will involve on construction of test cases and test data. For each functional requirement, the testing team will identify one or more test cases, based on the functional point's analysis testing for each test case, corresponding test data is created. The test cases would also be mapped to the requirements for traceability. System testing follows similar test design approach. 3.2.4 Test Execution: Once the test cases and test data are signed off, testing will be conducted in the `Development' environment and the test cases would be executed in this phase. During this phase, the testing team will execute the test cases; document the test results, track defects to logical closure. 3.2.5 Test Closure: At the end of each test execution cycle, the testing team would submit End of Cycle Test Results Report summarizing the test execution status, defect severity and test execution coverage. Upon completion of all the testing cycles, the testing team will submit a Test Closure report.

3.3 Risks of this Test Approach:

Accessibility of the application cannot be assured in all browsers, since browser compatibility is not performed.

Batch ID : CHN11TA025

www.amazon.com

Page 6 of 18

-7Software Requirements Document

4.Test Schedule:
The testing schedule and the Resourcing for System Testing are as below: Testing phases Knowledge Transfer Requirement Analysis Test Plan System Test Design Test Execution Test Closure Start Date 12/15/2012 12/15/2012 12/16/2012 12/16/2012 12/16/2012 12/17/2012 End Date 12/15/2012 12/15/2012 12/16/2012 12/16/2012 12/16/2012 12/17/2012

5.Roles and Responsibilities in System Test:

Responsibilities Resources Athreya Joshi K, Pradeep R, Prakash Acharya, Puneeth R Damle, Varun R S

Test Requirement Preparation

Test Plan Preparation

Prakash Acharya, Puneeth R Damle

Batch ID : CHN11TA025

www.amazon.com

Page 7 of 18

-8Software Requirements Document

Test Scenario/Test Cases Preparations Test Report Preparation

Athreya Joshi K, Pradeep R, Prakash Acharya, Puneeth R Damle

6.Test Environment:
Testing needs to be done IE 7/Crome direct from desktop. The following table elaborates the different tools that would be used in the course of the project at different stages of the project life cycle. Quick Test Professional would be used for Test Management.

Tools Used MS Excel 2003

Stages

Activities Involved Test Scenario

Test Design

Test Case Requirement Traceability Matrix Test Requirement Test Plan

MS Word 2003

Test Management

Batch ID : CHN11TA025

www.amazon.com

Page 8 of 18

-9Software Requirements Document

7.Entry Criteria for Testing:

The following table explains the entry criteria for Test Design phase and Test Execution sign off.

Sl. No 1

Phases Business Requirements phase

Entry Criteria KT Document Business Requirement Signoff Test Objective Test Plan Signoff

Test Plan Phase

Test Design Phase

Business Requirement Signoff Test Case signoff

Test Execution Phase

Test Data Signoff

Batch ID : CHN11TA025

www.amazon.com

Page 9 of 18

- 10 Software Requirements Document

8. Exit Criteria for Testing:

The following table explains the exit criteria for Test Design phase and Test Execution sign off

Batch ID : CHN11TA025

www.amazon.com

Page 10 of 18

- 11 Software Requirements Document

Sl. No 1

Phases Business Requirements phase

Exit Criteria Business Requirement Signoff Test Objective Test Plan Signoff

Test Plan Phase

Business Requirement Signoff Test Scenario signoff

Test Design Phase Test Case signoff Test Log Signoff

Test Execution Phase

Defect Log Signoff

Batch ID : CHN11TA025

www.amazon.com

Page 11 of 18

- 12 Software Requirements Document

9.Suspension criteria and resumption requirements:

Resumption Requirements Availability of the application Show stopper is rectified

S No 1 2

Suspension Criteria Non-availability of the application Showstopper defects (Critical), which prevent further testing along any path. Actual hardware, operating system or communication defects. Non availability of the test environment

Phase/Stage Test Execution Test Execution

Communication or hardware. O/S defects are rectified. Availability of the test environment

Test Execution Test Execution

Batch ID : CHN11TA025

www.amazon.com

Page 12 of 18

- 13 Software Requirements Document

10. Test deliverables:

The following are the deliverables from testing team in each phase of testing.

Phase

Key Focus Area

Deliverables

Requirement Analysis

Understanding of Application under test

Business Requirement Document

Batch ID : CHN11TA025

www.amazon.com

Page 13 of 18

- 14 Software Requirements Document

Phase Test Plan

Key Focus Area Test Planning 1. Creation of test scenario/cases 2. Establish traceability between the requirements and test cases to ensure complete coverage of each requirement 1. Test Execution planning 2. Execution of test cases for the application under test 3. Defect logging and tracking

Deliverables Detailed Test Plan Test cases

Test Design

Test Execution

Test Execution Log Defect logs Test Summary Reporting

Test Closure

1. Test Summary

11.Test Reporting and Tracking:

The test reports would be prepared by the testing team and would be shared with the appropriate recipients as specified below.

Report Type Defect Reports

Description The defect reports capture the defect status across modules at the end of test cycles.

Batch ID : CHN11TA025

www.amazon.com

Page 14 of 18

- 15 Software Requirements Document

Report Type

Description

Test Summary Reports

The test summary report is prepared at the end of test case execution detailing the features covered, not covered and defect

12.Assumptions and Dependencies:

12.1Assumptions:
1. The Customer should have Valid e-mail Id.. 2. The Customer details should be displayed in the corresponding Customer Account. 3.Test Environments will be available and supported for all testing time

12.2 Dependencies:
Requirement and design documents are available in a timely manner to allow progression of requirement analysis and test design to the schedule.

13.Risks and Mitigation:

Risk Application / environment outage Delay in requirement

Impact Schedule, Effort and Cost Testing timelines

Mitigation Plan Adequate support to be enabled during testing hours. Business team to clarify any doubts in requirements

Batch ID : CHN11TA025

www.amazon.com

Page 15 of 18

- 16 Software Requirements Document

Risk clarifications Too many open defects in the delivered build , so that a retest is futile

Impact

Mitigation Plan raised by testing team in time. All Showstopper defects

Testing timelines.

to be addressed immediately. The interdependencies with these modules should be

Dependency of interfaces within/outside the project

Thoroughness of testing.

clearly defined from the project perspective along with clear timelines. It would be detailed in the test plan.

14. Version Log:

Version Number V1.0 V1.1 <First version>

Changes made

<If the change details are not explicitly documented in the table below, reference should be provided here>

Batch ID : CHN11TA025

www.amazon.com

Page 16 of 18

- 17 Software Requirements Document

Page no

Changed by

Effectiv e date

Changes effected

1.2

<If the change details are not explicitly documented in the table below, reference should be provided here> Page no Changed by Effectiv e date Changes effected

Batch ID : CHN11TA025

www.amazon.com

Page 17 of 18

- 18 Software Requirements Document

Batch ID : CHN11TA025

www.amazon.com

Page 18 of 18