New Factory Implementation Test Plan Template

Version: 2, effective date: 06-Dec-2022

Berhan Cem Ozelbicer

---

Contents

• 1 Standard description

• 2 Document objectives and benefits

  • 2.1 Objectives
    • 2.1.1 Objective Item 1: GLA
    • 2.1.2 Objective Item 2: SAP
    • 2.1.3 Objective Item 3: TPM (If TnT enabled)
    • 2.1.4 Objective Item 3: CR (If TnT enabled)

• 3 Definitions

• 4 Test items

  • 4.1 Planning stage
  • 4.2 User manual and instrucion documents
  • 4.3 Test preparations
  • 4.4 Out of scope

• 5 Test strategy

  • 5.1 Test approach
  • 5.2 Tools to be used
  • 5.3 Defect management
    • 5.3.1 Bug Trackers
    • 5.3.2 Exit Criteria
  • 5.4 Special requirements

• 6 Test deliverables

  • 6.1 Periodic reports
  • 6.2 Final report
  • 6.3 Defect report

• 7 Communication

  • 7.1 Communication methods and tools
  • 7.2 UAT team
  • 7.3 IT team

• 8 Document control

  • 8.1 Document Owner
  • 8.2 Contact person
  • 8.3 Revision History

1 Standard description

This document describes the strategy, approach, processes should be applied on “New Factory Implementation” test plan.

2 Document objectives and benefits

2.1 Objectives

Objectives are aiming to provide a checklist for each, to check if the below mentioned criteria are met and working as expected.

2.1.1 Objective Item 1: GLA

• Integration testing on GLA
  • GLA – SAP
  • GLA – TPM
  • GLA – GATE
  • GLA – WMS (If Exists)
  • GLA – MOM (If Exists)
  • GLA – CR
  • GLA – SRS(If TPD Factory)
• Functional Testing on GLA
  • GLA Smoke Tests
  • UAT Tests on GLA

2.1.2 Objective Item 2: SAP

• UAT on SAP

2.1.3 Objective Item 3: TPM (If TnT enabled)

• Integration testing on TPM
  • TPM – CR
  • TPM – GATE (If Factory does Virtual Code Pairing)
  • TPM – OMS (If Factory is under Russian Federation Regulation)
• Functional Testing on TPM
  • UAT on TPM

2.1.4 Objective Item 3: CR (If TnT enabled)

• Integration testing on TPM
  • IF TPD market CR – PR/SR
  • ELSE CR – Target Regulation
• UAT on CR

3 Definitions

Abbreviation / Term	Explanation
TPD	Tobacco Products Directive
OMS	Order Management System
TPM	Tracking Process Manager
UK	United Kingdom
EU	European Union
CR	Corporate Repository
GB	Great Britain
Tracy	MS Virtual Agents chat bot that automates T&T business processes
3PL Tracy	MS Virtual Agents chat bot similar to original Tracy, although designed for 3PL partners and will have features with limited access to CR

Please refer to IT Glossary in the IT P&P portal for further definitions.

4 Test items

4.1 Planning stage

Define the test period, resource needs and estimated due dates

4.2 User manual and instrucion documents

Documents supporting test execution will be referenced(if exists)

4.3 Test preparations

1. Creation of acceptance criteria per system

2. Creation of UAT test cases per acceptance criteria

3. Estimation of test execution

4. Assignment of testers

5. Configuration of the environment where UAT test execution will be held

6. Creation and design of test data per test case

4.4 Out of scope

Below tests are out of scope:

1. Non-Functional Testing

2. Performance Testing (depending on the need this can be discussed with local teams)

3. Security Testing

4. Accessibility Testing

5. Usability Testing

6. Functional Testing

7. E2E business Tests

8. Regression Tests

5 Test strategy

5.1 Test approach

In Test Plan below testing methods and suites will be used.

1. User Acceptance Testing – Add there reference link for both acceptance criteria and test cases

5.2 Tools to be used

List the tools will be used.

5.3 Defect management

5.3.1 Bug Trackers

Bugs found will be trace with below Tags.

• To be filled(ITSP,JIRA,WL JIRA)(QA,PPR,)

5.3.2 Exit Criteria

From Critical to Major : Only fix, retested by QA team and approved to be resolved

From Normal to Minor : Two conditions are acceptable, first is fix, retested by QA team and approved to be resolved, second is project manager approval for later fix after production deployment.

5.4 Special requirements

Below points to be considered and delivered before test case creation/execution

• Test Data
  • Market
  • Facility
  • Regulation related data
  • Request/Response samples
  • Message sample
  • Master Data
• Configuration
  • User Account for Market and Facility
  • Security Authorization and Environment Information
  • API urls
  • Certificates

6 Test deliverables

6.1 Periodic reports

Daily or Weekly test reports for internal usage

6.2 Final report

After UAT Team’s test execution, will be shared with relevant stakeholders

6.3 Defect report

Will be used to track defects found with up-to-date status and brief explanation from UAT Team

7 Communication

7.1 Communication methods and tools

• Test Alignment Meeting with IT and UAT Team via Teams
• Mail chain for seamless communication

7.2 UAT team

To be filled – UAT Director

To be filled – UAT Manager

To be filled – UAT Tester

7.3 IT team

To be filled

8 Document control

8.1 Document Owner

The owner of this document is Berhan Cem Ozelbicer.

8.2 Contact person

Questions and feedback regarding this test plan template should be submitted to Berhan Cem Ozelbicer.

8.3 Revision History

Version	Effective date	Purpose of change	Author
2	06-Dec-2022	First version	Berhan Cem Ozelbicer
1	30-Nov-2022	Initial draft	Berhan Cem Ozelbicer

ANY QUESTIONS?

ASK TEAM