logo

Testing Report for Driving Knowledge Test Program

   

Added on  2022-10-01

15 Pages2818 Words133 Views
Testing Report for Driving Knowledge Test Program_1
Contents
Background................................................................................................................ 3
Introduction................................................................................................................ 3
Assumptions............................................................................................................... 3
Test items................................................................................................................... 3
Features to be tested................................................................................................. 3
Input data................................................................................................................... 4
Test environment....................................................................................................... 4
Testing....................................................................................................................... 4
System Testing........................................................................................................ 4
GUI Testing.............................................................................................................. 9
Unit tests............................................................................................................... 12
Nunit test codes....................................................................................................... 16
Defects and fixes................................................................................................... 17
Resources.............................................................................................................. 18
Testing Report for Driving Knowledge Test Program_2
Background
Driving Knowledge test is a program that enables users to test their knowledge
using a number of test questions available in the program. The program has two
type of users; A normal user and an admin user. A normal user can only access and
attempt the test questions and then view the results while an admin user can
perform all actions performed by a normal user but can also manage tests which
involves adding, updating and deleting of test questions. Both users are supposed
to login using a username and password and then access different features of the
program depending on the type of user. The normal user is restricted from
accessing features of the program that require administrator rights.
Introduction
This report presents a discussion on the testing of the Driving Knowledge tests
where by unit tests are done on the methods making up the program, Graphical
user interface of the program is tested to make sure all functionalities work as
expected and system tests are performed to make sure the whole program works
as expected. Each of the tests is documented.
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.
Testing Report for Driving Knowledge Test Program_3
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 where by 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
System Testing
Test Type System Testing
Test Case Number ST_1
Test Case Name Login
Test Case
Description
Tests whether user is able to login using the correct
login credentials
Specifications
Testing Report for Driving Knowledge Test Program_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Testing Process for Driving Test Knowledge Application
|19
|2934
|311

Testing Report for Driving Knowledge App
|18
|3116
|51

E-Visitor Program for Efficient Data Management
|3
|765
|76

Software Testing: Types, Approaches, Plan, Cases, Logs, Results
|15
|1230
|76

Test Process and Plans | Assignment | Solutions
|5
|1595
|11

Analyzing Security Options for JKL Company
|12
|841
|51