Documentos de Académico
Documentos de Profesional
Documentos de Cultura
December 2009
Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011
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
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
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
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
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
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.
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
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.
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
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
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
Page 9 of 20
Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011
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)
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
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)
ibm44p20 AIX server (Websphere Application Server) ibm44p9 AIX server (DB2 (mut1))
[serverName(s)] AIX server (Websphere Application Server) [serverName] AIX server (DB2 (instanceName))
[regionName] mainframe PRD region (CICS, Datacom) FACICR0 mainframe PRD region (CICS, Datacom, DB2) PACICR0 failover region.
FCS
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)
RDS
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
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
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
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
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.
Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011
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
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 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
This is a testing resource scheduling application. Testing Advocates are responsible for creating their own application TSC entries for this project. http://tsc/
Save Date: 11/14/2011 Last Saved By: j.manikanda Print Date: 11/14/2011
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
Violetta Felgin
PPQA Analyst
Ginene VanLierop
Gareth Davies
QCO Team
Resolve tool problems and answer questions about Test Scheduler and Bug Tracker
mailto:MST DevTools@macys.com
Comments
Marketing POS - Lorain Logistics Direct to Consumer Stores Stores Stores POS
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
Comments
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
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
11.2
Each Testing Advocate will setup a separate Test Scheduler entry for their application. The link to Test Scheduler is http://tsc/
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
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
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
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
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
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
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
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