Loyalty Program
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
11 Testing Schedules...................................................................................15
11.1 High-Level Testing Milestones.................................................................................................. 15
11.2 Link to Test Scheduler.............................................................................................................. 16
Page 2 of 14
13.2 Constraints............................................................................................................................... 16
13.3 Dependencies.............................................................................................................................. 16
14 Document References................................................................................17
15 Glossary of Terms.....................................................................................17
16 Document History.....................................................................................17
18 Appendix.................................................................................................. 18
Page 3 of 14
Document Purpose
The purpose of this Master Test Plan is to describe the testing efforts for the Client’s tender neutral
loyalty program also known as the Customer Centricity Initiative (CCI). The areas covered will include
scope, approach, resources, and scheduling
of testing activities across all testing phases.
1 Scope
Client 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 intranet site.
2 Testing Levels
Page 4 of 14
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.
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.
Page 5 of 14
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.
Page 6 of 14
Figure 2: Test Environment Resources
Page 9 of 14
9 Cross-Business Unit/Third Party Participation by
Application
Business Unit/ Team Name/ Contact Person, Comments
Company Name Applications Phone, E-mail
5 Testing Schedules
Page 10 of 14
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 05099 –
60007 (this is subject to change).
Note: Testing Advocates should start testing as soon as Developers have completed Unit Testing and
there are available product areas ready to test.
7.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: Client’s 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 application’s data loaded into the various testing
environments prior to testing.
7.2 Constraints
Page 11 of 14
Resources available to perform testing may impact application team’s ability to produce quality
results.
Un-configured environments may impact application team’s 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.
14 Document References
Document Path/Location
Q4M Streamline (Beta) Document Assets
for WT1
Q4M Streamline (Beta) Document Assets
for WT2
15 Glossary of Terms
MST Glossary
16 Document History
Page 12 of 14
®eviewer,
Version Name / BU (A)pprover or Disposition Date
(B)oth
18 Appendix
N/A
Page 13 of 14
8 Process Asset History
Page 14 of 14