Online Backstage Management System (OBMS) Software Test Plan Document

This document presents a comprehensive test plan for the Online Backstage Management System (OBMS), a system designed to manage competitors in various sections. The plan encompasses a master test plan, unit test plan, integration test plan, and system test plan. It outlines the purpose, objectives, roles, and responsibilities of the testing team, including developers, project managers, and stakeholders. The test plan defines the scope, covering integration, user acceptance, and regression testing, while excluding user certifications and unit testing by external teams. Detailed test cases are provided, along with a traceability matrix and a Gantt chart for project management. The document also includes budget considerations and document approval procedures, ensuring a structured approach to software testing. The testing strategy includes unit, integration, system, user acceptance, and regression tests, with clear responsibilities assigned to the development team and other stakeholders. This ensures that the system is fully functional and all requirements are met.

Running head: ONLINE BACKSTAGE SOFTWARE TESTING 1
Online Backstage Software Testing
[Student name]
[University name]

2Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Table of Contents
1 Summary.............................................................................................................................................3
2 Test plan - including requirements traceability matrix........................................................................4
2.1 Master test plan...........................................................................................................................4
2.2 Instruction...................................................................................................................................4
2.3 Purpose........................................................................................................................................4
2.4 Test Objectives............................................................................................................................4
2.5 Roles and Responsibilities............................................................................................................5
2.6 Test Scope....................................................................................................................................6
2.7 Processes and References............................................................................................................6
2.8 Items to Be Tested.......................................................................................................................6
2.8.1 Overview of Test Inclusions................................................................................................7
2.8.2 Overview of Test Exclusions...............................................................................................8
2.9 Test Approach..............................................................................................................................8
2.9.1 Unit Test.............................................................................................................................10
2.9.2 Integration Test..................................................................................................................13
2.9.3 System Tests......................................................................................................................16
2.10 Test Environment (tools, system, databases)............................................................................18
2.11 Test Cases..................................................................................................................................18
2.11.1 System test cases...............................................................................................................18
2.11.2 System traceability matrix.................................................................................................19
2.12 Gantt chart.................................................................................................................................20
2.12.1 Test Milestones..................................................................................................................20
2.12.2 Gantt chart diagram...........................................................................................................21
2.13 Budget.......................................................................................................................................21
2.14 Document Approval...................................................................................................................22
Reference..................................................................................................................................................22

3Running head: ONLINE BACKSTAGE SOFTWARE TESTING
1 Summary
The system development is a major process where the development team conducts system
requirements analysis, the system design and the system development. This is report about the
test plan for the proposed Online Backstage Management System that is meant to record the
various competitors who are classified according to sections.
This report covers the various aspects in the test plan that includes the master test plan, the unit
test plan, integration test plan and system test plan.
The report however highlights the various test cases, traceability matrix test scope, test objective,
test purpose, roles and responsibilities of involved people, the items to be tested , the items not to
be tested, the test approach to be used, the test environment, the Gantt chart and the test
document approvals.
The system testing will therefore be important to ensure each system unit is fully functional and
all the entire integrated system is also functional.

4Running head: ONLINE BACKSTAGE SOFTWARE TESTING
2 Test plan - including requirements traceability matrix
2.1 Master test plan
2.2 Instruction
This is the test plan document that is meant to define the process of doing the master test plan.
After the outlining of the master test plan the test plan documents will be constantly be reviewed
and then be approved by the selected technical development team of this project and the selected
business team member’s representatives. In case there are some changes that will be introduced
while executing or testing the system project, the master test plan document will be updated and
re-approved by both technical team and business representative team members.
2.3 Purpose
This test plan is designed due to the following purposes:
i. Documenting the entire tests processes.
ii. Describing of the test strategy which includes the test levels.
iii. To include the various test activities that will be performed.
iv. Documenting those who will be performing the testing activities.
2.4 Test Objectives
The following are the master plan objectives:
i. Providing the 100% test coverage of the documented system requirements.
ii. To cover the system software design documented elements.
iii. To do the execution of the various test cases during the users functional testing.
iv. To do the execution of the performance testing.
v. Creating, maintaining and controlling the tests environments.

5Running head: ONLINE BACKSTAGE SOFTWARE TESTING
2.5 Roles and Responsibilities
The table below shows the various major roles and responsibilities included in the master test
plan.
Table 1: Roles and Descriptions
Roles Descriptions
Developers Team These are the people who are responsible of designing,
developing and coding the entire system components.
Developers Manager This is the person that will assist the development and
implementation of the entire system master test plan.
Program Manager This is the person that is responsible of planning and
executing the proposed project and also plays a role in
assisting the developer manager in creating the master
test plan.
Stake holders These are the people who hold a place in the organization
and their responsibility would likely affect the system
results.
Tests Analysts These are the people who will be doing the full system
execution of testing processes which includes the
verifying the system technical requirements and the
validating the business requirements.
Tests Leads This is a person that is either seasoned tests analyst or
test team members that is responsible of leading and
coordinating the various activities that are related to the
various aspects of tests that are based on the approved
mater tests plans and schedules.
Test Team/Testers These are the people who will be responsible of
executing the tests and ensuring that the testing
environment is adequately supporting the planned tests
activities.
Test Environment Team These are the people that are responsible of establishing,

6Running head: ONLINE BACKSTAGE SOFTWARE TESTING
maintaining and controlling the test environment.
2.6 Test Scope
This master test plan is going to be used in testing of all Online Backstage Management System
requirements with exception of few requirements and the selected requirements will be tested by
the development team and other stake holders with a reason to ensure that the system is fully
functional and all requirements are meet. However in this master plan the tests will cover the
integration, user acceptance, level and regression testing.
This test plan will not include the user certifications which will be done by the finance team and
unit testing that will be done by the external team.
2.7 Processes and References
The following are the various processes that guide the master test plan implementation.
i. Test Preparation
ii. Product Build
iii. Independent Test and Evaluation
The following are the references that support the implementation of Master Test Plan:
i. Business Requirement Document (BRD) Version 1.1, 08/2019
ii. Requirements Specification Document (RSD) Version 1.1, 08/2019
iii. System Design Document (SDD) Version 1.1, 08/2019
iv. Requirements Traceability Matrix (RTM) Version 1.1, 08/2019
v. Risk Log Version 1.1, 08/2019
2.8 Items to Be Tested
During the master plan testing there are various items that will be tested and they are different
range, these items can be categorized as follows:
i. Application software.
ii. Hardware system.
iii. Developed system.
iv. Project source codes
v. System objects codes.
vi. Jobs control codes.

7Running head: ONLINE BACKSTAGE SOFTWARE TESTING
vii. System documentation.
2.8.1 Overview of Test Inclusions
The following are the various tests that will be done in the master test plan to ensure that system
is functioning properly and the executing environment is well configured.
BR
# Feature
Responsible party or
groups
1. User logon, admin IT
2. User logoff IT, A/P Director
3. Register competitor by section IT, A/P Director
4. Register competitor by group / school. IT, Controller
5. Distribute Updated Information to key
Staff
IT
6. Import data from guidebook. IT, A/P Director
7. Print reports IT, A/P Director
8. Backup data IT, Controller
9. Restore data IT
10. Configure screens IT, A/P Director
11. Recording of Results IT, A/P Director
12. Update Section information IT, Controller
13. Move competitor between sections. IT
14. Displaying Competitor information IT, A/P Director
15. No client install IT, Controller
16. Setting Security passwords IT, A/P Director
17. Administration panel IT, Controller
18. Register by Section IT, Controller
19. Welcome screen IT
20. Display Sections that the Competitor is in IT, A/P Director
21. Data backup / restore IT, A/P Director
22. Field validation IT, Controller
23. TV display IT

8Running head: ONLINE BACKSTAGE SOFTWARE TESTING
(Tycho, 2014).
2.8.2 Overview of Test Exclusions
The below are the various components and features and combination of those components that
will not be done test:
BR
# Feature
1. Maintain historical records
2. Resemble existing system
3. Multiple sites
4. Roles
5. Discipline
6. Section
7. Displaying the Competitor
8. Competitor sequence number
9. Communication tool
10. PDA compatibility
11. Debating
2.9 Test Approach
In this section it entails the various testing strategies that are going to be followed in the
conducting the master test plan (Specialist, 2018).This shows the way the team of developers
plans covers the various activities that are specified in the building of the system, conducting the
independent tests and carrying the system evaluation of the proposed Online Backstage
Management System.
The below is the system testing strategy that will how the various tests, who will carry out tests
and when the tests will be carried.
Test Type Description Comment
Unit Test This is the test that will test individual
system component and it is carried out by
This is done by the team of system
developers after completing every

9Running head: ONLINE BACKSTAGE SOFTWARE TESTING
the system developers to ensure all
components are fully functional.
system stage to ensure full system
functionality.
Integration Test This type of test that is carried by the
system developers and they test how the
various integrated components works,
however it helps to detect if the changed
functionalities are functional end to end.
This is a test that is done by the
developers after integrating the
various unit components to check if
the system is fully functional after
some changes are made.
System Test This is type of test that is done to test the
system environment functionality, this
entails the system software, database
systems, the hardware and the
communication system, However the test
is done before system is installed to the
organization to ensure smooth execution
of the system.
This is the test that is done by the
system developers and also the
network and database administrators
to ensure the system installation
environment is fully functional.
User Acceptance
Test
This is the test that is meant to be carried
out by the business owners, and it mainly
tests the various changes made according
to the system end user requirements.
This is a test that is done after full
implementation of the system by the
development team that is done to
check if all the system requirements
are fully implemented.
Regression Test This is type of test done to the entire
system to ensure that any unimplemented
functionality does not affect the entire
project work and entire system use.
This is the test done by the team of
developers and the system owners.
User Certification
Test
This is type of test that is done after the
entire system is fully implemented and
installed to the organization environment
and this is done to ensure that entire
system had been installed successfully.
This is the test done by the system
owner and in case of hitches they alert
the team of developers.
(Stephen, 2014).

10Running head: ONLINE BACKSTAGE SOFTWARE TESTING
2.9.1 Unit Test
This is the test that is done by the system Developers Team, Developers Manager, Program
Manager, Tests Analysts, Tests Leads, and Test Team/Testers to check the functionality of the
system during the system development process (Paige, 2015).
Test item Role Responsibility
Login form module Developers Team
Developers Manager
Program Manager
Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing Login form module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Registration form module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing registration form module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Guide book module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing guide book module
 Logging system defects
 Documenting tests results.
 Communicating tests results to

11Running head: ONLINE BACKSTAGE SOFTWARE TESTING
management.
 Giving any recommendation on system
improvement
Report print form module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing report print form module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Data backup module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing data backup module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Data restore module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing data restore module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Screens configuration module Tests Analysts  Providing technical directions.

12Running head: ONLINE BACKSTAGE SOFTWARE TESTING
Tests Leads
Test Team/Testers
 Acquiring testing resources.
 Executing the screen configuration module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Results module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing results module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
Section module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing section module
 Logging system defects
 Documenting tests results.
 Communicating tests results to
management.
 Giving any recommendation on system
improvement
competitor module Tests Analysts
Tests Leads
Test Team/Testers
 Providing technical directions.
 Acquiring testing resources.
 Executing competitor module
 Logging system defects
 Documenting tests results.