0% found this document useful (0 votes)
12 views10 pages

Unit Test Specifications Overview

The document outlines the testing phase of software development, emphasizing the importance of detecting and correcting errors through various levels of testing including Unit Testing, Integrated Testing, and System Testing. It provides detailed specifications for unit tests across multiple forms such as Login, Designation, and LeaveRequest, listing test conditions, expected results, and actual results. The document serves as a comprehensive guide to ensure software functionality and reliability before deployment.

Uploaded by

mgharat359
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views10 pages

Unit Test Specifications Overview

The document outlines the testing phase of software development, emphasizing the importance of detecting and correcting errors through various levels of testing including Unit Testing, Integrated Testing, and System Testing. It provides detailed specifications for unit tests across multiple forms such as Login, Designation, and LeaveRequest, listing test conditions, expected results, and actual results. The document serves as a comprehensive guide to ensure software functionality and reliability before deployment.

Uploaded by

mgharat359
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

TESTING

Introduction
Testing is the phase where the error remaining from the earlier phase also must be detected. It
is the process of examining something with the intension of finding errors. Testing a program
consists of providing the program with a set of test inputs and observing if the program as
expected .If the program fails, then the conditions under which a failure occur are noted for
debugging and corrections.

Level of Testing:
Before the implementation of the system, testing has been carried out thoroughly to eliminate
any bugs, which may be [Link] test been conducted based on some level of testing.

They are as follows:

 Unit Testing
 Code walkthrough
 Integrated Testing
 Validation Testing
 Output Testing
 System Testing

Unit Testing:
Testing at the unit level is very much essential because the error is accurate.
Unit testing is testing of different units or modules of a system in isolation. Testing is
done to check whether each module in the software works properly so that it gives
desired outputs to the given inputs.

Code walkthrough:
In this phase of testing the code is thoroughly checked for discrepancies that
may occur in the code such as redundancy of code, deviations in the naming
convention etc.

Validation Testing:
At the culmination of the integration testing the software was completely
assembled as a package , interfacing errors have been uncovered and corrected and a
final series of software validation testing [Link] we test the system in a manner
that can be reasonably expected by the customer, the system was tested against system
requirement specification.
Integrated Testing:
In integrated testing all the code modules are put together and tested for
desired outputs. The modules unit tested are integrated and [Link] the modules are
combined in this testing step. Then the entire program is tested as a whole.
The integrated testing is carried out using integrated test plans prepared in the design
phase of the system development as a guide. All the errors found in the system are
corrected for the next testing steps. The module which are tested show expected
result.

Output Testing:
Feeding sample valid input image and then comparing the ratio obtained in the
compressed output image with the expected ratio conduct it. Correctness of the output
depends on the input image.

System Testing:
In system testing entire system is tested as a whole with all forms,code,
module and class [Link] the integrated testing the whole of the system is
tested in different environments and it is found that the system has performed well
without giving any runtime error. Hence after the testing is concluded that the system
will work fine in all environments.

Unit Test Specification for Login Form:

[Link] Test Condition Expected Result Test Result


1. Valid user id and Main form is As Expected
password is entered displayed
2. User id or password Invalid user message As Expected
is invalid box is displayed
3. If User id or Enter the login As Expected
password is not details message box
entered is displayed

Unit Test Specifiction for Designation Form:

[Link] Test Condition Expected Result Test Result


1. Enter the staff type Staff type of a staff As Expected
is updated
2. Enter the designation Designation of a staff As Expected
is updated
3. Click on save Record is stored and As Expected
displayed in grid
4. Click on reset All the fields are As Expected
cleared
5. Designation or staff Enter the details As Expected
type left blank message is displayed
6. Designation grid Staff type and As Expected
view designation gets
updated in the grid
with delete and edit
option
7. If edit link is clicked Respective record is As Expected
in the grid displayed and
updated
8. If delete link is Confirmation As Expected
clicked in the grid message box is
[Link]
confirmation, record
is deleted

Unit Test Specification for Leaves Form:

[Link] Test Condition Expected Result Test Result


1. Leave code is entered It is updated from As Expected
leaves table
2. Leave type is entered Type of leaves are As expected
displayed
3. No of leaves No of leaves present As Expected
is displayed
4. Details are not Enter the details As Expected
entered message box is
displayed
5. Click on save Record is stored and As Expected
displayed in grid
6. Click on reset All the fields are As Expected
cleared
7. Leaves grid view Leave code,type and As Expected
no of leaves gets
updated in the grid
8. If edit link is clicked Respective record is As Expected
in the grid displayed and
updated
9. If delete link is Confirmation As Expected
clicked in the grid message box is
[Link]
confirmation,record
is deleted

Unit Test Specification for LeaveRequest Form:

[Link] Test Condition Expected Result Test Result


1. Staff no is entered It is updated from As Expected
staff table
2. Leave type is entered Type of leave is As expected
displayed
3. Date Date on which As Expected
request is sent
4. From date From date of the As Expected
leave request is given
5. To date To date of the leave As Expected
request is given
6. No of days It is calculated by the As Expected
difference of to date
and from date
7. Purpose Purpose of the leave As Expected
is mentioned
8. Status Status of the leave is As Expected
displayed
9. Request Leave request is sent As Expected
10. Reset All the fields are As Expected
cleared
11. Cancel Leave request is As Expected
cancelled
12. Details are not Enter the details As Expected
entered message box is
displayed
13. If details entered are Record is stored and As Expected
valid displayed in the grid

Unit Test Specification for Approve Form:

[Link] Test Condition Expected Result Test Result


1. Approve is clicked The leave request As Expected
gets approved
2. Reject is clicked Leave request gets As Expected
rejected
3. Ok button is clicked The option clicked As Expected
gets updated in the
viewleaverequest
grid

Unit Test Specification for Holiday Form:

[Link] Test Condition Expected Result Test Result


1. Date is displayed It is obtained from As Expected
date time picker
2. Holiday is displayed Name of the holiday As expected
is displayed
3. Save is clicked It gets updated to the As Expected
form holiday
4. Reset is clicked It resets the data As Expected
entered
5. Holiday grid view Date and holiday As Expected
details are updated in
the grid

Unit Test Specification for Department Form:

[Link] Test Condition Expected Result Test Result


1. Department Code is Department code of As Expected
entered the department is
updated
2. Department name is Department name of As expected
entered the department is
updated
3. Details are not Enter the details As Expected
entered message box is
displayed
4. Save is clicked Record is stored and As Expected
displayed in grid
5. Reset is clicked All the fields are As Expected
cleared
6. Department details Department code and As Expected
grid view name are updated in
the grid and we have
an option of editing
and deleting the
updates
7. If edit link is clicked Respective record is As Expected
in the grid displayed and
updated
8. If delete link is Confirmation As Expected
clicked in the grid message box is
[Link]
confirmation,record
is deleted

Unit Test Specification for Change Password Form:

[Link] Test Condition Expected Result Test Result


1. Staff no is entered It is updated from the As Expected
staff table
2. Old password is It is updated from As expected
entered change password
table
3. New password is It is updated from As Expected
entered change password
table
4. Confirm password is New password is re- As Expected
entered entered
5. Save Changes is Record is stored and As Expected
clicked password changed
successfully message
box is displayed
6. Details are not Enter the details As Expected
entered message box is
displayed
7. Invalid old or new Invalid password As Expected
password message box is
displayed
8. Invalid confirm Confirm the As Expected
password password message
box is displayed

Unit Test Specification for CurrentYear Form:

[Link] Test Condition Expected Result Test Result


1. From It is updated to As Expected
currentyear form
2. Month Month is entered to As expected
currentyear form
3. Year Year is entered to As Expected
currentyear form
4. Save is clicked Data gets saved in As Expected
currentyear form
5. Reset is clicked Data entered gets As Expected
reset

Unit Test Specification for Branch Form:

[Link] Test Condition Expected Result Test Result


1. Branch code Branch code of the As Expected
branch is updated
2. Branch name Branch name of the As expected
branch is updated
3. Save is clicked Data gets saved in As Expected
branch form
4. Reset is clicked Data entered gets As Expected
reset
5. Branch details grid Branch code and As Expected
view branch name is
updated in the grid
having delete and
edit options

Unit Test Specification for Staff Form:

[Link] Test Condition Expected Result Test Result


1. Staff No Staff no of the staff is As Expected
updated
2. Staff Name Staff name of the As expected
staff is updated
3. Address Address of the staff As Expected
is updated
4. Land line Land line of the staff As Expected
is updated
5. Mobile Mobile no of the staff As Expected
is updated
6. Date of join Date of join of the As Expected
staff is updated
7. Designation Designation is As Expected
updated from the
designation table
8. Branch Branch of the staff is As expected
updated from branch
table
9. Department Department of the As Expected
staff is updated from
department table
10. Save is clicked Details gets updated As Expected
to the staff table
11. Reset is clicked Data gets reset As Expected
12. Staff grid view Staffno,Staffname ,a As Expected
nd all the above
details gets updated
along with edit and
delete options

Unit Test Specification for User Form:

[Link] Test Condition Expected Result Test Result


1. Staff no Staff no of the staff As Expected
is updated
2. Password Password is updated As expected
3. CreateUser is clicked User is created As Expected
4. Reset is clicked Data entered gets As Expected
reset
5. User details grid Staff no and As Expected
view password gets
updated

Unit Test Specification for View Leaverequest Form:

[Link] Test Condition Expected Result Test Result


1. Search by It searches the leaves As Expected
requested on the
basis of date of
request,staffno and
status
2. Date of request Displays when the As expected
leave was requested
3. Staff no Displays the staff no As Expected
who has requested
the leave
4. Status Displays the status of As Expected
the request
5. Viewleaverequest Staffno,leave As Expected
grid view type ,etc is updated
in the grid

Unit Test Specification for Master Form:

[Link] Test Condition Expected Result Test Result


1. Bank Information Gives details of the As Expected
bank
2. Staff Gives details of the As expected
staff forms
3. Leaves Gives details of the As Expected
leaves forms

Unit Test Specification for Staff Pay Form:

[Link] Test Condition Expected Result Test Result


1. Staff No Staff no of the staff is As Expected
updated
2. Basic Pay Basic pay of the staff As expected
is given
3. Special Pay Special pay of the As Expected
staff is given
4. DA Dearness allowance As Expected
of the staff is given
5. HRA House Rent As Expected
Allowance of the
staff is given
6. FPA Fixed Personal As Expected
Allowance of the staff
is given
7. Convayence Convayence of staff As Expected
is calculated
8. CCA City Compensatory As expected
Allowance of staff is
entered
9. Wash Allowance Wash allowance of As Expected
staff is entered
10. Other Earnings Other earnings of As Expected
staff is calculated
11. Earning arrears Earning arrears of As Expected
staff is entered
12. Official Pay Officiating payments As Expected
of the staff is entered
13. Hill and fuel Fuel expenses are As Expected
entered
14. Gross Gross of the staff is As Expected
calculated
15. PF Contribution Provident Fund As Expected
contribution of the
staff is deducted
16. V.P.F Voluntary Provident As Expected
Fund of staff is
deducted
17. Staff Insurance Insurance of staff is As Expected
deducted
18. P.L.I.C Policy deductions As Expected
19. Family Welfare Family welfare As Expected
expenses are
deducted
20. Profession Tax Profession tax of As Expected
staff is deducted
21. Union Fees Union fees of the As Expected
staff is deducted
22. Income tax Income tax of the As Expected
staff is deducted
23. Exgratia salary Exgratia salary of the As Expected
staff is deducted
24. PF Arrears Provident Fund As Expected
Arrears of staff is
deducted
25. VBEC1 Union fees of staff is As Expected
deducted
26. VBEC2 Union fees of staff is As Expected
deducted
27. VBEC3 Union fees of staff is As Expected
deducted
28. HR Deduction HR expenses is As Expected
deducted
29. Furniture Deduction Furniture deductions As Expected
are done
30. Petrol and oil Petrol and oil expenses As Expected
are deducted
31. Other br cr Other expenses As Expected
32. Suspense Pay Suspense pay is As Expected
deducted
33. Excess Rent Excess rent of staff is As Expected
deducted
34. Other deduction Other deductions are As Expected
done
35. PF loan Provident Fund loan of As Expected
staff is deducted
36. PRO loan Pronote loan of staff is As Expected
deducted
37. INT FLN Interest free loan of As Expected
staff is dedeucted
38. SPL loan Special loan of staff is As Expected
deducted
39. SEC loan Secured loan is As Expected
deducted
40. LMV loan Loan on MotorVehicle As Expected
is deducted
41. HSG loan Housing loan is As Expected
deduced
42. MRTG loan Mortgage loan is As Expected
deducted
43. SC/ST fee Scheduled caste fee is As Expected
deducted
44. Deductions Total deductions are As Expected
calculated
\

You might also like