Customer Centricity Initiative

Macys Loyalty Program

Master Test Plan

v. 1.01

December 2009

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Contents
Document Purpose....................................................................................................................................4 1 Scope.....................................................................................................................................................4 1.1 Requirements to Be Tested..............................................................................................................4 1.2 Requirements Not to Be Tested........................................................................................................5 2 Testing Levels.......................................................................................................................................5 2.1 Unit Testing......................................................................................................................................5 2.2 System Testing................................................................................................................................5 2.3 Acceptance Testing .........................................................................................................................5 2.4 Regression Testing .........................................................................................................................5 3 Approach ..............................................................................................................................................5 3.1 Guidelines for Iterative Testing........................................................................................................6 3.2 Guidelines for Test Factors..............................................................................................................6 3.3 Application Interfaces.........................................................................................................................6 5Environments and Data...........................................................................................................................7 5.1 Inventory of Environment Resources...............................................................................................9 Test Data................................................................................................................................................13 6Enterprise Test Tools............................................................................................................................13 7 Test Deliverables Project Teams....................................................................................................14 8 Staffing, Responsibilities, and Training ...........................................................................................14 9 Cross-Business Unit/Third Party Participation by Application.....................................................15 10Test Communication Plan..................................................................................................................16 10.1 Meeting Schedules and Purpose....................................................................................................16 10.2 Metrics and Measurements..........................................................................................................16 10.3 Link to Bug Tracker .....................................................................................................................16 11Testing Schedules...............................................................................................................................16 11.1High-Level Testing Milestones........................................................................................................16 11.2Link to Test Scheduler.....................................................................................................................17 12Risks and Contingencies....................................................................................................................17 13Assumptions, Constraints, and Dependencies................................................................................17
http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential Page 2 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

13.1Assumptions....................................................................................................................................17 13.2Constraints......................................................................................................................................17 13.3 Dependencies..............................................................................................................................17 14 Document References......................................................................................................................18 15 Glossary of Terms...........................................................................................................................18

16 Document History.............................................................................................................................18 17 Reviewers and Approvers................................................................................................................18 18 Appendix...........................................................................................................................................19 19Process Asset History ........................................................................................................................20

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 3 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Document Purpose
The purpose of this Master Test Plan is to describe the testing efforts for the Macys tender neutral loyalty program also known as the Customer Centricity Initiative (CCI) and the Macys Loyalty Program. The areas covered will include scope, approach, resources, and scheduling of testing activities across all testing phases.

1 Scope
Macys is creating a tender neutral loyalty program, which will allow customers the opportunity to enroll in the program via in-store, online, and through customer service. The scope of this Program Level Master Test Plan is to outline testing information at a high-level that supports the implementation of the tender neutral loyalty program. The implementation of this program will require both Mainframe and Windows application-testing teams to ensure quality testing is performed during the system development lifecycle of this project. Testing Advocates on projects classified as a Work Type 1 (WT1) will include their testing activities in the Project SDLC Document and will provide a link to the Loyalty Program Master Test Plan. Testing Advocates on projects classified as a Work Type 2 (WT2) will be required to create an application detail test plan with reference to the Loyalty Program Master Test Plan. Testing Advocates should use the document asset templates from the new Q4M Streamline (Beta) intranet site. The link to this site is http://mymacys/applications/Q4M/Q4MBETA/default.aspx

1.1 Requirements to Be Tested

The requirements to be tested will fall into three categories, Business Requirements, System Requirements, and Technical Requirements. Business Requirements: The Business Requirements to be tested are those presented in the Macys Loyalty Program Overview Document. The link to this document is
http://secure.macyspartners.com/sites/dunnhumby/Docs/MSTLoyalty/Program Documents/Loyalty Overview Document.doc. Application teams will provide traceability evidence from their System Requirements to

their applicable Business Requirements. System Requirements: The System Requirements to be tested are those presented in each applications WT1 SDLC Document or Requirements Definition Document (RDD). These documents can be found on the MST Loyalty Team Site by selecting the desired application tab. The link to the MST Loyalty Team Site is http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx. Testing Advocates from each application team will perform testing using System Requirements outlined in either the WT1 SDLC Document or the RDD and any other supported documentation relevant to their testing efforts. Technical Requirements: The Technical Requirements to be tested are those presented in the Technical Definition Document (TDD). Testing Advocates should contact their Project Manager or Development Lead for their projects location of the TDD. Application teams will provide traceability evidence from their Technical Requirements to their System Requirements, to their applicable Business Requirements.

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 4 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Program Change Requests (PCRs): For WT1 projects, Testing Advocates should list all approved PCRs relating to their projects in the Projects SDLC Document. For WT2 projects, Testing Advocates should list all approved PCRs relating to their projects in their application detail test plan. A list of all PCRs are located http://secure.macyspartners.com/sites/dunnhumby/Program Documents/Forms/AllItems.aspx?
RootFolder=%2fsites%2fdunnhumby%2fProgram%20Documents%2fChange %20Management&FolderCTID=&View=%7bAFD18C61%2dEDDF%2d46F4%2d92D6%2d61EFD4F4661B%7d

1.2 Requirements Not to Be Tested

MST will not be testing any requirements relating to the testing activities of third-party vendor Acxiom or out of scope to the tender neutral loyalty program for Pilot.

2 Testing Levels
All application groups participating in the tender neutral program should incorporate the levels/phases of testing as needed for the project type.

2.1 Unit Testing

Unit testing is performed during coding and integration testing and is done during detailed design. Since these are developer activities, they would be included in the unit test plan (Use the Unit Test Workbook Template on Q4M Streamline (Beta). Testing Advocates should follow-up with the Development Lead for verification.

2.2 System Testing

System testing can include many types or phases/levels of testing (Smoke Test, Functional/Component Testing, Regression Testing, Integration/Cross-FOB Testing, Beta Testing, etc.). Often these are performed concurrently and in various combinations. Testing Advocates should define and describe the test types that will be performed for their application testing effort.

2.3 Acceptance Testing

Acceptance testing will be performed as End-to-End Test of all functionality across all platforms and applications. A Program Level Acceptance Test Plan will be created prior to the End-to-End Test. Testing Advocates can also create a separate Acceptance Test Plan for their projects, if applicable.

2.4 Regression Testing

Regressing testing should be performed by every application Testing Advocate to ensure the quality of existing code has not been changed as new code is introduced.

3 Approach
The scope of the testing effort for the Loyalty Program will be based on both Waterfall and Iterative Testing Methodologies. Waterfall Testing is an approach where you complete a number of phases in a strictly ordered sequence: requirements analysis, design, implementation/integration, and then testing. Iterative Testing is an approach to testing where an evaluation or assessment of quality is conducted continuously, on smaller, more manageable units of work.

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 5 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

The Loyalty System testing activity will focus on the FIT Model (Focused Iterative Testing). Focused Iterative Testing means testing iteratively against a focused area of a software product/system. A focused area usually refers to a group of specific features in the software product (for example, Offer/Reward). All other systems can elect to perform Iterative Testing or continue with their current Waterfall method of testing until End-to-End Testing is ready to be performed. There will be a separate End-to-End Acceptance Test Plan where all application-test teams will participate together at one time.

3.1 Guidelines for Iterative Testing

Start with Iteration 1, Build 1. o There may be several iterations within a Build. o For iterations performed, the next iteration should build on the previous iteration. Record and keep track of the number of Iterations performed. Record and keep track of the number of Builds completed. For each Build, request Dev. Lead produces Release Notes so that you know whats in each Build. This will be beneficial as the product continues to develop and will provide traceability. Each Build produced should build on the work of the previous Build.

3.2 Guidelines for Test Factors

There are many applications interfacing for the Loyalty Program. In order for a successful testing effort, you may use the following test factors where applicable. Test factors enable the test process to be logically constructed. Correctness Assurance that the data entered, processed, and outputted by the application system is accurate and complete. File Integrity Assurance that the data entered into the application system will be returned unaltered. Audit Trail The capability to substantiate the processing that has occurred. Continuity of processing The ability to sustain processing in the event problems occur. Reliability Assurance that the application will perform its intended function with the required precision over an extended period of time. Ease of Use The extent of effort required learning, operating, preparing input for, and interpreting output from the system. Maintainability The effort required to locate and fix an error in the application system or missing requirement or misinterpretation of a requirement. Portability The effort required to transfer data from one application to another. Web Service Communication Assurance that messaging service are communicating between applications without error.

3.3 Application Interfaces

Integrated Application Context Diagram link
http://secure.macyspartners.com/sites/dunnhumby/Docs/MSTLoyalty/Program%20Documents/Visio-Customer, %20Loyalty%20and%20Offers%20Integrated%20System%20Context%20Diagram%20v16.pdf

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 6 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

5 Environments and Data

The following environment information is at a high-level and continues to be a work in progress and subject to change. If changes are made, this document will be updated to reflect those changes. Note: Figures 1, 2, and Table 1 were retrieved from the Loyalty Program Level Environment Plan.

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 7 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Figure 1: Environment Readiness Timeline

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 8 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Figure 2: Test Environment Resources

5.1 Inventory of Environment Resources

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 9 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

This section lists the resources that are used by each system in each environment. The reference environment names are those used by the new Loyalty system and their mappings to other nomenclatures are indicated. New resources are emphasized. Table 1: Environment Resource Inventory Development Loyalty esul1084 Redhat Linux 5.3 server (TIBCO Syndera Dashboard, TIBCO Business Works, TIBCO Enterprise Messaging System, TIBCO Business Events, Coherence DataGrid) Sun M5000 Solaris server board, shared with other nonproduction environments (Oracle 11g (schemaName)) Test esul1085 Redhat Linux 5.3 server (TIBCO Syndera Dashboard, TIBCO Business Works, TIBCO Enterprise Messaging System, TIBCO Business Events, Coherence DataGrid) Sun M5000 Solaris server board, shared with other nonproduction environments (Oracle 11g (schemaName)) Pre-Production esul1086, esul1087, esul1088, esul1089 Redhat Linux 5.3 servers (TIBCO Syndera Dashboard, TIBCO Business Works, TIBCO Enterprise Messaging System, TIBCO Business Events, Coherence DataGrid, RT View) Sun M5000 Solaris server board, shared with other nonproduction environments (Oracle 11g (schemaName)) CSS Load Balancer Customer TC1CICD mainframe DEV region (CICS, DB2) TFLCICX mainframe DEV region (CICS, XML/TRANSL, DB2) FZ000XSWEB90 Windows 2003 DEV server (ASP, VB6) TC1CICB mainframe BIZ region (CICS, DB2) TFLCICB mainframe BIZ region (CICS, XML/TRANSL, DB2) FS000XVXML92 Windows 2003 BIZ server (ASP, VB6) TC1CICQ mainframe REL region (CICS, DB2) Stress Initial Stress environment will be Production. Subsequently, a duplicate of the Production environment will be setup in Lorain and will double as a disaster recovery and stress test environment. Production esu1l162, esu1l163, esu1l164, esu1l165, esu1l166 Redhat Linux 5.3 servers (TIBCO Syndera Dashboard, TIBCO Business Works, TIBCO Enterprise Messaging System, TIBCO Business Events, Coherence DataGrid) esu1l167 Redhat Linux 5.3 server (RT View) 2 x Sun M5000 Solaris server boards (Oracle 11g (schemaName)) CSS Load Balancer [regionName] mainframe PRD region (CICS, DB2) [regionName] mainframe PRD region (CICS, XML/TRANSL, DB2) [serverName(s)] Windows 2003 PRD server(s) (ASP, VB6)

FedFIL (including XML MidTier)

TFLCICQ mainframe REL region (CICS, XML/TRANSL, DB2) FZ000XSWEB91 Windows 2003 REL server (ASP, VB6)

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 10 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Development SPOS Windows XP Register (.NET) [serverName] Linux server (C scripts) MCOM ibm44p15 AIX server (Websphere Application Server) ibm52p20 AIX server (DB2 (mci252)) RPS TDNCICD mainframe DEV region (CICS, Datacom)

Test Windows XP Register (.NET) [serverName] Linux server (C scripts) ibm64p1 AIX server (Websphere Application Server) ibm64p2 AIX server (DB2 (muq8)) TDNCICB mainframe BIZ region (CICS, Datacom)

Pre-Production Windows XP Register (.NET) [serverName] Linux server (C scripts)

Stress Windows XP Register (.NET) [serverName] Linux server (C scripts)

Production Windows XP Register (.NET) [serverName] Linux server (C scripts)

ibm44p20 AIX server (Websphere Application Server) ibm44p9 AIX server (DB2 (mut1))

[serverName(s)] AIX server (Websphere Application Server) [serverName] AIX server (DB2 (instanceName))

TDNCICQ mainframe REL region (CICS, Datacom)

[regionName] mainframe STR region (CICS, Datacom)

[regionName] mainframe PRD region (CICS, Datacom) FACICR0 mainframe PRD region (CICS, Datacom, DB2) PACICR0 failover region.

FCS

TFACICR mainframe FIX region (CICS, Datacom)

ICM

WindowsXP desktop (.NET, C++, SQL Server, Development configuration files) TDNCICD mainframe DEV region (CICS, Datacom, DB2)

WindowsXP desktop (.NET, C++, SQL Server, Test configuration files) TDNCICB mainframe BIZ region (CICS, Datacom, DB2)

WindowsXP desktop (.NET, C++, SQL Server, PreProduction configuration files)

WindowsXP desktop (.NET, C++, SQL Server, Stress configuration files)

WindowsXP desktop (.NET, C+ +, SQL Server, Production configuration files)

RDS

TDNCICQ mainframe REL region (CICS, Datacom, DB2)

[regionName] mainframe PRD region (CICS, Datacom, DB2)

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 11 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Development SOCR esu2v111 Redhat Linux 4.1.2-14 server (Websphere Application Server 6.1) mt001xsbti90 Windows 2003 server (btwebsvcdev, ASP.NET (VB)) TDNCICD mainframe DEV region (CICS, Datacom, DB2) Offer Mgmt CIM DCR

Test esu2v115 Redhat Linux 4.1.2-14 server (Websphere Application Server 6.1) mt001xsbti90 Windows 2003 server (btwebsvcbiz, ASP.NET (VB)) TDNCICB mainframe BIZ region (CICS, Datacom, DB2)

Pre-Production

Stress

Production esu1l138 & esu1l139 AIX 5.3 servers (Websphere Application Server 6.1), load-balanced by esu1l137 ma001xsbti01 & ma001xsbti02 Windows 2003 server(s) (ASP.NET (VB)) [regionName] mainframe PRD region (CICS, Datacom, DB2)

esu2v136 Redhat Linux 4.1.2-14 server (Websphere Application Server 6.1) mt001xsbti90 Windows 2003 server (btwebsvcrel, ASP.NET (VB)) TDNCICQ mainframe REL region (CICS, Datacom, DB2)

Dunnhumby server of some kind Acxiom FTP server [serverName] Windows 2003 server (TBL, C#.NET) [serverName] Linux [N.n?] server (Oracle N.n) [serverName] Windows 2003 server (TBL, C#.NET) [serverName] Linux [N.n?] server (Oracle N.n) MA000XSDCR01, MA000XSDCR02, MA000XSDCR03 & MA000XSDCR04 Windows 2003 servers (TBL, C#.NET) esu1l075, esu1l076 & esu1l077 Linux [N.n?] server (Oracle N.n)

Credit

Multiple mainframe TEST regions (CICS, Datacom) several since Loyalty has different expectations by market per Jan Altfield. TM3CICC Cleveland market TPCCICC Sacramento market TDYCICC NY East TI0CICC outside of test market store but zip code falls within target zip code area TFVCICC Cobrands in Sacremento/NY East markets TF2CICC Cobrandds in Cleveland market TLGCICC NAPS

Multiple mainframe PRD regions (CICS, Datacom) [regionNames]

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 12 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Development StrongMai l / OES ? WindowsXP desktop (Websphere Application Server)

Test

Pre-Production

Stress

Production [serverName] [OS?] mail server [serverName] AIX server (Websphere Application Server, MQ Series) [serverName] AIX server (Oracle 10g)

[serverName] [OS?] mail server OES2: [serverName] AIX server (Websphere Application Server, MQ Series) [serverName] AIX server (Oracle 10g)

Support Structures CAPS ibm64p4 & ibm64p3 AIX servers (DB2 (dev), DataStage) ibm64p5 & ibm64p6 AIX servers (DB2 (qa), DataStage) ibm66p1 & ibm67p1 AIX servers (DB2, DataStage) fsgncr10 AIX server (Teradata N.n (EDW_PROD / RRPMST & RRPMVP))

DDW

fsgncr10 AIX server (Teradata N.n (EDW_PROD / EWPTMP))

GL PCS

TH3CICF mainframe test region (CICS, Datacom?) TDNCICD mainframe DEV region (CICS, Datacom, DB2) TDNCICB mainframe BIZ region (CICS, Datacom, DB2) TDNCICQ mainframe REL region (CICS, Datacom, DB2) [regionName] mainframe STR region (CICS, Datacom, DB2) [regionName] mainframe PRD region (CICS, Datacom, DB2)

STK SAL

Test Data
The test data required to support the testing scenarios listed in the Approach section of this document will be outlined in the individual applications SDLC or RDD documents. Contact the Quality Control Organization (QCO) at mailto:MST QCO Support@macys.com if help is needed to load application data.

6 Enterprise Test Tools

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential Page 13 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Update the following chart to reflect the testing tools used on a project. Tool Testing Scheduler (TSC) Bug Tracker Purpose Testing resource scheduling Defect management Link to the Tool
http://tsc/ http://bugtracker/bug/ (uf0a3b55rmt1z5550f3ktw45)/default. aspx http://fs000xscar91:9197/qadirector/d efault.aspx

QA Director & Changepoint

Testing script depository and execution tool. Defect management.

7 Test Deliverables Project Teams

The Testing Advocates are responsible for the following work products. Deliverable Work Product Test Plan Purpose Describes the scope, approach, resources, features to be tested, testing tasks, and risk contingency planning. For WT1 projects: Enter the link to Loyalty Master Test in Section 6.1 of the SDLC Document. For WT2 projects: Test Cases
See the Q4M Streamline (Beta) intranet site, Q4M (Beta) Assets link for the Test Plan Template http://mymacys/applications/Q4M/Q4MBETA/default.aspx

Specifies test inputs, execution conditions, test outputs, expected results, actual results, and test pass/fail results. For WT1 projects: Enter the link to your test cases Section 6.4 of the SDLC Document. For WT2 projects:
See the Q4M Streamline (Beta) intranet site, Q4M (Beta) Assets link for the Test Case Template http://mymacys/applications/Q4M/Q4MBETA/default.aspx

Test Summary Report

Test Summary Report summarizes the application testing results for this project. For WT1 projects: Enter the summary information in Section 6.3 of the SDLC Document. For WT2 projects:
See the Q4M Streamline (Beta) intranet site, Q4M (Beta) Assets link for the Test Summary Report http://mymacys/applications/Q4M/Q4MBETA/default.aspx

Test Scheduler (TSC)

This is a testing resource scheduling application. Testing Advocates are responsible for creating their own application TSC entries for this project. http://tsc/

8 Staffing, Responsibilities, and Training

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential Page 14 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Team Member
Russ Summers

Role
Enterprise Program Manager

Responsibilities
Project management for the Loyalty Program Project management for the Loyalty Program PPQA Analyst for the Loyalty Program Coordinating the testing efforts for the Loyalty Program Coordinating development and test environments for the Loyalty Program Support and guide the application teams with environment and data configurations.

Contact
Russ.Summers@macys.com (678) 474-2085 Diane.Nachazel@macys.com (678) 474-2136 Violetta.Felgin@macys.com (678) 474-3236 Ginene.VanLierop@macys.com (678) 474-2256 Gareth.Davies@macys.com (678) 474-3899 Charles.Clyburn@macys.com (Test Management) (678) 474-3024 Cynthia.Jyang@macys.com (Data Loads) (678) 474-3232 Tatyana.basin@macys.com (Test Environments) (678) 474-3134

Diane Nachazel

Sr. Enterprise Program Manger

Violetta Felgin

PPQA Analyst

Ginene VanLierop

Program Testing Advocate

Gareth Davies

Program Operations Advocate

QCO Team

Test Environments and Data Set-up

Enterprise Tools Team

Bug Tracker, Test Scheduler Tools

Resolve tool problems and answer questions about Test Scheduler and Bug Tracker

mailto:MST DevTools@macys.com

9 Cross-Business Unit/Third Party Participation by Application

Business Unit/ Company Name
Marketing

Team Name/ Applications

CUS

Contact Person, Phone, E-mail

Ginene VanLierop Meenakshi Tarun

Comments

Marketing POS - Lorain Logistics Direct to Consumer Stores Stores Stores POS

Loyalty System SPOS RDS D2C-FedFil CVT FCS RPS Credit

Charanya Govindarajan Matthew Johnson MST/Lorain Tina Arrowood James Wiggins Marc Bergroschtje Rosa Summers Cecilia Unger (Bonnie) Andrea Perine

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 15 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Business Unit/ Company Name

Direct to Consumer

Team Name/ Applications

MCOM

Contact Person, Phone, E-mail

Roland Demeter

Comments

10 Test Communication Plan

10.1 Meeting Schedules and Purpose
The Loyalty Program Testing Advocates began meeting on Monday, November 11, 2009 and will continue to meet on Mondays from 3:15 p.m. to 4:15 p.m. to discuss all related items surrounding the testing efforts for this project. During End-to-End Testing the application test teams will meet daily.

10.2 Metrics and Measurements

Defect Tracking Metrics: Reports from Bug Tracker will be produced weekly and distributed to each applications Project Manager, Development Lead, and Management. The Testing Advocate for RDS will produce and submit a weekly defect summary report from QA Director to the Program Level Testing Advocate, who will incorporate with the Bug Tracker reports and distribute to all applicable parties.

10.3 Link to Bug Tracker

All test teams will use Bug Tracker for defect management with the exception of RDS, which is using QA Director. There is one project level entry in Bug Tracker for the Loyalty Program. The Bug Tracker link for this project is http://bugtracker/bug/(144skzvyk04ori45isa5rrju)/default.aspx

11 Testing Schedules
The testing schedule for the Loyalty Program will be based on the overall project schedule and the details for the project schedule are still a work in progress. The current project schedule section for the Loyalty Pilot Development & System Test Phase currently starts in the project plan on ID 599 607 (this is subject to change). The Loyalty Program Project Schedule link is
http://secure.macyspartners.com/sites/dunnhumby/Docs/MSTLoyalty/Program Documents/Loyalty Program Schedule (PDF).pdf

Note: Testing Advocates should start testing as soon as Developers have completed Unit Testing and there are available product areas ready to test.

11.1

High-Level Testing Milestones

Testing Range Date 01/18/2010 02/18/2010 02/18/2010 04/19/2010 02/18/2010 04/19/2010 02/18/2010 04/19/2010 02/18/2010 04/19/2010
Page 16 of 20

Task/Milestone Pre-System Testing System Testing Integration Testing Regression Testing Acceptance Testing (E2E) Development & QA
http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Task/Milestone UAT (Business Partners)

Testing Range Date 04/01/2010 04/19/2010

11.2

Link to Test Scheduler

Each Testing Advocate will setup a separate Test Scheduler entry for their application. The link to Test Scheduler is http://tsc/

12 Risks and Contingencies

Risks and contingencies are being tracked at the project level. If a project risk affects the overall testing, notify Ginene VanLierop to escalate the risk.

13 Assumptions, Constraints, and Dependencies

13.1 Assumptions
13.1.1 A Testing Advocate, Project Manager, Tech Lead, Development Lead, and Operations Advocate shall be assigned for each application area. 13.1.2 All projects shall record defects in Bug Tracker, Project Name: Macys Loyalty Program, Release Pilot with the exception of RDS, which will be using Changepoint. 13.1.3 Development Leads and Operations Advocates shall contact the QCO with any data or environment issues. 13.1.4 Testing Advocates shall verify their teams have access to all testing environments. Access shall be verified prior to the Ready To Test (RTT) checkpoint. 13.1.5 Testing environments shall be ready for each testing phase/level. 13.1.6 All application testing teams shall have their applications data loaded into the various testing environments prior to testing.

13.2 Constraints
Resources available to perform testing may impact application teams ability to produce quality results. Un-configured environments may impact application teams development and testing activity.

13.3 Dependencies
The Loyalty Program application teams will identify testing dependencies. Examples of testing dependencies are: 1. A requirement for another application team to provide (load or create) test data. 2. A requirement for another application to be functional in the test environment during testing. 3. A requirement for another team to process or validate output from testing.

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 17 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

14 Document References
Document Q4M Streamline (Beta) Document Assets for WT1 Q4M Streamline (Beta) Document Assets for WT2 Path/Location
http://mymacys/applications/Q4M/Q4MBETA/Q4M BETA Release/Forms/Work Type 1.aspx http://mymacys/applications/Q4M/Q4MBETA/Q4M BETA Release/Forms/Work Type 2.aspx

15

Glossary of Terms

MST Glossary http://intrafsg/glossary/FSG_Glossary.htm

16 Document History
Version .01 1.01 Date 12/11/09 1/12/10 Change Initial document creation Updated environment section. Updated link to the latest system context diagram. Author Ginene VanLierop Ginene VanLierop

17 Reviewers and Approvers

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 18 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

Version
1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0

Name / BU
Marc Bergroschtje / Stores Testing Advocate Tina Arrowood / Logistics Testing Advocate Matthew Johnson / POS Lorain Testing Advocate James Wiggins / D2C Testing Advocate Rosa Summers / Stores Testing Advocate Cecilia Ungers (Bonnie) / Stores Testing Advocate Andrea Perine / POS Credit Testing Advocate Tammerra Tillman (Tami) Product Manager Roland Demeter

eviewer, (A)pprover or (B)oth

R R R R R R R R R

Disposition Date 12/17/09 12/16/09 12/15/09 12/17/09 12/17/09 12/17/09 12/17/09 12/17/09 12/17/09

18 Appendix
N/A

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 19 of 20

Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011

Macys Loyalty Program Master Test Plan v. 1.01

19 Process Asset History

Release
Rel 3.3, Template v3.1

Date
3/24/09

Change
Added Process Asset History section to the template; FMT #9229 - Removed any guidance that allowed deletion of sections of the template (Introductory guidance, section 2 guidance and section 4 guidance were changed) Changed CARS to Quality Manger (QM) in guidance (3 places)

Author
K.Hadfield

Rel 3.3.2 Template v3.2

8/25/09

K.Hadfield

http://secure.macyspartners.com/sites/dunnhumby/docs/mstloyalty/default.aspx Test Plan Template v 3.2 (do not delete) Company Confidential

Page 20 of 20