PROJECT PROJECT NAME

Version (Major.Minor) Date Name / Position

1.0 María Mora / QA Lead

TEST PLAN

DOCUMENT REVISION HISTORY

VERSIONING

DATE ( REVIEWED
VERSION BY MANDATORY AUTHOR MODIFICATIONS FROM PREVIUOS VERSION
REVIEWERS) 1

1.0 María Mora Document creation

1.1

LAST VERSION REVIEWERS2

ROLE NAMES TYPE

1) Business Analist
Mandatory reviewers 3
2) Delivery Lead

3) Product Owner
Lead

4) SW Security
Engineer and/or
Architect

5) SW Security
Architect

6) Solution Architect

7) DevOps Lead

1
Adding a date will imply that all mandatory reviewer reviewed and agree with the document content.
2
More reviewers can be added depending on the context of the project. Maintain the list of the last reviewers in case of
changes.
3

INTERNAL USE ONLY

02.12.2022 Page 1 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

8) Test Leads of
modules and products

8) QA manager
Optional

TABLE OF CONTENTS
DOCUMENT REVISION HISTORY.................................................................................1

1 INTRODUCTION 4
1.1 ACRONYMS ABBREVIATIONS..................................................................................4

2 OVERVIEW & TESTING SCOPE 5

2.1 SOLUTION OVERVIEW..............................................................................................5
2.2 INPUT TO TEST STRATEGY......................................................................................5
2.3 application ARCHITECTURE.......................................................................................5
MODULES and PRODUCTS........................................................................................6
2.4 REQUIREMENTS........................................................................................................7
2.5 PRODUCT RELEASE PLAN.......................................................................................7
2.6 UNIT TEST APPROACH.............................................................................................7
2.7 PRODUCTION IT ARCHITECTURE ..........................................................................8
2.8 PIA RESULTS AND ACTIONS (privacy RISK ASSESSMENT)...................................8
2.9 BIA RESULTS AND ACTIONS (SECURITY RISK ASSESSMENT)............................8
Please, refer to document attached to the above point that includes the security
requirements that the product has to fulfil.....................................................................8

3 TEST STRATEGY 8

INTERNAL USE ONLY

02.12.2022 Page 2 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

3.1 TEST PHASES and test levels..................................................................................10

3.2 REGRESSION TEST STRATEGY............................................................................10
3.3 AUTOMATION TEST STRATEGY............................................................................10
3.4 USABILITY TEST STRATEGY..................................................................................11
3.5 field TEST STRATEGY..............................................................................................11
3.6 end-to-end TEST STRATEGY...................................................................................11
3.7 DATA MIGRATION TEST STRATEGY......................................................................11
3.8 HARDWARE CERTIFICATION (SAFETY AND ENVIRONMENT).............................11
3.9 OBSOLESCENCE MANAGEMENT..........................................................................11
3.10 Subcontractors management.....................................................................................12

4 ROLES, RESPONSIBILITIES AND RESOURCES PER TEST PHASE 12

4.1 PHASE 1) FAT project...............................................................................................12
4.2 OTHER ROLES AND RESOURCES NEEDED.........................................................14

5 REPORTING AND TEST CASES 15

6 ASSUMPTIONS, RISKS, AND DEPENDENCIES 15
6.1 PROJECT RISKS RELATED TO TESTING..............................................................15
6.2 Dependencies............................................................................................................17

ANNEX – NEEDS DETAILS 17

TEST ENVIRONMENT......................................................................................................17
SIMULATORS...................................................................................................................17
TEST DATA....................................................................................................................... 17

INTERNAL USE ONLY

02.12.2022 Page 3 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

1 INTRODUCTION
The Test Plan collects all inputs needed to build a meaningful test strategy and share it with
main stakeholders.
The test strategy is described in this document and detailed in the test designed recorded in
the test management tool.
This test strategy is described at the very beginning of the project when requirements may
not be fully defined yet. Therefore, the test plan will be updated during the following phases
when needed.
This document provides, as an output, a description of the test strategy, test schedule and
milestones, resources and R&R, needs (devices, test environment, labels, data, etc).

1.1 ACRONYMS ABBREVIATIONS

Acronym Definition

FAT Factory Aceptance Test

MIT Module and Integration Tests

SAT Site Acceptance Tests

UAT User Acceptence Tests

PO Product Owner

BA Business Analyst

DL Delivery Lead

SW Team Development Teams for software

SW Software (former named software engineering)

INTERNAL USE ONLY

02.12.2022 Page 4 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

Acronym Definition
Test role performed by the QA function: purpose is Module and Integration
tests, FAT Tests, and specifications for SAT Tests.
TT interacts with Development Manager and Teams to plan the tests and
Test Team subsequently undertakes the tests sessions that are planned during the
product or project development.
TT is consulted by HOP and/or PO during Design Reviews.

QC Quality Control

SOP Standard Operating Procedures

US User Story

WA Web application

2 OVERVIEW & TESTING SCOPE

2.1 SOLUTION OVERVIEW

2.2 INPUT TO TEST STRATEGY

Test strategy is built based on the following inputs:

- Solution architecture by Solution Architect who shall inform promptly the Test Lead in
case of change, for relevant changes, test plan may need to be updated.
- Requirements by the Product Owners.
- IT architecture for production by DevOps.
- BIA results by the Head of Project.
- PIA results by Head of Project.

INTERNAL USE ONLY

02.12.2022 Page 5 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

2.3 APPLICATION ARCHITECTURE

MODULES and PRODUCTS

Below the list of components:

Components

INTERNAL USE ONLY

02.12.2022 Page 6 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

The components that will be assigned to the bugs created on Jira will be:

Components in Jira

2.4 REQUIREMENTS
List of requirements can be checked in Jira.

Requirements will be linked to the tests through Zephyr and Jira in order to assure a
coverage of the 100%, otherwise, impact analysis will have to be carried out.

Test lead will extract the traceability matrix from Zephyr and will attach it to the QA section.

At this moment of the project, there are not non functional requirements defined.

2.5 PRODUCT RELEASE PLAN

The roadmap of the project is defined in Jira.

Below the product release plan:

INTERNAL USE ONLY

02.12.2022 Page 7 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

The scope of the future releases can be checked in Jira to a high level:

2.6 PRODUCTION IT ARCHITECTURE 4

Below the IT architecture:

Architecture review details in the wiki.

2.7 PIA RESULTS AND ACTIONS (PRIVACY RISK

ASSESSMENT)

The attached document includes the security requirements identified.

2.8 BIA RESULTS AND ACTIONS (SECURITY RISK

ASSESSMENT)
Please, refer to document attached to the above point that includes the security requirements
that the product has to fulfil.

4
IT architecture expected for production will be the base for pre-prod environment definition. For
internal product must be defined in product strategy.

INTERNAL USE ONLY

02.12.2022 Page 8 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

3 TEST STRATEGY

Testing Phases and environments

Manual tests

API tests

Performance tests

Security tests

Exploratory tests

Execution details

End-to-end

Compatibility Testing - Devices

INTERNAL USE ONLY

02.12.2022 Page 9 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

Risks

Risks have been identified together with the PO and the delivery lead and have been raised
on Jira identifiying the impact and the severity.

Risks will be documented in the test reports.

Testing management

The test management will be done with Zephyr; E2E tests are already stored in the tool.

Test cases will be added to the test repository ordered by year and organized by
requirement.

3.1 TEST PHASES AND TEST LEVELS

Below the key test levels of the project test strategy:

3.2 REGRESSION TEST STRATEGY

INTERNAL USE ONLY

02.12.2022 Page 10 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

3.3 AUTOMATION TEST STRATEGY

Automation team will be contacted in order to prepare the automation test strategy for this
project.

3.4 USABILITY TEST STRATEGY

3.5 FIELD TEST STRATEGY

Field test strategy point will be raised with the SQC community in order to decide if it can be
tackled in SDAS project.

3.6 END-TO-END TEST STRATEGY

INTERNAL USE ONLY

02.12.2022 Page 11 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

3.7 DATA MIGRATION TEST STRATEGY

3.8 HARDWARE CERTIFICATION (SAFETY AND

ENVIRONMENT)

3.9 OBSOLESCENCE MANAGEMENT

Obsolescence management will be tackled based on release management.

3.10 SUBCONTRACTORS MANAGEMENT

At this moment of the project, there are not subcontractors. In case the project will have them
in the future, any subcontractors of testing will be manage by the test lead.

INTERNAL USE ONLY

02.12.2022 Page 12 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

4 ROLES, RESPONSIBILITIES AND

RESOURCES PER TEST PHASE

4.1 PHASE 1) FAT PROJECT

Below the details about how the FAT of the project will be organized and coordinated:

Products list FAT product QA Test environment Test data, equipment,

Lead Name need samples, devices,
simulators specific
needs

Details.

INTERNAL USE ONLY

02.12.2022 Page 13 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

4.2 OTHER ROLES AND RESOURCES NEEDED

Find below the stakehdolder list to this document, those stakedholder SHALL review this
document and inform the Test Lead of any change that SHALL trigger a new version of this
document.

Task Name Applicable Yes/No

Set up and maintain IT test DevOps /

Environment as defined in
this document

Test data creation and DevOps/

maintenance as defined in
this document

Deploy the solution to

validate the deployment
instruction and run sanity
check as first FAT check

Performance test strategy Yes

Inform test lead about Solution Architect Yes

architecture change, phase
Business Analyst /
scope modification

Security Bugs Opening Software Security Engineer Yes

Security Test Strategy Security Architect Pending

Mandatory licence Product Owner / Yes

attribution

Release plan Product Owner/ Yes

Delivery Lead

FMEA updated (HW) Product Owner / No

INTERNAL USE ONLY

02.12.2022 Page 14 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

Obsolescence Requirement Product Owner / Yes

5 REPORTING AND TEST CASES

Test
repository
on Zephyr

QA section

Reports
available
on QA
section

Bugs
Dashboard

Jira project

Releases
on Jira

INTERNAL USE ONLY

02.12.2022 Page 15 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

6 ASSUMPTIONS, RISKS, AND

DEPENDENCIES

6.1 PROJECT RISKS RELATED TO TESTING

Risks Responsible Person Mitigation

Security engineer

Devops engineer

PO / Developers

Business Analist

INTERNAL USE ONLY

02.12.2022 Page 16 of 17
 PROJECT PROJECT NAME
Version (Major.Minor) Date Name / Position
1.0 María Mora / QA Lead

6.2 DEPENDENCIES

ANNEX – NEEDS DETAILS

TEST ENVIRONMENT

The environments of project are detailed in Confluence:

SIMULATORS

TEST DATA

*** End of document ***

INTERNAL USE ONLY

02.12.2022 Page 17 of 17