0% found this document useful (0 votes)
25 views14 pages

Payroll System

The document discusses testing various units and modules of a leave management system. It describes unit testing individual components in isolation, code walkthroughs to check for errors, integrated testing to combine components, and system testing of the full system. Test specifications are provided for login, staff designations, leaves, leave requests, approving requests, and holidays to validate inputs, outputs, and functionality across different use cases. The testing aims to eliminate bugs before implementation and ensure the system meets requirements.

Uploaded by

தருண்
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
25 views14 pages

Payroll System

The document discusses testing various units and modules of a leave management system. It describes unit testing individual components in isolation, code walkthroughs to check for errors, integrated testing to combine components, and system testing of the full system. Test specifications are provided for login, staff designations, leaves, leave requests, approving requests, and holidays to validate inputs, outputs, and functionality across different use cases. The testing aims to eliminate bugs before implementation and ensure the system meets requirements.

Uploaded by

தருண்
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

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 present.The 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 begun.Here 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 tested.All 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 modules.After 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:

Sl.No Test Condition Expected Result Test Result


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

Unit Test Specifiction for Designation Form:


Sl.No Test Condition Expected Result Test Result
1. Enter the staff type Staff type of a staff As Expected
is updated
2. Enter the Designation of a As Expected
designation staff is updated
3. Click on save Record is stored As Expected
and displayed in
grid
4. Click on reset All the fields are As Expected
cleared
5. Designation or Enter the details As Expected
staff 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 As Expected
in the grid is displayed and
updated
8. If delete link is Confirmation As Expected
clicked in the grid message box is
displayed.On
confirmation,
record is deleted

Unit Test Specification for Leaves Form:

Sl.No Test Condition Expected Result Test Result


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

Unit Test Specification for LeaveRequest Form:

Sl.No Test Condition Expected Result Test Result


1. Staff no is entered It is updated from As Expected
staff table
2. Leave type is Type of leave is As expected
entered 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 As Expected
leave request is
given
6. No of days It is calculated by As Expected
the difference of to
date and from date
7. Purpose Purpose of the As Expected
leave is mentioned
8. Status Status of the leave As Expected
is displayed
9. Request Leave request is As Expected
sent
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 Record is stored As Expected
are valid and displayed in
the grid

Unit Test Specification for Approve Form:


Sl.No 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:

Sl.No Test Condition Expected Result Test Result


1. Date is displayed It is obtained from As Expected
date time picker
2. Holiday is Name of the As expected
displayed holiday is displayed
3. Save is clicked It gets updated to As Expected
the 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:

Sl.No Test Condition Expected Result Test Result


1. Department Code Department code As Expected
is entered of the department
is updated
2. Department name Department name As expected
is entered of 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 As Expected
and displayed in
grid
5. Reset is clicked All the fields are As Expected
cleared
6. Department details Department code As Expected
grid view and 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 As Expected
in the grid is displayed and
updated
8. If delete link is Confirmation As Expected
clicked in the grid message box is
displayed.On
confirmation,record
is deleted

Unit Test Specification for Change Password Form:

Sl.No Test Condition Expected Result Test Result


1. Staff no is entered It is updated from As Expected
the 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 New password is re As Expected
is entered -entered
5. Save Changes is Record is stored As Expected
clicked and 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:

Sl.No 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:

Sl.No 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:

Sl.No Test Condition Expected Result Test Result


1. Staff No Staff no of the staff As Expected
is updated
2. Staff Name Staff name of the As expected
staff is updated
3. Address Address of the As Expected
staff is updated
4. Land line Land line of the As Expected
staff is updated
5. Mobile Mobile no of the As Expected
staff 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 As expected
is updated from
branch table
9. Department Department of the As Expected
staff is updated
from department
table
10. Save is clicked Details gets As Expected
updated to the
staff table
11. Reset is clicked Data gets reset As Expected
12. Staff grid view Staffno,Staffname As Expected
,and all the above
details gets
updated along with
edit and delete
options

Unit Test Specification for User Form:

Sl.No Test Condition Expected Result Test Result


1. Staff no Staff no of the staff As Expected
is updated
2. Password Password is As expected
updated
3. CreateUser is User is created As Expected
clicked
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:

Sl.No Test Condition Expected Result Test Result


1. Search by It searches the As Expected
leaves 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 As Expected
no who has
requested the leave
4. Status Displays the status As Expected
of the request
5. Viewleaverequest Staffno,leave type As Expected
grid view ,etc is updated in
the grid

Unit Test Specification for Master Form:

Sl.No 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:

Sl.No Test Condition Expected Result Test Result


1. Staff No Staff no of the staff As Expected
is updated
2. Basic Pay Basic pay of the As expected
staff is given
3. Special Pay Special pay of the As Expected
staff is given
4. DA Dearness As Expected
allowance 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 As Expected
staff 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 As Expected
payments of the
staff is entered
13. Hill and fuel Fuel expenses are As Expected
entered
14. Gross Gross of the staff As Expected
is 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 As Expected
is 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 As Expected
the staff is
deducted
24. PF Arrears Provident Fund As Expected
Arrears of staff is
deducted
25. VBEC1 Union fees of staff As Expected
is deducted
26. VBEC2 Union fees of staff As Expected
is deducted
27. VBEC3 Union fees of staff As Expected
is 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 As Expected
expenses 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 As Expected
is deducted
34. Other deduction Other deductions are As Expected
done
35. PF loan Provident Fund loan As Expected
of staff is deducted
36. PRO loan Pronote loan of staff As Expected
is deducted
37. INT FLN Interest free loan of As Expected
staff is dedeucted
38. SPL loan Special loan of staff As Expected
is deducted
39. SEC loan Secured loan is As Expected
deducted
40. LMV loan Loan on As Expected
MotorVehicle 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 As Expected
is deducted
44. Deductions Total deductions are As Expected
calculated
\
STUDENTS FACULTY COORDINATOR HOD

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy