SCOUTING PROGRAM

TEST PLAN
MOSES KIPKEMOI KIPNGENO
19/05914
BSC. INFORMATION SECURITY AND FORENSICS
MR. FRED OMONDI
Contents
Introduction...........................................................................................................................................3
2.0. Goals and objectives..................................................................................................................3
3.0. Purpose......................................................................................................................................3
4.0. Statement of scope....................................................................................................................3
5.0. Major constraints......................................................................................................................4
6.0. Formal reviewing............................................................................................................................4
7.0. Testing plan...............................................................................................................................4
8.0. Software to be tested................................................................................................................4
9.0. Strategy of testing......................................................................................................................5
Unit testing........................................................................................................................................5
Integration testing.............................................................................................................................5
Validation testing...............................................................................................................................6
9.6. High order testing.......................................................................................................................6
10.0. Testing process.............................................................................................................................7
11.0. Test schedule................................................................................................................................7
12.0. Conclusion....................................................................................................................................8
Introduction
System testing is testing conducted on a complete integrated system to evaluate the
systems compliance with its specified requirements.

The various functionalities of the system are tested from an end-to-end perspective to
evaluate the full potential of the document

Before being released into the highly growing software market, a developed system is
usually created depending on the request of the client. Thus, different users, depending
on their occupations, require different applications

2.0. Goals and objectives.

The main aim of system testing is to assess the quality of the software developed and to display the
real image of the system functionalities to the stakeholders and the users.
It is also meant to discover situations in which the behaviour of the software is incorrect or does not
confirm to its specifications. The objectives of the system will be;
 • To ensure proper functionality – the system is to work properly under different
test cases.
• To expose the systems defects if there are any.

3.0. Purpose.
The main purpose of the testing document is to present the functionality of the Scouting program and
to make sure good players are highlighted to the scouts
Scouts are also provided with issues about technicality, restrictions, risk factors, etc. It can be done in
the forms of:

• Test coverage
• Test conditions  Test reports

4.0. Statement of scope.

 The user(scout) should be able to login after a successful entry of his/her username and
password to access the systems services.
 All information and details required by the user should be readily available when searched.
 The software should be able to work efficiently in the process of receiving and retrieving
data.

All the stored reports should also be able to be generated at any time.

5.0. Major constraints

 Timing factor

Complete system testing was time consuming and cumbersome but it was successful
during the development phase.

 Funding

The system development was costly but the stakeholders were able to aid in the funding
process.
6.0. Formal reviewing
All the formal reviews that were raised were well handled and have greatly been of a major impact to
the completion of the quality software.

7.0. Testing plan.

The test plan describes the procedure in the testing approach. Test planning can also be considered as
a project plan since it conveys how the testing will be done at different particular levels.
It also describes the strategy, deliverables, schedule, objectives and resources required to perform the
testing in a respective software product. With a test plan, you can be able to determine the quality
validation of the application and confirm that all the requirements have been met.
The software testing carried out didn’t find any defects and confirmed the system had met all the user
requirements.

8.0. Software to be tested

The software tested was Scouting Program system and was considered fit.

9.0. Strategy of testing

Testing strategy was performed in different levels. The strategy testing levels in a respective order of
execution was;

 The unit testing.

 Integration testing
 Validation testing
 High-order testing

Unit testing
Unit testing is the process of testing individual components in isolation. The testing was done to each
and every component to verify the results.
The outcome is demonstrated below;

Tested field Expected outcome Actual outcome

Username The username should be correct. Confirmed correct username.

Password The password characters should Didn’t show the characters.
not show.
Email Should be fully displayed Was fully displayed

Integration testing
Integration testing is the general testing. This testing is done to ensure the application created
functions efficiently when running with different applications at the same time.
This type of testing was also aimed to discover if any issues arises when the components are
integrating.

Procedure carried out Expected outcome Actual outcome

Increase process by adding a The components should Integrated well

component to the system and integrate smoothly and function
observing the integration properly
process.

Installed the application in the Should sync and work well Synced and worked as intended
user’s system and observe how
it syncs with other systems
applications

Validation testing.
The system was initialized with test case, that is, the namely input is keyed in and expected output is
displayed.
A portion of tested components are as shown below.

Tested area Expected outcome Conclusion

Save Entry saved to database Done

Delete Field removed Done

Add New detail inserted to database Done

9.6. High order testing.

High order testing consisted of various other testing types. This was to ensure the system functions
under pressure of other conditions.
The various types of other tests include:

• Security testing. – the security test was done to be sure of the systems database
details.
 • Recovery testing. – the system was also tested for its ability to recover from
constant problems and failures.
• Stress testing. – in this testing, we monitored the system to make sure it does not
experience any crashes and failures.

10.0. Testing process.

The testing process is as shown;
11.0. Test schedule.
Activity Planned Planned Actual Actual
start finish start finish
Test plan 15/11/2021 18/11/2021 16/11/21 17/11/21
design
Execute 18/11/2021 20/11/2021 19/11/21 2120/11/21
predefined
tests
Generate test 20/11/2021 24/11/21 2211/21 25/11/21
report

12.0. Conclusion
Testing process requires total keenness as it is the vital part to ensuring a well functioning
system. It requires procedural planning and continuous involvement of the stakeholders in
conjunction with the presence of the developer to fulfill the meeting of all requirements as
requested