Pottermore high level test plan Release 3.1.

18

www.javelingroup.com

Pottermore High Level Test Plan

Release 3.1.18

Version 1.0
06/02/13

Version 0.1a Page: 1 of 6

Pottermore high level test plan Release 3.1.18

Document History:

Version Date Author Description

0.1 01-02-2013 Bosco D
1.0 05-02-2013 Bosco D

Document References:

Referenc Version Author Title

e

Sign off:

Mothercare

By Javelin

Name Andrew Parkin

Title Project Manager

Date 07-02-2013

By Pottermore

Name Maciej

Title

Date

Version 0.1a Page: 2 of 6

Pottermore high level test plan Release 3.1.18

Contents:

1 Overview..................................................................................................................................... 4

2 Approach.................................................................................................................................... 4

3 Scope of testing......................................................................................................................... 4

4 Environment............................................................................................................................... 5

5 Test Deliverables........................................................................................................................ 5

6 Schedule..................................................................................................................................... 6

7 Responsibilities.......................................................................................................................... 6

Version 0.1a Page: 3 of 6

Pottermore high level test plan Release 3.1.18

1 Introduction

This is the test plan for the Pottermore Release R.1.1.18. The plan will cover the changes included
in the release and any affected areas.

2 Approach

In this release any a defect fix will be verified by running the test described either in the Jira or the
specific test cases. If the test passes the Jira is closed. Any particular functionality or module that
has been impacted by a change or fix, will be tested in regression testing by adding a detail set of
test cases or updating the existing set of the test case in the Regression Suite.
For new functionality/Feature/Improvements, new test cases and test data (if needed) will be
created according to the Functional Design Document (FDD) and Technical Design Document.
The test cases will be reviewed by the BA and Architect to verify if the coverage criteria are met.
Any defects found during this phase of Cycle 1, will be logged in the JIRA and assigned to the
developer for fixing it which will be verified and Closed or Reopened in the next Phase of testing,
namely Cycle 2. For this release we have planned 2 cycles of testing.

3 Scope of testing

1. Defect and improvements in this Release 3.1.18

Bug
[MOA-1841] - 'Cancel' link on epub3 warning overlay when adding JP book to
basket/changing edition in basket directs user to basket if Javascript not enabled
[MOA-1925] - TS2 & Prod - On the Collect Gift page (logged-in user) when the site language
is changes, site crashed showing "Sorry, we have encountered a problem" ERROR
[MOA-2137] - Help links on the CG2 are not working
[MOA-2141] - Changing the book language and site language (in the below scenario),
shows a 404 error
[MOA-2258] - GA - For the Buy as a gift overlay, everytime the add to basket button is
clicked, a GA tag is captured.
[MOA-2305] - Changing the site currency setting is changing the book edition back to the
editioncodeebooks cookie value
[MOA-2306] - Copy extends below banner for Japanese hero
[MOA-2322] - Affiliate Link - The ProgUUID is not getting captured in the mobile site when
coming via a interstitial page/link
[MOA-2327] - URL writing does not work when the book edition is changed on the Product
Details Page
[MOA-2344] - On mobile the Interstitial page is stripping out the ProgramUUID and the
AffiliateName when you access the site via an affiliate link
[MOA-2391] - AffiliateName cookie is created even when PartnerUUID is not equal to
"PHG". It should be created only when PartnerUUID=PHG
[MOA-2392] - Issue when click through to product from affilaite link using Mobile.
Improvement
[MOA-2312] - Inclusion of client facing CSS within the back office
[MOA-2315] - Changes to the PayPal UI
[MOA-2325] - Investigate why BOGOF promotions are not being displayed
[MOA-2350] - Investigate why 'Cross-Selling' not getting triggered correctly on the front end

Version 0.1a Page: 4 of 6

Pottermore high level test plan Release 3.1.18

[MOA-2374] - Change collect gift url within email to be more user friendly
[MOA-2386] - Modify the localisation template at Akamai to support pass through of affiliate
request parameters
Task
[MOA-2388] - Note: Content update summary from Content Gold 2
[MOA-2389] - Note: Content update summary from Testshop2
[MOA-2390] - Copy contents from Content Gold 1 to Testshop1

2. Reporting Extract to the data is populated correctly

3. Affiliate Network Changes End to end integration testing PHG and Reporting server
4. As a part of regression testing following areas will be covered (See attached)
5. Any content changes will be verified

4 Environment

Release 3.1.18 will be system tested on the testshop1. http://test1.pottermore.com

Reporting Server test environment

PHG staging environment

5 Environment

Release 3.1.18 will be system tested on the testshop1. http://test1.pottermore.com

Reporting Server test enviromnet

PHG Staging environment

6 Test Deliverables

Test Design
Test case for this release are written in TestRail

Test data

Defect Management
Defects identified during this testing will be reported in the JIRA

Test Report
Test Completion Report

Version 0.1a Page: 5 of 6

Pottermore high level test plan Release 3.1.18

7 Schedule

Planned sign off for the Release 3.1.18 is set for 20th Feb 2013. Below details the schedule for
the System Test

Start Date End Date

Defects testing 3-Feb-13 6-Feb-13
Regression testing 7-Feb-13 7-Feb-13
Cycle #2 testing 7-Feb-13 08-Feb-13
QA Sign of 8-Feb-13
Issue test completion report 8-Feb-13

8 Responsibilities

Name Role Responsibilities

Bosco Tester 1. Preparing Test cases & Test Data for
the release
2. Providing estimates for the test
execution
3. Executing test case
4. Identifying and logging defects in Jira
Responsible for setting up the
environment for testing with the
deliverables needed to be release for
Release 3.1.18
Paul R Lead Dev Issue RFC
Bharath / Final verification tests of any
Mai BA improvements
Andrew Internal Review and sign of test plan and
Parkin Project Manager RFC
Verification of content changes included
Nell in the release
Final acceptance and sign of the release
Pottermore prior to deployment

Version 0.1a Page: 6 of 6