GlobalTrak Test Plan

GlobalTrak

Test Plan

Purpose: Through testing achieve a product that is sound in security and functionality for both the
supply chain personal and the end user

Revision History
Date Version Author Description
October 15th, 2018 1.0 Daniel Bedell Test Plan

Test Plan GlobalTrak, version 1.0 Page 1 of 22

Test Plan GlobalTrak

Table of Contents

1. Overview ....................................................................................................... 4
1.1. Purpose ...................................................................................................................... 4
1.2. Scope .......................................................................................................................... 4

2. Testing Summary ......................................................................................... 5

2.1. Scope of Testing ....................................................................................................... 5

3. Analysis of Scope and Test Focus Areas................................................. 6

3.1. Release Content........................................................................................................ 6
3.2. Regression Testing ................................................................................................... 6
3.3. Platform Testing ........................................................................................................ 6

4. Progression Test Objectives ...................................................................... 7

5. Progression Test Objectives ...................................................................... 8

6. Other Testing ................................................................................................ 9

6.1. Security ....................................................................................................................... 9
6.2. Stress & Volume Testing (S&V).............................................................................. 9
6.3. Connectivity Testing (CT) ........................................................................................ 9
6.4. Disaster Recovery/Back Up..................................................................................... 9
6.5. Unit Testing .............................................................................................................. 10
6.6. Integration Testing .................................................................................................. 10

7. Test Strategy .............................................................................................. 11

7.1. Test level responsibility .......................................................................................... 11
7.2. Test Type & Approach............................................................................................ 11
7.3. Build strategy ........................................................................................................... 11
7.4. Test Execution Schedule ....................................................................................... 12
7.5. Facility, data, and resource provision plan .......................................................... 12
7.6. Testing Tools ........................................................................................................... 13
7.7. Testing Handover Procedure ................................................................................ 13
7.8. Testing Metrics ........................................................................................................ 13

8. Test Environment Plan .............................................................................. 14

8.1. Test Environment Man ........................................................................................... 14
8.2. Test Environment Details ....................................................................................... 14
8.3. Establishing Environment ...................................................................................... 15
8.4. Environment Control ............................................................................................... 15
8.5. Environment Roles and Responsibilities ............................................................. 15

9. Assumptions and Dependencies ............................................................. 16

9.1. Assumptions ............................................................................................................ 16

Test Plan GlobalTrak, version 1.0

Page 2 of 22
Test Plan GlobalTrak

9.2. Dependencies .......................................................................................................... 16

10. Entry and Exit Criteria ............................................................................. 17

11. Administrative Plan ................................................................................. 19

11.1. Approvals ............................................................................................................... 19
11.2. Test Milestones and Schedule............................................................................ 19
11.3. Training................................................................................................................... 19
11.4. Defect Management ............................................................................................. 19

12. Definitions ................................................................................................. 20

13. References ................................................................................................ 21

14. Points of Contact ..................................................................................... 22

Test Plan GlobalTrak, version 1.0

Page 3 of 22
GlobalTrak Test Plan

1. Overview

1.1. Purpose

This test plan describes the testing approach and overall framework of testing in
regarding the GlobalTrak system. The document will define:
 The test scope focus areas and objectives; Test the ability to track, integrate database
into the new work environment.
 The test responsibilities; Test the different roles of the application.; Admin/Warehouse
specialist, and End User.
 The test strategy for the levels and types of test for this release; Test the
environment for any loopholes that might cause information to be accessed by outside
parties.
 The entry and exit criteria; Entry criteria is defined as the ability to track shipments and
send notifications to End User and Admin services. Exit Criteria will be a seamless
integration of the final products.
 The basis of the test estimates; The testing shall be done within the span of 8-Months
in order to assure the requirements set forth by the End User.
 Any risks, issues, assumptions and test dependencies; The Risks are that testing
won’t be done in time.
 The test schedule and major milestones; As stated above 8-months for the start date
we must deliver a usable and secure program for the End User.
 The test deliverables; Prior to delivering the program we shall test the end product to
insure no holes in the security framework, and that seamless integration can occur.

1.2. Scope
This document details the testing that will be performed by the project team for the GlobalTrak
project. It defines the overall testing requirements and provides an integrated view of the project
test activities. Its purpose is to document:
 What will be tested; Testing of the initial design will be done, followed by testing of the
integration between the different components of the hardware and software. Testing will
be performed on the final product before being released.
 How testing will be performed; Testing will be done by Design ReviewTest
PlanningTest DesigningTest EnvironmentTest ExecutionTest Reporting.
 What resources are needed, and when; We will need to send the development team to
the End Users location to establish the key components needed in the final product.
During the end test phase, the End User shall be brought to our location to run a series
of final tests to make sure the product, meets their requirements.

Test Plan GlobalTrak, version 1.0 Page 4 of 22

GlobalTrak Test Plan

2. Testing Summary

2.1. Scope of Testing

2.1.1. In scope
The scope of the test is to verify the functionality of GlobalTrak works occurring to the
specifications required by both parties.

The product testing will verify that all aspects of the software are complete and fully
vetted prior to launch. These aspects will be refined and dialled in during the test phase
in which members of the End User team, and the development team when they test their
final phases.
 A production-ready software;
 A stable test environment with minimal flaws.
 Reassurance that functionality of the program is sound before delivery to End
User.

2.1.2. Out of scope

The during out testing the following issues we will plan on not including in the final product due to
increased cost of the final product.

 Route tracking while on Military Installations.

 Location of Shipment pinging by End User
 Ability for End User to interrogate clients inventory database.
 Speed tracking of shipment (MPH due to possible Union rules)
 2-way communication with delivery hub and driver.

Test Plan GlobalTrak, version 1.0 Page 5 of 22

Test Plan GlobalTrak

3. Analysis of Scope and Test Focus Areas

3.1. Release Content

Upon release the software will contact the following for the clients;
 Inventory integration
 Tracking of shipments by shipper
 Real time notifications to both clients (End User and Admin/Shipper)
 Email notifications to all parties regarding status of shipments (delayed, on time,
arrival, shipped)
 Tracking Overlay with GoogleMaps

3.2. Regression Testing

For GlobalTrak to be able to work seamlessly we will need to perform Regression Testing on the
legacy system of inventory and shipping logistics. The inventory will need to be absorbed by the
new system, a new system of categorizing inventory and labelling and sorting will need to be
defined at a later state. This will most likely utilize QR code scanners integrated with a newer
style database. For the mean time the older stored inventory database will be ported line by line
to the incoming inventory server. The testing will take place during the Test plan to ensure that
legacy inventory will be ported and will work fine with the newer serves.

3.3. Platform Testing

Detail of the platform that will be used for testing:
 GlobalTRAK App
o Client
 Must have a Microsoft Windows 10 based terminal/laptop or tablet,
supported by the lastest security suit.
o Server
 Microsoft Server 2008 or better
 4GB free memory
 60GB disk space

 GlobalTRAK User Interface

o Java Runtime Environment v5.0 or better
o 60GB disk space
o 4GB free memory

Test Plan GlobalTrak, version 1.0

Page 6 of 22
GlobalTrak Test Plan

4. Progression Test Objectives

Ref Function Test Objective Evaluation Criteria X-Ref P

Function to be tested

Test Integration of Ability to search database for Ability to search and keep track of inventory stock. P
inventory inventory
database
Test Shipment Alerts generated for shipped, en- Alerts must be triggered by pre-determined situations. See Info on P
Tracking route, delivered, delayed. Geo-location
Test Email Alerts Email generated to all parties on Emails sent to End User, and Admin regarding shipment See Shipment P
situations designed above in station. Tracking
regards to shipment status.
Test QR Code Ability to track and generate QR Unique QR code generated per specific piece of Non-
Generator for codes for inventory database inventory, with the ability to scan with handheld device Priority
inventory

Test Plan GlobalTrak, version 1.0 Page 7 of 22

Test Plan GlobalTrak

5. Progression Test Objectives

Ref Function Test Objective Evaluation Criteria X-Ref P

Regression testing

Test Geolocation of Demonstration of pinging location Location shall be overlayed with GoogleMaps and will See Testing for P
shipments of shipments by all users be able to be pinged within the area of 30 ft. Anything tracking
more will prove a negative test shipments
Test Locations around Tracking will shut down within 2 Location tracking shall stop within 2 miles of destination See above P
secure facilities miles of destination. if located on secure facility.
will be shut down
Test Delayed When arrival time frame is Email notifications, Test /Automated Call (if enabled) P
Shipment status extended due to issues, will be sent to all parties. Push Notifications through the
alert notifications will be sent. App
Test Application Test the functionality of app for App integration is one of the key components of this P
integration end user and admin program, to use and track shipments with ease.

Test Plan GlobalTrak, version 1.0

Page 8 of 22
GlobalTrak Test Plan

6. Other Testing

6.1. Security
Security will be dealt in the following ways to help mitigate any information leaking to parties no
associated with orders.
 Security will be part of the design process. (Security will not be an afterthought)
 OWASP Top 10 will be referred to while designing the program.
 Functionality and performance will not override security.
 Pen-testing will take place during all steps of the design and implementation process.
 Security Audits will take place during and after the development phases of this
application.
 Logging of flaws and bugs will be done during testing, planning, designing, and
implementation phases.
 Encryption of AES-256 will be utilized.
 All application stakeholders should agree on the date and time of the vulnerability
assessment. This is necessary to ensure that the test has minimal impact on any of the
stakeholders.

6.2. Stress & Volume Testing (S&V)

To perform an adequate stress test, we must increase to volume of traffic to both the system,
application and tracking. Utilizing multiple applications, terminals and computers we will simulate
an increased flow to both the web portal and inventory terminal. We will be monitoring the system
for issues regarding the following;
 Bottlenecking
 Long loading times
 Response time
 Stability
In order to test perform the following test we most take to following steps; 1) Set the Test
environment, 2) Agree on acceptable performance, 3) Design a test, 4) Prepare the test
environment, 5) Test the design, 6) Monitor tests, 7) Analyse results.

6.3. Connectivity Testing (CT)

Detail connectivity testing to be performed for the project, how it will be performed, who will
perform it and expected outcomes.

6.4. Disaster Recovery/Back Up

Disaster Recovery will revolve around total back up of data on a separate server which is stored
in a secure off-site facility protected from the elements. The backup server location as well as the
main hub will be both fed from 2 different utility power feeds. If power is interrupted via utility
power on the primary circuit, an automatic throw over will throw the facilities power to the
energized source. On top of the automatic throw over the utility power, the site will be equipped
with UPS (Uninterruptable Power Supply) to keep the servers energized until emergency
generation or utility power can be re-routed. The lead site manager will be tasked with any
upgrades need and will be the primary contact between our site and the power company. Every
year we will maintenance on the switchgear and will have to switch dates in order to keep the
system running.

Test Plan GlobalTrak, version 1.0 Page 9 of 22

Test Plan GlobalTrak

6.5. Unit Testing

Unit Testing will be done on the following equipment.
 GlobalTRAK App
o Client
 Must have a Microsoft Windows 10 based terminal/laptop or tablet,
supported by the lastest security suit.
o Server
 Microsoft Server 2008 or better
 4GB free memory
 60GB disk space

 GlobalTRAK User Interface

o Java Runtime Environment v5.0 or better
o 60GB disk space
4GB free memory
 2 Apple Ipads (12.0 IOS)
 2 Microsoft Surface Pro 4 (Microsoft Windows 10

6.6. Integration Testing

The Integration Testing will be performed as follows;

The goals of the testing are as followed;

 Unit test: test logic in classes by programmers to show code level correctness.
They should be fast and not depend on other parts system.
 Functional acceptance test: test scenario's with limited data set done by the
testers to show every scenario will work as designed.
 User acceptance test: test scenario's on production by the End User to make them
formally accept the application
 Integration test: Test communication paths between different parts of the module
done by the test department or by developers to show that all modules work
correctly together.

Test Plan GlobalTrak, version 1.0

Page 10 of 22
Test Plan GlobalTrak

7. Test Strategy

7.1. Test level responsibility

Detail the testing levels expected to be applied and who has primary (P) and secondary (S)
responsibility for performing this testing (example below).

Test Level External Proj Team Business

Party

Unit Testing P
Integration Testing P
Security Testing P
Connectivity Testing P
User Acceptance Testing S S P
Production Verification Testing S P
GeoLocation Testing S P

7.2. Test Type & Approach

Test Type Objectives

Progression Requirements The objectives are to verify that the application:

 Meets the defined requirements;
 Performs and functions accurately;
 Correctly handles error conditions;
 Interfaces function correctly;
 Data load is successful.
Functional testing will occur in an iterative and controlled manner,
ensuring the solution matches the defined requirements.
Regression testing The objectives are to verify the following:
 Geolocation of shipments
 Locations around secure facilities will be shut down
 Delayed Shipment status alert
 Application integration

7.3. Build strategy

Strategy to build this program will be done on a twofold approach. Brainstorming will be handled
by all parties involved, an interview of the End User has been done prior. The programmers will
work in teams to build the requirements set forth by the End User. During key phases of the build,
the teams will complete pen-testing on different aspects of the build.

Test Plan GlobalTrak, version 1.0

Page 11 of 22
Test Plan GlobalTrak

7.4. Test Execution Schedule

Provide a test schedule for the project team in written format (e.g. using MS Word, MS Project or
MS Excel) Detail each type of testing, the function and the priority.
Quarter and Year Test Schedule
Q-4 2018 Begin Testing of Code and integration
Q-1 2019 Testing Complete
Q-2 2019 Start of Integration testing
Q-3 2019 User Training Starts / Pen-testing
Q-4 2019 End integration testing
Q-1 2020 Release

7.5. Facility, data, and resource provision plan

7.5.1. Test environment
Tests will be done both at the End User site, for acceptance training to prevent interruption to
their business process. The Development team will be testing via virtual machines within our
office location.

7.5.2. Access to other applications

While this part of the program isn’t a primary necessary to the completion of the software, our
teams will need access to GoogleMaps HTML. QR Code generation programs

7.5.3. Testing Requirements

Detail the requirements for testing to commence.
Each person involved in testing will need the following access:
 A web browser with access to the intranet
 Access to the Inventory Database, and relevant database SQL tool;
 Access to Business Objects;
 Access to Microsoft Excel to raise defects;
 QR Scanners

7.5.4. Data Requirements

See above in Section 6.5

7.5.5. Resources & Skills

Define the types of resources required during the testing window. For example:
 A resource with SQL skills;
 A resource with .NET skills to resolve any defects;
 A resource with internet technologies understanding.

Test Plan GlobalTrak, version 1.0

Page 12 of 22
Test Plan GlobalTrak

7.6. Testing Tools

Detail the tools to be used for testing.
For example:
The following tools will be used for testing:

Process Tool

Test case creation Microsoft Word

Test case tracking Microsoft Excel
Test case execution Manual
Test case management Microsoft Excel
Defect management Microsoft Excel
Pentest environment Kali Linux on VirtualBox

7.7. Testing Handover Procedure

The handover procedure for transfer of program to users will set when the project is close to
being finished. Handover of the program will entail proper documentation, training material, and
active support for a specific time frame. The support of our production team will be utilized for any
issues that occurred by the end user. On-Call support will be offered for afterhours support for the
client. Prior to full integration of the systems we will ensure a bug free environment for a time
frame of 1 month.

7.8. Testing Metrics

Detail the metrics to capture, the reasons for capture, and how you will capture them.
To move to the transition or Handover. We would like to the an 100% on no flaws during testing.
We will use this equation to determine to move forward. % = (# of tests run/Total # of tests
written) *

Test Plan GlobalTrak, version 1.0

Page 13 of 22
Test Plan GlobalTrak

8. Test Environment Plan

8.1. Test Environment Man

GPS DATA

API
GATEWAY TRACKING
SERVICES TRACKING DATABASE

ADMIN/COMPANY API

INVENTORY
DATABASE INVENTORY DATABASE
API
HTTP

WEB ACCESS NOTIFICATION

DATABASE
NOTIFICATION DATABASE

API

END USER

8.2. Test Environment Details

8.2.1. Testers
Define the number of testers who will be involved in testing and their:
 System testing will be a team of 4, with 1 project manager
 Hardware requirements See above in Sect

8.2.2. Hardware and Firmware

 GlobalTRAK App
o Client
 Must have a Microsoft Windows 10 based terminal/laptop or tablet,
supported by the lastest security suit.
o Server
 Microsoft Server 2008 or better
 4GB free memory
 60GB disk space

 GlobalTRAK User Interface

o Java Runtime Environment v5.0 or better
o 60GB disk space
4GB free memory
 2 Apple Ipads (12.0 IOS)
 2 Microsoft Surface Pro 4 (Microsoft Windows 10

Test Plan GlobalTrak, version 1.0

Page 14 of 22
Test Plan GlobalTrak

8.2.3. Software
Microsoft Windows Server 2008, Windows 10, VirtualBox, QRCode GEN, GoogleMaps, Java,
Windows Office Suite, Outlook, Kali Linux..

8.2.4. Interfaces
Interface will be established with; GPS data from Satellites, Scanners to read QR Code, Ipads,
and Microsoft Surface 4.

8.2.5. Other Materials

None.

8.3. Establishing Environment

Define the plan for establishing the testing environment, and responsibilities. This should include
acquisition of each element, setup, installation and testing the environment.

Task Requirements Responsibility Start Date End Date

Notification Send when Prg Team Jan-2019
criteria met
System Integration Migration of all Dev Team Jan-2020
parts

8.4. Environment Control

Define any control measures that will be placed on the environment. This might include:
 Unknown at this time

8.5. Environment Roles and Responsibilities

Define the roles and responsibilities of persons who will be responsible for, or interface with the
environment

Role Staff Member Responsibilities

Release Manager Chris Angel Responsible for overall
establishment, coordination and
support of the test environment
Test Manager Tom Sismore Responsible for advising release
manager of environment
requirements for planning,
establishment and ongoing
Project Manager Dan Bedell Escalation point for environment
issues.

Test Plan GlobalTrak, version 1.0

Page 15 of 22
Test Plan GlobalTrak

9. Assumptions and Dependencies

9.1. Assumptions
Detail any assumptions made for testing.
The during the making of this system the Project management will learn the system so well that
any acceptance testing and training of the End Users can be handled by them.

 The object code will be fully unit and integration tested and made available on the Test
environment by the date(s) given in the schedule for executing the test scripts and sign-
off has been forwarded to the Test Team Leader.
 The application environment and content components will have successfully completed
the SILC Application Environment and Content review process as outlined in the
Acceptance Process section of the Project Plan and the appropriate sign-offs have been
forwarded to the Test Team Leader.
 Budget has been set to $1510,000 no including labour, if project goes over by 1 month
money shall be reduced from end check.

9.2. Dependencies
Detail testing dependencies
 Prior to all tests the manager or team lead of the engineering team, will make
sure the test environment is properly set up.
 All system engineers must properly track, bugs on the bug report documents.

Test Plan GlobalTrak, version 1.0

Page 16 of 22
Test Plan GlobalTrak

10. Entry and Exit Criteria

Detail the entry and exit criteria that are used to determine when a phase of testing (or level of
testing)

Entry
 Unit Testing:
 Planning phase is complete.
 System design, tech. design and other documents are properly
reviewed/approved.
 Business and functional requirements are defined and approved.
 Testable codes are available.
 Availability of test environment.
 Integration Testing:
 Phase testing is complete.
 Priority bugs found has been fixed and closed.
 Integration plan and test environment to carry out integration testing is ready.
 Each module has gone through unit testing before the integration process.
 System Testing:
 Completing the integration testing process.
 Priority bugs found have been fixed and closed.
 Testing environment is available.
 Test cases are available to execute.
 Acceptance Testing:
 Completion of system testing phase.
 Priority bugs found have been fixed and closed.
 Functional/Business requirement has been met.
 Acceptance testing environment is abailable.
 Test cases are available.
Exit
 Unit Testing:
 Successful execution of the unit tests.
 All the identified bugs have been fixed and closed.
 Project code completed.
 Integration Testing:
 Successful execution of the integration tests.
 Satisfactory execution of stress & load tests.
 Priority bugs are fixed and closed.
 System testing
 Successful execution of the system tests.
 All specified business and functional requirements has been met.
 Priority bugs are fixed and closed.
 System’s compatibility with supported hardware and software.
 Acceptance testing

Test Plan GlobalTrak, version 1.0

Page 17 of 22
Test Plan GlobalTrak

 Successful execution of the user acceptance tests.

 Approval from management to stop the testing.
 All requirements have been fulfilled.
 No critical defects left.
 Signing off acceptance testing.

Test Plan GlobalTrak, version 1.0

Page 18 of 22
Test Plan GlobalTrak

11. Administrative Plan

11.1. Approvals

Task Responsible Person Escalation/ Approver

Systems Integration Signoff Department Head

User Acceptance Testing Signoff End User Admin
Production Verification Testing Signoff Department Head

11.2. Test Milestones and Schedule

Milestone Planned End Actual End Resource

Date Date

Inventory Merger Dec - 2018

Shipping Notification Feb-2019

Shipping Status Jul -2019
GoogleMaps integration Aug-2019
App integration Dec-2019
QR Code Gen/Scan Dec or Jan -
2020

11.3. Training
The following training requirements have been identified to ensure testing can commence:

Training Requirement Staff Date

QR Code Scanner Testing Delivery personnel TBD

User Acceptance Training End User TBD
Inventory and Shipping Training Admin/Delivery TBD
personnel

11.4. Defect Management

Any Defects will be logged into our database of defects, these are categized by time received,
level of severity. When Defects are followed up on, they are logged in an additional database,
with date completed, and resolution used.

Test Plan GlobalTrak, version 1.0

Page 19 of 22
Test Plan GlobalTrak

12. Definitions
The following acronyms and terms have been used through out this document
Term/Acronym Definition

Test Plan GlobalTrak, version 1.0

Page 20 of 22
Test Plan GlobalTrak

13. References
The following documents have been used to assist in creation of this document.
# Document name Version Comments

How to Create a Test Plan 1 https://www.guru99.com/what-

everybody-ought-to-know-
about-test-planing.html

Test Plan GlobalTrak, version 1.0

Page 21 of 22
Test Plan GlobalTrak

14. Points of Contact

The following people can be contacted in reference to this document

Primary Contact

Name Daniel Bedell

Title/Organisation Project Manager

Phone

Email

Secondary Contact

Name

Title/Organisation

Phone

Email

Test Plan GlobalTrak, version 1.0

Page 22 of 22