SCHOOL OF TECHNOLOGY

BACHELORS IN INFORMATION TECHNOLOGY

PROJECT TITLE: ONLINE MUZIKI MUSIC STORE
PROJECT CODE: BIT 3205A

UNIT: FINAL YEAR PROJECT 1

REG. NO: 19/02013
NAME: MAXWEL OWINO ODUOR
SUPERVISOR: EZEKIEL KURIA

THIS PROJECT IS SUBMITTED IN PARTIAL

FULFILMENT OF THE REQUIREMENTS OF THE
AWARD OF BACHELORS IN INFORMATION
TECHNOLOGY IN KCA UNIVERSITY
 DECLARATION

I hereby declare this project is submitted to the full requirements of the diploma in
Information Technology based on my original work and has not been presented in any other
university.

STUDENT
Signature………… Date………..

SUPERVISOR
Signature……….. Date………..
 TABLE OF CONTENTS

1. Test Plan Identifier ………………………………………………………….. 3

1.1Definations………………………………………………………………3
2. Introduction ……………………………………………………………………3
2.1 Goals and Objectives…………………………………………………………….…….3
2.2 Scope…………………………………………………………….…….3

3. MAJOR CONSTRAINTS………………………………………………………….. 3

3.1 Software to be tested …………………………………………………………….…….3

3.2 Testing strategy……………………………………………………………………………….3

3.4 Unit Testing…………………………………………………………………………………………3
4. INTEGRATION TESTING…………………………………………………………………………………………3
5. VALIDATION TESTING…………………………………………………………………………………………3
6. HIGH ORDER TESTING (SYSTEM TESTING)………………………………………………………………….3
7. RECOVERY TESTING………………………………………………………………………………………………3
8 SECURITY TESTING…………………………………………………………………………………………………………..3
9. PERFOMANCE TESTING…………………………………………………………………………………………………………..3

10. ACCEPTANCE TESTING…………………………………………………………………………………………………………..3

11. SYSTEM TESTING…………………………………………………………………………………………………………………3

12. TESTING
PROCEDURE…………………………………………………………………………………………………………………3

13. SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS…………………………………3

Test Plan Identifier: MICRO
FINANACE MANAGEMENT
SYSTEM
1.1 DEFINITIONS
The following are some of the terms and definitions that are related to the test plan of the
Finance management system:
• Pass/Fail criteria: Decision rules that are used to determine whether a software
Item passes or fails a test.
• Test: A collection of one or more test cases
• Test Item: A software item that is an objective of testing.
• Test Plan: A document describing the scope, approach, resources and schedule of
The intended testing activities.
• Test Summary Report: A document summarizing the testing activities and
Results.
• Testing: The process of analysing a software item to detect the differences
Between the existing and required conditions.

INTRODUCTION
This document describes the accreditation requirements for Micro finance Management
system. This system is made with the purpose of outlining the software
Testing is a major source of feedback and serves as a benchmark whether the system is
working efficiently. Testing software will be done to ensure the system produces desired
results.
This process generates a high level test plan document that identifies the software items to
be tested, the degree of tester independence, the test environment, the test case design
and test measurement techniques to be used and rationale of their choice.
The system will do the following:
1. To enable loan approval
2. Cash management.
3. Budgeting.
4. Advanced reporting

This document will address the different standards that will go to account creation and
system testing of the specified application.
 GOALS AND OBJECTIVE
The main goal of testing is to come up with a detailed document that will be used by the
developer and the user to satisfy that the system is able to perform as per the system
requirements

a) The system test should help identify errors, faults, bugs and failures in the system so
that it can be described as a successful test.
b) It should help to establish test cases for the system and also test data to enable an
efficient and effective system test.
c) It should help to establish resources for performing the test in the test plan. These
resources include money for man power.
d) The test schedule is also developed for performing the tests which allocates the time
required for each part of testing and the procedures to be followed.
e) Ensuring that it meets all user requirements as stated in the system requirement
specification.
f) The developed software should be easy to use and understand to all personnel in the
organization.
g) The system should also ensure consistency in the software that has been developed
ensuring there are no deviations from the specifications.

SCOPE

The primary purpose for testing is to detect software failures so that defects may be
uncovered and corrected as early as possible during the development stage. This is a
nontrivial pursuit.
Testing cannot establish that a product functions properly under all conditions but can only
establish that it does not function properly under specific conditions. The scope of this
system testing will include examination of code as well as the execution of that code in
various environments and conditions as well as examining the aspect of code.
 MAJOR CONSTRAINTS
Software to be tested
The software to be tested: financial management system management system to
prove whether it provides the identified objectives.

Testing Strategy
The test strategy consists of various test that will ensure the system is tested appropriately
in units and as a whole and that all its functions are working appropriately.

Unit Testing
Unit testing is where individual components are tested independently to ensure they are
operating correctly before being integrated.

Type of test Area being Expected Actual Incorrect

tested Output Outcome Outcome

Unit Test Inputs

Password It should not Output result of User fails to Log

show password the password into the system.
characters. on the screen.
***

Username Registered User is logged Takes you back

usernames can in. to the
be used. homepage

Screen design Layout Ease of use of All interfaces

and layout interface are in a format
which the
admin and user
can easily
obtain data and
information
 they need
Output design Output Ease of The availability
components producing forms should be
forms in the easily
required format produced.

Database Storage Correct storing The information

and retrieval of entered should
information in be stored in a
the database. correct format.

INTEGRATION TESTING

A system comprises of various different modules which have been developed separately and
have to be combined to come up with a fully functional system that is ready for delivery to
the client. After the modules have been fully tested multiple components are combined.

Integration testing is accomplished incrementally by adding one module at a time to isolate

errors. Integration testing is systematic technique for constructing the program structure
while at the same time conducting test to uncover errors associated with interfacing. The
objective is to take unit tested modules and build a program structure as directed by the
design. It is also concerned with validating that the system meets its functional and non-
functional requirements.

Functional requirements include:

I. A functional attendance system.
II. Consistency and integrity of the database.
III. Accuracy of data entry.
IV. Accurate output from the system.
V. Effective information search mechanism.
VI. Report generation.
VII. Usability in terms of the system interface requirements.

Type of test Area being Expected Actual

tested Outcome Outcome

Integration Test Relationship Entities that are Defines

logically related relationship
should be able to between entities
share data.

Department Reports should be Generates

produced for each relevant reports
operation. for specific users.

VALIDATION TESTING
Validation testing is sometimes called high order testing, tests the software to validate that
it functions in a manner that the end user would expect. This test gives two possible
outcomes: the function or performance characteristics conforms to specifications and are
accepted and a deviation from the specification is uncovered and a deficiency list is
uncovered.

Type testing Area being Expected Actual

tested outcome Outcome

Validation Forms
testing

Add Module Ease of adding Insert new records

records to the to the database.
system.
Delete module Ease of removing Delete records from
existing records the database.
 from the database.

Menu Module Should open the The area being

required account displayed.
creation page.

Update Module Details to be The current details

displayed if it exists. are being updated.

Save Module Should save clients The data is saved.

information to the
database.
Display Module Ability to display Display the content
clients or customer of a table in the
database database.
information when
required.

Search Module Able to find personal Retrieve a required

information where it record from the
is stored. database.
 HIGH ORDER TESTING (SYSTEM TESTING)

This involves carrying out a test after the different components for the entire system have
been integrated. This process is aimed at finding errors that may arise as the different
components interact with each other. It also ensures that the whole system meets its
functional requirements and non-functional requirements.

Test component Status Recommendation

Login Form Pass Validate User

Account Form Pass Allow admin to log into an

account.

Chat Form Pass Communication between

client and admin.

Add product/room Pass Add New product/room

Log Out Form Pass Allow users to log out

RECOVERY TESTING

Recovery testing is the activity of testing how well the application is able to recover from
crashes, hardware failures and other similar problems. Recovery testing is the forced failure
of the system in a variety of ways to verify that recovery is properly performed.
Some of the recovery testing that will be used include:
• Switching off server when the application is loading data after that checking the validity of
applications data integrity.
• Sudden restarting of the computer while the system is running and after that checking the
validity of applications data integrity.

Unplug then plugin data cable when the application is getting data from an external
source and observe if it continues.
•Redirect URL to observe if the key authentication forms can be bypassed by the user
session.
SECURITY TESTING

This is the process to determine that the system protects data and maintains its
functionality as intended.

Concepts covered in security testing are: confidentiality, integrity, authentication,

authorization, availability and non-repudiation.
1. Confidentiality- a security measure which protects against the disclosure of
information to parties other than the intended recipient.
2. Integrity- a measure intended to allow the receiver to determine that the
information which it receives has not been altered in transit or by other than the
originator of the information.
3. Authorization- process of determining that the requestor is allowed to receive a
service or perform an operation. This will ensure access control to the system.
PERFOMANCE TESTING

Performance testing is testing performed from one perspective, to determine how

fast some aspect of the system performs under a particular workload. It will also
serve to validate and verify other quality attributes of the system such as scalability,
reliability and resource usage.

Performance testing can be used to determine if it meets the performance criteria. It

can compare two systems to find which performs better. It can measure what parts
of the System or workloads that cause the system to perform badly. In the diagnostic
case, software engineers use tools such as profilers to measure what parts of a
device or software contribute most poor performance or to establish throughput
levels for maintained acceptable response time. The later a performance defect is
detected, the higher the cost of remediation.
Purposes:

 Demonstrate that the system meets performance criteria.

 Compare two systems to find which performs better.
 Measure what parts of the system or workload cause the system to perform
badly.
ACCEPTANCE TESTING
This testing is generally performed when the project is nearing its end. This test mainly
Qualifies the project and decides if it will be accepted by the users of the system. The
Users or the customers of the project are responsible for the test.

SYSTEM TESTING
The system testing is mainly done on the whole integrated system to make sure that the
Project that has been developed meets all the requirements. The test cases for the system
Testing will be the combination of unit and integration tests
TESTING PROCEDURE
Organise the project- this involves creating a system test plan, schedules and test approach
As well as assigning resources.
Design/ build system test – involves identifying the test cycles, test-cases, entrance and exit
criteria, expected results are identified by the test team.
Design/ build test procedures- includes setting up procedures such as error management
systems and status reporting and setting up the data tables for the automated testing tool.
Build test environment- it entails requesting / building hardware, software, and data
setups.
Execute project integration test.
Execute operations acceptable test.
Log out- happens when all predefined exit criteria have been achieved.

SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS

SUSPENSION CRITERIA
Testing for all the dependant features will be suspended if a test case fails. The failed test
case will be logged onto the test log which contains the description for the error.
RESUMPTION REQUIREMENT
The test cases which are not dependant on the case where the bug is reported will be
executed in parallel with the bug fixing. Once the failed test case has been taken note of and
has been identified and fixed then the testing for the failed test case will resume.
TEST DELIVERABLES
The following documents will be produced after the testing phase for the system has been
completed.
• Test Plan
• Test Cases
• Test Log