1.

Introduction

Amazon.com wants to enhance their online site with Gift & Wish Lists, Gift Cards, Sell on
Amazon, Careers and Wish List functionality.

This document details the System Test Strategy and plan for the added enhancements.

The System test will be performed at BetaSoft Systems Inc, in Fremont, CA.

The scope of System Testing for Amazon.com enhancements is to ensure that the various units
behave in a very consistent and in a manner as required. Amazon.com will conduct 2 rounds of
System Testing with the round 2 meeting the exit criteria. At the end of round 1 – a review of the
ST results will be conducted and the corrections will be done to those task units where errors
have been reported. All test cases will be tested again in round 2 with more emphasis on round 1
failed cases. The software has to meet the exit criteria set in round 2. If the exit criterion is not
met in ST round 2 another round will be conducted until the exit criteria i.e. a rating of 4 or more
is met.

1.1 Purpose
The purpose of this document is to outline the Scope, Coverage, Procedures, Schedule,
Transactions checklist & System test conditions for Amazon.com new enhancements.

1.2 This test plan is written from a business/functional perspective—without consideration

for how the application/system is technically implemented. The primary focus of the testing
described in this plan, therefore, is black-box testing. White-box testing coverage is provided by
the Development Team via Developer Unit Testing (DUT) and Developer Integration Testing
(DIT).

In Scope Out of Scope

Types of Testing

The following types of testing are in scope:
 System Integration Testing (SIT)
• Functional / End-to-End
Testing
• Cross Operating System and
Browser Testing
• Usability Testing
• Critical Path Testing
• Spot Check Testing
The following types of testing are out of scope
in relation to this test plan:
 Developer Testing
• Developer Unit Testing (DUT)
• Developer Integration Testing
(DIT)
 System Testing
• Performance Testing
• Stress/Load Testing
 • Regression Testing  User Acceptance Testing (UAT)
• Key Stakeholder Testing
• Subject Matter Expert Testing

Operating System and Browser Coverage

Testing will be performed on the following Testing will NOT be performed on the
operating systems and Internet browsers: following operating systems and Internet
browsers:
 Operating Systems
• Windows 2000  Operating Systems
• Windows XP • Windows 95
• Windows Vista • Windows 98
• Windows 7 • Windows ME
• Windows NT
 Browsers • Mac OS 8, 9, X
• Internet Explorer: 6.0  Browsers
• Mozilla Firefox • Netscape: 4.7, 4.75, 4.76, 4.77, 6.1
• Google Chrome • America Online: 7.0
• Safari

Genie CIA 1.0 Phase-II Components

The following components to be tested for The following components will not be tested:
Amazon Gifts & Wish Lists: Wedding Registry
Browse dialogue box: Baby Registry
 Validate the Your Wish List
Gift Cards
 Validate Universal Gift List
Browse dialogue box:
 By Price
 By relationship
 For Kids & Teens
 By Personality
  By Occasion

Stop Payment Cash Management WF:

 Validate the
eligible/applicable accounts for Cash
Management Workflow:
Bank Accounts
 Savings
(ACH Stop Payment Only)
Checking
NonInt
In
HouseInt
MM
Checking
In House
NonInt
Checking
Internet
Checking
 Verify
ineligible account types as
applicable
 Brokerage Accounts
 Individual
 Joint
 Custodial
 CMA
 Trust, Estate or Conservatorship
 Sole Proprietorship
 Corporate Partnership
 Investment Club
 IRA
 Verify ineligible account types
as applicable
ET Complete Accounts
Individual
Joint
Custodial
 Verify ineligible account types
as applicable

 Validate if the single

 check has already been cashed. If the
check has already been cashed, verify
the error message on the screen.
 Verify that the Stop
Payment Workflow will generate a
Stop Payment Tickler in Pulse.
 Verify and Validate the
additional dropdown field / values on
Stop payment WF UI, if Single Check
is selected:
 Issued By Dropdown field
E*Trade
Customer
 Verify that
workflows submitted before 7:00pm
ET will be processed the same business
day
 Verify that
Workflow will be processed by Genie
WF Automation for Bank and CMA
accounts. If the workflow becomes
ineligible for automation Operations –
Arlington will process the request.

Genie Main Enhancements:

 Validate the new
elements(enhancements) available on
following Genie Main screens/pages,
their default/possible values, formats
available, and also perform both
positive and negative field tests:
Customer Summary Page
 Tier – Gold and Platinum tier
will be displayed in bold font
and text color green, all other
tiers will remain black. Left
Justify.
 RM – If the customer has an
RM display it next to tier. Right
Justify.
 Segment – Former Power ET
and Priority ET headers will be
replaced with the Segment
header. Possible values are
1. PET Day Trader
 2. PET Highly Active
Trader
3. PET Active Trader
4. Priority E*Trade
5. MainStreet
6. Int’l PET
7. Int’l Priority E*Trade
8. Int’l MainStreet
9. Not Found
 Total Value - Total
value of customers accounts.
Right Justify.
 Accounts - Number of
bank Accounts, number of
brokerage accounts. Right
Justify
Account Registration Section
 Display Portrait after
Account Registration title
separated by a hyphen
 Primary address
populated from the mailing
address found in UCDB

Complaint Review Workflow:

 iS
hare link to Complaint Review
Workflow Testplan is:
https://ishare.corp.etradegrp.com/viewc
at.php?catid=17828&view=

End-To-End Testing:
 End-to-End system testing will be
done against all the affected
Genie/Serena Bank and
Brokerage pages.
 End-to-End testing will be
done/performed for the
Automated Bank/Brokerage-Non-
ECA/ET Complete Workflows.

All other areas of Genie Brokerage and

Bank will be regressed as a part of Genie
 CIA 1.0 Phase – II testing.

Deliverables

(Descriptions of each deliverable are found at qa.etrade.com)

In addition to this plan, the following The following deliverables are not required:
deliverables are required:
 User Acceptance Test Plan
 Product Test Cases Suite  Performance, Load, and Stress Test Plan
 Defect Tracking System Entries
 Testing Status Reports
 Go/No-Go Justification

Test Data
QA will need following information in order to verify Gift & Wish Lists components:
• Your Wish List
 Should have Email address
 Amazon accounts

Universal Gift List

 You can add items to Universal Wish List from any website like Google chrome, Firefox,
safari, internet explorer, ipad, etc
 Include Amazon "Add to Wish List" buttons on your website

1.3 Audience
The targeted audiences are:

• Amazon SQA (Software Quality Assurance Group)

• Amazon Development Team.
• Amazon Test Execution Team.
• Amazon Third SPC/PM
• Amazon Third QA Team.
1.4 Test Strategy
Two rounds of System test are to be conducted. Both the rounds of testing shall follow the
System test plan. The changes in the test execution and plan felt during the first round of testing
shall be incorporated in the second round. The testing shall be carried out from Betasoft location
and shall test the core functionality of the application concentrating on the changes made. The
defects found in the first round shall be addressed before the second round is carried out. The
second round of System test would also execute the regression of code impacted by the change
defects fixed in the first round as well as the full end-to-tend cycle.

1.5 Assumptions
• All the hardware and connectivity used shall try to simulate the final state environment for
the application.
• The ST shall mainly concentrate on the core functionality of the ‘Scheduled and Repeating
Transfers’ enhancement and tests on individual module level items like the User Interface
shall be covered in the UTPs that are scheduled for each of the units.
• All the Unit Test defects are fixed.

Test Environment

1.6 Hardware Environment

• Onsite Environment “Amazon4” to be used for testing.

1.7 Software Environment

• Application Server:
IBM Websphere Application Server Version 4.0.6

• Database Server:
IBM DB2 8.0 running on AIX

• Browser:
Internet Explorer 6.0 on Windows XP

The testing environment will be isolated from the development environment. There will be
dedicated workstations for the transactions input and verification. A separate physical area will
be set up, which will include the workstations and other peripheral devices that will be required
during the testing process.

1.8 Resource Requirements

The existing development team will be split into two groups. The Execution team will be
responsible for activities related to setting up of the test bed, test environment & execution of
System test plan. The correction team will be responsible for fixing errors reported by the
execution team. In both of the first & second rounds of system test, there will be an entire end-to-
end testing of Schedule and Repeating Transfers in Internet Banking application.

1.1 Build Schedule and Release Management

To expedite defect resolution and verification, the following build schedule will be utilized for
Amazon 4.

SIT Build Schedule

Task # Task Responsible Party

The SIT environment will be built 3

1 times a week: Monday, Wednesday, System Engineering
and Friday.

All code must be checked in by

2 midnight the previous day before Development Team
each build.
Defect records must be updated by
midnight the previous day before Technical Lead
each build. Required defect updates
3 include: (1) state transitions (i.e. new Development Team
to open, open to fixed, and/or fixed to
QA Test Team
verified), (2) Dev fix comments and
(3) QA verification comments.
Test and development teams are to be
4 notified upon the successful QA Department
completion of each build.

SIT environment availability and

5 connectivity is to be verified upon the QA Department
completion of each build.