KIJANI ONLINE GROCERY STORE
BSCIT
UNIT CODE: BIT 3205A
TEST PLAN
MICHAEL MOCHAMA ONDIEKI
18/06296
DR. MWENDIA SIMON
9TH NOV 2021
,Contents
1.0 Introduction.....................................................................................................................................................3
1.1 Goals and objectives........................................................................................................................................3
1.2 Statement of scope..........................................................................................................................................3
1.3 Major constraints.............................................................................................................................................3
2.0 Test Plan..........................................................................................................................................................3
2.1 Software (SCIís) to be tested............................................................................................................................3
2.2 Testing strategy...............................................................................................................................................3
2.2.1 Unit testing...................................................................................................................................................3
2.2.2 Integration testing........................................................................................................................................4
2.2.3 Validation testing..........................................................................................................................................5
2.3 Test metrics.....................................................................................................................................................6
2.7 Testing tools and environment........................................................................................................................6
2.8 Test schedule...................................................................................................................................................7
3.0 Test Procedure.................................................................................................................................................9
3.1 Software to be tested......................................................................................................................................9
3.2 Testing procedure............................................................................................................................................9
Functionality Testing.............................................................................................................................................9
Usability Testing..................................................................................................................................................11
Interface Testing.................................................................................................................................................11
Performance Testing............................................................................................................................................12
Security Testing...................................................................................................................................................13
Whitebox testing.................................................................................................................................................14
3.2.1 Unit test cases.............................................................................................................................................14
3.2.1.2 Stubs and/or drivers for component i......................................................................................................14
3.2.1.3 Test cases component.............................................................................................................................14
3.2.1.4 Purpose of tests for component..............................................................................................................15
3.2.1.5 Expected results for component i............................................................................................................15
3.2.2 Integration testing......................................................................................................................................15
3.2.3High-order testing (a.k.a. System Testing)...................................................................................................15
, 1.0 Introduction
Software testing is a process of running with intent of finding errors in software. Software testing assures the
quality of software and represents final review of other phases of software like specification, design, code
generation etc.
1.1 Goals and objectives
To reach 100% correct code
To identify the test methodologies for Unit and System Testing
To provide a procedure for Unit and System Testing
To ensure all Functional and Design Requirements are implemented as clarified in the documentation
To identify the documentation process for Unit and System Testing
1.2 Statement of scope
The current system can be extended to allow the users to create accounts and save products
in to wish list.
The users could subscribe for price alerts which would enable them to receive messages
when price for products fall below a particular level.
The current system is confined only to the shopping cart process. It can be extended to have
a easy to use check out process.
Users can have multiple shipping and billing information saved. During checkout they can
use the drag and drop feature to select shipping and billing information.
1.3 Major constraints
• Compatibility with browsers like Mozilla Firefox, Internet explorer etc
• Using a layered approach in developing the application which would make the application maintainable.
• Learning new technologies like using JavaScript for drag and drop behavior and Ajax toolkit controls with little
guidance. The overall idea of doing this project is to get a real time experience. Learn new technologies
2.0 Test Plan
This section describes the overall testing strategy and the project management issues that are required to
properly execute effective tests.
2.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
2.2 Testing strategy
The overall strategy for software testing is described.
2.2.1 Unit testing
Unit testing emphasizes the verification effort on the smallest unit of software design i.e.; a software component
or module. Unit testing is a dynamic method for verification, where program is actually compiled and executed.
Unit testing is performed in parallel with the coding phase. Unit testing tests units or modules not the whole
software. I have tested each view/module of the application individually. As the modules were built up testing
was carried out simultaneously, tracking out each and every kind of input and checking the corresponding output
until module is working correctly. 20 The functionality of the modules was also tested as separate units. Each of
the three modules was tested as separate units. In each module all the functionalities were tested in isolation. In
BSCIT
UNIT CODE: BIT 3205A
TEST PLAN
MICHAEL MOCHAMA ONDIEKI
18/06296
DR. MWENDIA SIMON
9TH NOV 2021
,Contents
1.0 Introduction.....................................................................................................................................................3
1.1 Goals and objectives........................................................................................................................................3
1.2 Statement of scope..........................................................................................................................................3
1.3 Major constraints.............................................................................................................................................3
2.0 Test Plan..........................................................................................................................................................3
2.1 Software (SCIís) to be tested............................................................................................................................3
2.2 Testing strategy...............................................................................................................................................3
2.2.1 Unit testing...................................................................................................................................................3
2.2.2 Integration testing........................................................................................................................................4
2.2.3 Validation testing..........................................................................................................................................5
2.3 Test metrics.....................................................................................................................................................6
2.7 Testing tools and environment........................................................................................................................6
2.8 Test schedule...................................................................................................................................................7
3.0 Test Procedure.................................................................................................................................................9
3.1 Software to be tested......................................................................................................................................9
3.2 Testing procedure............................................................................................................................................9
Functionality Testing.............................................................................................................................................9
Usability Testing..................................................................................................................................................11
Interface Testing.................................................................................................................................................11
Performance Testing............................................................................................................................................12
Security Testing...................................................................................................................................................13
Whitebox testing.................................................................................................................................................14
3.2.1 Unit test cases.............................................................................................................................................14
3.2.1.2 Stubs and/or drivers for component i......................................................................................................14
3.2.1.3 Test cases component.............................................................................................................................14
3.2.1.4 Purpose of tests for component..............................................................................................................15
3.2.1.5 Expected results for component i............................................................................................................15
3.2.2 Integration testing......................................................................................................................................15
3.2.3High-order testing (a.k.a. System Testing)...................................................................................................15
, 1.0 Introduction
Software testing is a process of running with intent of finding errors in software. Software testing assures the
quality of software and represents final review of other phases of software like specification, design, code
generation etc.
1.1 Goals and objectives
To reach 100% correct code
To identify the test methodologies for Unit and System Testing
To provide a procedure for Unit and System Testing
To ensure all Functional and Design Requirements are implemented as clarified in the documentation
To identify the documentation process for Unit and System Testing
1.2 Statement of scope
The current system can be extended to allow the users to create accounts and save products
in to wish list.
The users could subscribe for price alerts which would enable them to receive messages
when price for products fall below a particular level.
The current system is confined only to the shopping cart process. It can be extended to have
a easy to use check out process.
Users can have multiple shipping and billing information saved. During checkout they can
use the drag and drop feature to select shipping and billing information.
1.3 Major constraints
• Compatibility with browsers like Mozilla Firefox, Internet explorer etc
• Using a layered approach in developing the application which would make the application maintainable.
• Learning new technologies like using JavaScript for drag and drop behavior and Ajax toolkit controls with little
guidance. The overall idea of doing this project is to get a real time experience. Learn new technologies
2.0 Test Plan
This section describes the overall testing strategy and the project management issues that are required to
properly execute effective tests.
2.1 Software (SCIís) to be tested
The software to be tested is identified by name. Exclusions are noted explicitly.
2.2 Testing strategy
The overall strategy for software testing is described.
2.2.1 Unit testing
Unit testing emphasizes the verification effort on the smallest unit of software design i.e.; a software component
or module. Unit testing is a dynamic method for verification, where program is actually compiled and executed.
Unit testing is performed in parallel with the coding phase. Unit testing tests units or modules not the whole
software. I have tested each view/module of the application individually. As the modules were built up testing
was carried out simultaneously, tracking out each and every kind of input and checking the corresponding output
until module is working correctly. 20 The functionality of the modules was also tested as separate units. Each of
the three modules was tested as separate units. In each module all the functionalities were tested in isolation. In
