DRIVER KNOWLEDGE TEST

PROGRAM REPORT

EDITED BY:
MUSKAN PANDEY
CANTERBURY BUSINESS COLLEGE

REPORT NAME STUDENT DETAILS

 Table of Contents

Contents
1. Background...................................................................................................................................3
2. Introduction...................................................................................................................................3
3. Test Objective...............................................................................................................................3
4. Assumption...................................................................................................................................3
5. Process Overview........................................................................................................................3
6. Test Item.........................................................................................................................................4
7. Features to be tested...................................................................................................................4
8. Approach........................................................................................................................................4
9. Test Environment.........................................................................................................................4
10. Test cases with execution result:..........................................................................................5
11. Test execution results with N-unit:......................................................................................10
12. Bugs Report form:..................................................................................................................11
13. Test Deliverables:...................................................................................................................12
14. Roles and Responsibilities:...................................................................................................12
1. Project Manager:.................................................................................................................12
2. Test Leader:.........................................................................................................................12
3. Testers:.................................................................................................................................12
15. Responsibilities:.......................................................................................................................12
16. Staffing and Training:.............................................................................................................12
17. Schedule:...................................................................................................................................13
18. Approval:....................................................................................................................................13
19. References:...............................................................................................................................13
1. Background
Driving Knowledge Test Program is developed in VB.Net by windows application.
Administration and users are the two kinds of users in this program. This program
consists 3 parts which are given below:
1) Login
2) Question
3) Test Knowledge and Result

The main user of the program have the access to login in this programme. The main
user or the admin of this program have the role to add, update and delete the
questions. After the role of the admin, the user can login and test the knowledge and
gets the result straight on their screen.

2. Introduction
This archive is a point by point review characterizing testing system for the Driving
Knowledge Test Program. Its goal is to impart quality benchmarks and methods.
This record is the product test report of the discovery, white box testing period of the
Driving Knowledge Test Program. It contains the consequences of tests, which were
executed amid the testing procedure. All through the testing procedure we will apply
the test documentation determinations portrayed in the IEEE Standard 829 for
Software Test Documentation.[ CITATION inf18 \l 3081 ]
3. Test Objective
A main role of testing is to distinguish programming disappointments with the goal
that deformities might be found and revised. It is the way toward approving and
confirming that a program:

1. Meets the necessities that guided its outline and advancement,

2. Functions not surprisingly,
3. Can be actualized with similar qualities,
4. Meeting the every requirements of the customer.
5. Works as expected
This report contains tests done for given program at different levels such as
6. Unit testing
7. GUI testing

Functions used to manage this application are:

Login, load From File, add Question, find Question, update Question, delete
Question, save all File, submit Answer and Check and calculate Result. User
interface to utilize these functions is designed to be user friendly. [ CITATION ist181 \l
3081 ]
4. Assumption
 Testing method (practical testing or acknowledgment testing)
 Test condition set up date.
 Association with GUI is prepared.
 Association with different gadgets are finished

5. Process Overview
The following represents the overall flow of the testing process:
1. Recognize the essentials to be attempted. All analyses ought to be resolved using
the present Program Determination.
2. Recognize which particular test(s) will be used to test each module.
3. Review the test data and examinations to ensure that the unit has been inside and
out checked and that the test data and analyses are tasteful to affirm proper
undertaking of the unit.
4. Perceive the ordinary results for each test.
5. Report the investigation course of action, test data, and expected results.
6. Play out the test(s).
7. File the test data, test cases, and test game plan used in the midst of the testing
methodology. This information may be submitted through the Unit/Framework Test
Report (STR).
8. Productive unit testing is required before the unit is fit the bill for part
joining/structure testing.
9. Unsuccessful testing requires a Bug Report Frame to be delivered. This record
ought to depict the analysis, the issue encountered, its possible reason, and the
course of action of events that incited the issue. It ought to be used as a purpose
behind later particular examination.
10. Test files and reports may be submitted. Any points of interest to be investigated,
updated, or invigorated ought to be dealt with speedily.
6. Test Item
1. Login module (for administrator and client)
2. Deal with the database
3. Look after outcomes
4. Interface of framework
5. Change of information (questions)

7. Features to be tested
1. Login
2. Irregular choice of inquiries
3. Adjust/refresh/erase work (chairman)
4. Spare
5. Advance or in reverse
6. Figure and show Result

8. Approach
1. Sort of testing utilized: discovery testing, white box testing
2. Capacity testing
3. Robotized testing utilizing N-unit.

9. Test Environment
Testing of given program has been done in Visual Studio. Below are the minimum
requirements for Visual Studio 2012:

Hardware Requirements:
 1024MB RAM
 3GB of hard disk space
 5400 RPM hard disk drive
 DirectX 9-capable video card that runs at 1280 X 1024 or higher resolution
Software Requirements:
 Windows 7
 Windows 8
 Windows 8.1
 Windows 10
People:
 Project Manager: Muskan Pandey
 Test Leader: Smile Pandey
 Tester: Uzol Dhakal[ CITATION unl18 \l 3081 ]

10. Test cases with execution result:

Test Type Functional testing 01

Test Case Description  Login form testing
Step Procedural Expected result Actual result Pass/Fail
s Actions
Form Load Main form will be Main form Pass
1 displayed showing the displayed with
login page login page
Enter username Username and Password Page will be Pass
2 and password box will be displayed and continue to the
we can write valid data. next step

Test Type Functional testing 02

Test Case Description  main form testing
Step Procedural Expected result Actual result Pass/Fail
s Actions
Form Load Main form will be Main form shown Pass
1
shown
Click Test Your Test information Test information Pass
2 Knowledge form will be shown form was shown
Button
Click Question User will be able to User was able to Pass
3 button process the question access the question
form form.
Click close button Application will be Application was pass
4
closed closed
Test Type Functional testing 03
Test Case
Test Information form testing
Description 
Step Procedural Expected result Actual result Pass/Fail
s Actions
Form Load Test information form Test Information Pass
1
will be shown form shown
Click start It will continue to the Continue to the test Pass
2
Button test form form
Click Cancel It will close the form and Form closed and Pass
3 button it goes back to the main main form will be
form. shown.

Test Type Functional testing 04

Test Case Description  Test form testing
Step Procedural Expected result Actual result Pass/Fail
s Actions
Form Load Test form will be Test form shown Pass
1
shown
Click Test Your Test information form Test information Pass
2 Knowledge Button will be able to form was displayed
continue
Click Next button Next question will be Next question Pass
3
shown shown
Click Back button Previous question will Previous question Pass
4
be shown shown
Click Submit All the questions and Submitted Pass
5 Button answer will be successfully
submitted
Click Quit Test Correct answer will Correct answer Pass
6
Button be shown shown successfully
Test Type Functional testing 05
Test Case
Question form testing
Description 
Step Procedural Expected result Actual result Pass/Fail
s Actions
 Form Load Question form will be Question form Pass
1
displayed displayed
Click add Data will be added in the Data added Pass
2
Button system successfully
Click Save Data will be saved in the Data saved Pass
3
button system successfully
Click find Selected data will be Data shown pass
4
button shown successfully
Click Update Selected questions or data Data updated Pass
5 Button will be updated successfully
successfully
Click Delete Selected questions or data Data deleted Pass
6
Button will be deleted successfully successfully
Click Exit Question form will be Question form Pass
7
Button closed closed
11. Test execution results with N-unit:
Following are the test result which are obtain while running the test using N-unit:
12. Bugs Report form:

Name of Program: Driver Knowledge test Date: 2018/02/20

Bugs and error:

There are two types of error in this program which are submitted below:
1)Error in coding
2)Error in design

Problem:
In this program there are two errors in coding so that the login function doesn’t works
properly and also the error in the save button the question form doesn’t works
properly.

Fixing the error:

(1) Delete user because user is not on the list
(2) Change coding on the Exam class
(3) Change coding on the Main Form

Tested by Muskan Pandey Date: 22/02/2018

Reported By Smile Pandey Date: 22/02/2018
Resolved by Asmat Tharu Date: 22/02/2018

[ CITATION bug18 \l 3081 ]

13. Test Deliverables:
1. Test Design
2. Experiment
3. Execution
4. Blunder Documentation
5. Test Report
6. Application Source Code

14. Roles and Responsibilities:

1. Project Manager:
Audit and Endorsement of Venture of the testing procedure, approach, and
plans. Audit of testing results and deformities to decide/get to effect to general
extend plan and usage plan. Give formal approve all testing expectations and
testing occasions.[ CITATION pro18 \l 3081 ]
2. Test Leader:
Works with QA Lead and Testing Organizer to design and get ready for
testing. Screen testing progress; guarantee testing is being doled out for a
specific module territory. Give formal approve all testing expectations and
occasions. Give input, manage and survey the written work of utilization cases
and experiments. Work with Testing Facilitator and others to guarantee utilize
cases and experiments are composed accurately to guarantee finish test
scope.[ CITATION ist18 \l 3081 ]
3. Testers:
Works with QA Lead and Testing Facilitator to design and get ready for
testing. Screen testing progress; guarantee testing is being doled out for a
specific module territory. . Give formal approve all testing expectations and
occasions. Go to month to month QA meeting and may go to amass up close
and personal testing gatherings when expected to help Testing Facilitator in
settling issues.[ CITATION sta18 \l 3081 ]

15. Responsibilities:
Task Name(it can be done by Position
team or user)
Test Plan Muskan Pandey Test Leader
Test case Smile Pandey Senior tester
Execution of test case Uzi Dhaka Tester
Document Error Thru Junior Tester
Create test report Sula Documenter
16. Staffing and Training:
Requirement of staff or if it is an acceptance testing needs to design a training
session as already done in previous terms.
17. Schedule:
Task Days (number days Start(Date) Finish(Date)
to finish each task)
Test Plan 3o days 15/01/2018 15/02/2018
Test case 20 20/01/2018 10/02/2018
Execution of test 10 20/01/2018 30/01/2018
case
Document error 5 06/02/2018 11/02/2018
Create test report 1 10/02/2018 11/02/2018

18. Approval:
Tasks Approval By Whom(Designation of Date
person and name)
Test Plan Project manager (Muskan 15/01/2018
Pandey)
Test case Test Leader (Smile 20/01/2018
Pandey)
Execution of test case Tester(Uzi Dhaka) 20/01/2018
Document error Junior tester(Thru) 06/02/2018
Create test report Documenter(Sula) 10/02/2018

19. References:

References
bugreport. (2018, 02 24). bugreport. Retrieved from bugreport: https://bugreport.java.com

infosys. (2018, 02 26). infosys. Retrieved from www.infosys.com: https://www.infosys.com/it-

services/validation-solutions/white-papers/documents/test-result-reporting.pdf

istqbexamcertification. (2018, 02 21). software-testing-objectives-and-purpose. Retrieved from

istqbexamcertification: http://istqbexamcertification.com/what-is-the-software-testing-
objectives-and-purpose/

istqbexamcertification. (2018, 02 23). what-are-the-roles-and-responsibilities-of-a-test-leader.

Retrieved from istqbexamcertification: http://istqbexamcertification.com
projectsmart. (2018, 02 25). the-role-of-the-project-manager. Retrieved from projectsmart:
https://www.projectsmart.co.uk/the-role-of-the-project-manager.php

stackexchange. (2018, 02 20). what-are-the-main-role-and-responsibilities-of-a-tester. Retrieved

from stackexchange: https://sqa.stackexchange.com

unlockwindows. (2018, 02 15). beta-system-requirements. Retrieved from unlockwindows:

http://www.unlockwindows.com/visual-studio-11-beta-system-requirements/