Testing Process for Driving Test Knowledge Application

Contents
Background................................................................................................................ 3
Introduction................................................................................................................ 3
Assumptions............................................................................................................... 3
Test items................................................................................................................... 3
Features to be tested................................................................................................. 3
Input data................................................................................................................... 3
Test environment....................................................................................................... 4
Testing....................................................................................................................... 4
Unit tests................................................................................................................. 4
GUI Testing.............................................................................................................. 9
System Testing...................................................................................................... 11
Iv write testing code.............................................................................................. 17
V Track defects and verify fixes............................................................................ 18
Vii) Responsibilities............................................................................................... 18
Viii) Staffing and training....................................................................................... 19
Viii) Schedule........................................................................................................ 19
X) Resources......................................................................................................... 19
Xi) Approval........................................................................................................... 19

Background
The program being tested is called Driving test knowledge which allows the user to
take questions while the user with administrator rights can add, update or delete
questions in the test
Introduction
This report presents the testing process of the application. It discusses the testing
process for unit tests,, GUI tests and system tests.
Assumptions
Testing of the Driving Knowledge test program is done on the following
assumptions;
 All the functional requirements of the program described in the software
specifications documentation have been implemented
 The program runs without crashing unexpectedly.
 The user interface of the program is easy and straight forward to understand
such that its easy to map different features of the program to the specific GUI
in the program.
 The program does not use an external database to store data.
Test items
 Login
 Management of questions
 Attempting a test
 Browsing questions
 Calculation of results
 Flow of user interface
Features to be tested
The following features will be tested;
 User login for both a normal user and an admin. This test should be able to
verify that invalid credentials cannot be used to login into the program while
correct credentials can be used to login to the program for all type of users.
 An administrator user should be able to add a new question.
 An administrator user should be able to modify or update an already existing
question.
 An administrator user should be able to delete an already existing question.
 Any user should be able to open the test.
 Any user should be able to move through question using a next button to go
to the next question and a previous button to go back to the previous
question.
 Any user should be able to view their results after taking the test.
 Any user should be able to exit the program.

Input data
Two types of input data will be used to test the program;
 Valid test data- This set of data will be valid where if the program expects a
certain type of input then that specific input is provided. For example, if the
program expects a number then the provided input should be a number.
 Invalid test data- This set of data will be invalid whereby if the program
expects a certain type of input then a different type of input will be provided.
For example, if the program expects a number for a certain input then a
string will be provided.
Test environment
There are three types of tests that will be performed;
 Unit testing- Unit testing will be performed using the Nunit testing framework
 GUI testing- Graphical user interface testing will be done by running the
program using visual studio.
 System testing- This type of testing will be done by running the program
using Visual studio.
Testing
Unit tests
Unit testing will involve testing the individual methods of the program. The following
tests will be performed.
Test Type Unit testing
Test Case Number UT_1
Test Case Name btnLogin_Click method
Test Case Description This test case verifies that the method
associated with the login button works.
Specifications
Input
Expected
Output/Result
None Running the Nunit test on this method
should either pass or fail
Ste
ps
Procedural Actions Expected result Actual result Pass/
Fail