JComponent

ADVANCE SOFTWARE TESTING (CSE 6013)

HUMAN RESOURCE MANAGEMENT SYSTEM

For IT Center of Balkh University

Prepared by

Khatera Mastanzada (18MCS0105)

Frishta Mirzad (18MCS0104)

Ph.D. KARTHIKEYAN T
Guide

May , 2019
 HUMAN RESOURCE MANAGEMENT SYSTEM
For IT Center of Balkh University

Abstract

A HRMS (Human Resource Management System) is a form of HR software that combines a

number of systems and processes to ensure the easy management of a business’s employees and
data. The main aim of “Human Resource Management System” application is to develop a Human
Resource management module of HR Software. A Human Resource Management System
(HRMS) refers to the systems and processes at the intersection between human resource
management (HRM) and information technology (IT). It merges HRMS as a discipline and in
particular it’s basic HR activities and processes with the information technology field.
This Application mainly aims to maintain the details and information of the employees working
in an organization, payrolls with a facility to edit and update it. The HRMS projects facilitates user
as per their hierarchy and grants privilege to them accordingly. And after completing of this project
we will submit to ITCB (Information Technology Center of Balkh) Company.

1. Introduction
A HRMS (Human Resource Management System) or HRIS (Human Resource Information
System) is a form of HR software that combines a number of systems and processes to ensure the
easy management of a business’s employees and data. These systems could deal with everything
from payroll to performance evaluation, covering the whole business. Human Resources Software
is used by businesses to combine a number of necessary HR functions, such as storing employee
data, managing payrolls, recruitment processes, benefits administration and keeping track of
attendance records. It ensures everyday Human Resources processes are manageable and easy to
access. It merges human resources as a discipline and, in particular, its basic HR activities and
processes with the information technology field, whereas the programming of data processing
systems evolved into standardized routines and packages of Enterprise Resource Planning (ERP)
software. On the whole, these ERP systems have their origin from software that integrates
information from different applications into one universal database. The linkage of its financial
and human resource modules through one database is the most important distinction to the
individually and proprietarily developed predecessors, which makes this software application both
rigid and flexible.

Human Resource Information Systems provide a means of acquiring, storing, analyzing and
distributing information to various stakeholders. HRIS enable improvement in traditional
processes and enhance strategic decision making. The wave of technological advancement has
revolutionized each and every space of life today, and HR in its entirety was not left untouched.
Early systems were narrow in scope, typically focused on a single task, such as improving the
payroll process or tracking employees' work hours. Today's systems cover the full spectrum of
tasks associated with Human Resources departments, including tracking & improving process
efficiency, managing organizational hierarchy, and simplifying financial transactions of all types.
In short, as the role of Human Resources departments expanded in complexity, HR technology
systems evolved to fit these needs.
The Project Human Resource Management System is develop web application designed on
technology. The user interface is we will using HTML, CSS, PHP, Java Script, Bootstrap, JQuery,
and MYSQL while the server side programming is using PHP and My SQL is use as database.
This is the Software Test Plan for the HRMS (Human resource Management System for IT Center
of Balkh University), which is being produced for our client by Team VIT student. Team VIT
student is the development team responsible for both building and testing the code. Team VIT
student will deliver the final system to the university on May 25, 2019.

1.1 Scope

The project is confined to be run on any web server either on internet or intranet. The Application
makes sure that the proper user interface is provided to the communicating Parties to work easily
on the application.

This document describes the plan and procedures that will be used by Team VIT student to verify
that the HRMS performs as specified in the Software Requirements Specification (SRS).
The scope of this document is to cover development and testing of the HRMS in 1 module
Human Resource Record Management. As the development cycle will be compressed into
these 25 days, it is necessary to have a comprehensive and systematic plan for testing the
code units as they are developed and integrated into the overall system. This plan will address all
testing that will occur.

The test scope includes the following:

 Testing of all functional, application performance, security and use cases requirements
listed in the Use Case document.
  Quality requirements and fit metrics HRM
 End-to-end testing and testing of interfaces of all systems that interact with the
HRMS.

1. 2 Purpose
This document is aimed to give a detailed plan of test strategy, test schedule, resources, and
environment for performing Unit test, Integration test, System test and Acceptance test of HRMS.

 This Software Test Plan for the HRMS supports the following objectives.
 To detail the activities required to prepare for and conduct the software tests.
 To communicate to all responsible parties the tasks which they are to perform.
 To define the sources of information used to prepare the plan.
 To define the test tools and environment needed to conduct the software tests.
 To define the acceptance criteria, as agreed to by the client

1.3Objective

The project has been developed keeping in the view the current requirement of Human Resource
Management at any organization keeping in view these objectives:

 To develop an application that deals with the day to day requirement of any organization.

 To enable the end-users as well as the organization come out with an easy to handle
application of the Human Resource Management.

1.4 Project Overview

The Project Human Resource Management System is a complete web application designed on
technology. The user interface is designed using HTML, CSS, PHP, Java Script, Bootstrap,
JQuery, and MYSQL while the server side programming is done completely using PHP and My
SQL is used as database.

Each employee had an Employee ID and password through which he can log in. Depending on the
type of employee, either as user or admin, the employee is logged in or accordingly various
privileges are granted to him to carry out various task through the application.

The application makes sure of the security services and other privacy policies. Its grants privilege
to various employees to perform their work as per hierarchy in the organization.
The Human resource management System includes the processes required to coordinate the human
resources on a project. Such processes include those needed to plan, obtain, orient, assign, and
release staff over the life of the project.

HRMS is particularly developed for human resource management in university / colleges. The
System consists of key modules:

 Personal information management

 Employee labor contract management
 Recruitment & training processing
 Payroll
 Administration panel – Utilities
 Insurance management
 Assessment management
 Income management
 Report management

1.5 System
We were creating Human Resource Management System, this System has some page like
This for use our system, 8 button (Home, Employee, Tasks, Attendance, Report, Profile,
System, about us) when you click up to button you see page of system.

2. Assessing the Need for a HRMS Solution

Before a company makes a decision regarding the selection of a HRMS solution, it is important
for the management team to identify the needs of the company, its processes, and goals for both
long term and short term. It is essential to the success of the project to deeply involve the HR
professionals in the process. Depending on the size and structure of the company, it may be helpful
to have an organization-wide meeting or to select representatives from each department to discuss
HRMS goals and options.

3. Security
Security is of great concern when it comes to choosing a human resources management system.
The information stored in a HRMS is highly sensitive, including proprietary company data and
volumes of personal information about employees. It is essential for companies to choose a
solution that utilizes a method of secure transmission such as SSL which encrypts the data as it
transmits over the internet.

Internal security is also critical; information should be guarded by passwords that have varying
levels of access in relation to what is needed for the job position. While most companies now allow
employees to access portions of HRMS solutions, employees must understand the importance of
maintaining the integrity of the system and protecting the security of the information it contains
(i.e. no password sharing). Safeguards should also be in place to quickly bar terminated employees’
access to systems.

4. System Database ER Diagram

The following figure shows the system database ER diagram with the relationships between each
table, each box shows a table including each table’s attributes. Here as you can see in figure below
this database have six tables named Tasks, staff task, Staff, Attendance, Staff salary and Section
with their entities and relations. And just like these tables other tables also have one to one, one to
many and many to many relations.

Figure 1: System Database ER Diagram

4.1 Use case Diagram

Figure2: Use case diagram HRMS

Figure3: Use case diagram HRMS
Figure4: Use case diagram HRMS

5. Tools to Use

In this part of my paper I will describe the tools to use that I have used in this project:
 PHP
 MYSQUL
 Bootstrap
 JavaScript
 JQuery
 CSS
 HTML

6. Product Perspective
Currently, Siemens has an HRMS already in use. However, with the HRMS we will provide
them with additional capabilities and properties organized neatly. HRMS which is an online
intranet System will be used by four types of employees’ of Siemens. These types who have
different roles can be stated as; admin, manager, HR, employee. Every user enters the main
authentication page and after that, system will grant them authorization. After being authorized
according to their permissions (role type) users will basically query and edit the database via
HRMS.
Figure 5: Use case diagram HRMS

7. Product Functions
HRMS implements some major functions in order to accomplish required tasks. These functions
constitute a basis for the whole system.
The function of human resources (HR) departments is administrative and common to all
organizations. Organizations may have formalized selection, evaluation, and payroll processes.
Management of "human capital" progressed to an imperative and complex process. The HR
function consists of tracking existing employee data which traditionally includes personal
histories, skills, capabilities, accomplishments and salary. To reduce the manual workload of these
administrative activities, organizations began to electronically automate many of these processes
by introducing specialized human resource management systems. HR executives rely on internal
or external IT professionals to develop and maintain an integrated HRMS. Before client–
server architectures evolved in the late 1980s, many HR automation processes were relegated to
mainframe computers that could handle large amounts of data transactions. In consequence of the
high capital investment necessary to buy or program proprietary software, these internally
developed HRMS were limited to organizations that possessed a large amount of capital. The
advent of client–server, application service provider, and software as a service or human resource
management systems enabled higher administrative control of such systems. Currently human
resource management systems encompass:

 Retaining
 Administration
 Managing
 HR planning
 Recruiting/Learning management
 Performance record
 Employee self-service
 Scheduling
 Employee Reassign module
 Grievance handling by following precedents

7.1 Authentication and Authorization

Being connected to internet, users will be able to get into the system. In order to see the interface
related to his/her role type, the users account should be authorized and also his/her user name and
password should be authenticated. These tasks are basically held by the functions implemented
under the header of Authentication and Authorization major function.

7.2 Process Data

These functions which can be examined in that process data major function are basically provides
user to manage the database according to the desired task. These management tasks constitute the
major feature of the HRMS. With the help of these functions a user can update some basic personal
data like contact information, marital status etc. In addition to update data, a user can also search
the database in order to obtain the list of the users' which has the properties desired. Also a user
may also see the specific information about a user or all users which can be named as report. In
other words searching is the operation with rows of the database while reporting is operation with
columns of the database.

7.3 Recruitment
Recruitment of a new person which means introducing a new user to the system can be
accomplished in two steps. When it is needed to add a new user to the system, firstly, HR must
create an employee account, by the way at this step HRMS automatically gives an id to that user.
At the second step, admin creates a user related to that user id.
Figure 6: Use case diagram of Administrator

Figure 7: Use case diagram of Employee

8. Specific Requirements
8.1 Interface Requirements
All the users will see the same page when they enter HRMS. This page asks the users a username
and a password.

Figure 8: The interface which is seen to every user to inter to the system

After being authenticated users will see the interface containing the information of the first tab of
the user role types. This interface include different tabs according to their role types determined
by admin at the authentication phase. By the way, users may have more than one role. Then a user
who has more than one role will be able to see all the tabs that are related to his/her role types.
These tabs can be named as; Personal Data Tab, Employee List Tab, Add New Employee Tab,
Add New User Tab, Manage Users Tab, Users List Tab and Arrange Roles Tab. User who have
employee role have authorization to see only Personal Data Tab, HR role gives right to see
Employee List Tab and Add New Employee Tab. Manager role gives authorization to see only
Manager Tab. And Admin role gives user right to see User List Tab and Arrange Roles Tab. These
authorizations are default ones but an admin can change these authorizations by Arrange Roles
Tab. These tabs can be explained detailed as:

8.2 Personal Data Tab

With the help of this tab, employees will be able to see their personal information which appears
in a user-friendly design and also by means of this tab they may edit, update some information in
other words manage some personal information which are updatable such as contact information,
training information. This tab will only see by the users who has a role of Employee.
 8.3 Add New Employee
Tab With this tab HR can add new employee (when a new employee is recruited) to the employee
database with filling personal master data of this new employee. This tab adds new employee
without any authenticated or authorized user attached to it. In other words only being added via
this interface by HR is not enough to access this system. This account must be validated by admins.
Clicking on this tab an admin will see a window like:

8.3.1 Add New User Tab

With the help of his tab, Admins can add new user to the system. Admin can add user with user
ID and arrange authentication and authorization to it. This user will be created by synchronized to
the employee with the same ID from the employee database

Figure9: Add Employee page.

9.1 Functional Requirements

 Add New Employee
 Name
 Father Name
 Position
 Salary Per Month
  Photo
 Age
 Related Section
 Address
 Operation
 Email
 Phone
 Delete Employee
 Edit Employee
 View Employee Details
 View Employee Attendance Sheet
 Number of present days
 Number of absent days

 Calculate Salary According Attendance Sheet Per Month

 Task list
 Add task list
 Reporting
 Monthly Report
 Tasks reporting According Employee
 Report According User Entered Date

9.2 Non – Functional Requirement

 User Friendly
 Multiple users access
 Authentication Procedure
 System must be secure against viruses
 System must be secure and safe.
 The response time of system must be fast.
 System should have good privacy.
 System must have fault tolerance.

10. Hardware Requirements

The HRMS application will be storing more than 200 employees’ personal data. Roughly … MB
of storage capacity is needed.
 10.1 Software Requirements
 Since HRMS application is a web-based application, internet connection must be
established.
 The HRMS software will be used on PCs and will function via internet or interanet
in any web browser.
 The HRMS application interface will be developed by PHP and CSS
 The HRMS software personal database model will support MYSQL environment
as DBMS.

10.2 Development Environment Requirements

 Eclipse IDE will be used for developing the HRMS web-based interface and its relation
to person database module.  Eclipse IDE Eclipse is a multi-language software
development envirnoment comprising an integrated development environment (IDE) and
an extesible plug-in system. It is written mostly in Java and can be used to develop
applications in Java and, by means of various plug-ins, other programming languages
including Ada, C, C++, COBOL, Perl, PHP, Python, R, Ruby(including on Rails
framework), Scala, Clojure, Groovy, and Scheme. It can be used to develop packages for
the software Mathematica. The IDE is often called Eclipse JDT for Java programming
language, Eclipse ADT (Ada Development Toolkit) for Ada, Eclipse CDT for C/C++, and
Eclipse PDT for PHP.[5] Eclipse is an open source community, whose projects are focused
on building an open development platform comprised of extensible frameworks, tools and
runtimes for building, deploying and managing software across the lifecycle. The Eclipse
community is a not-forprofit, corporation who are members of the Eclipse community hosts
the Eclipse projects and helps develop an open source community and an wolrd of
complementary products and services.[6]
 MySql Administrator or Microsoft SQL Server will be used to create, manage, and
optimize the person database module.
 MySql Administrator
MySQL is a relational database management system(RDBMS)[7] that runs as a server
providing multi-user access to a number of databases. The SQL phrase stands for
Structured Query Language.[8] The MySQL development platform has made its source
code available under the terms of use of the GNU General Public License. Open source
free-software projects use MySQL if it is required a full-featured database management
system. Several paid editions are available for commercial use, and offer additional
functionality. MySQL is also used in may high-profile, large-scale World Wide Web
products, includeing Wikipedia, Goolge, Facebook, and Twitter.
11. Implementation steps of HRMS application and output

Figure10: Login page. User are required to enter their Employee ID and Password

Figure 11: Luck page, User are required to enter their Password.
Figure12: Home page and user is logged in successfully as user/admin.

Figure13: Add Employee page.

Figure14: Add Task Employee page.

Figure15: Task List Employee page.

 Figure16: View of the Database.

12 Test Plan
12.1 Test Phases
Software testing can be implemented at any time in the development process. However, most of
the test effort occurs after the requirements have been defined and the coding process has been
completed.
Testing of an application includes:

 Integration testing
 System Testing
 Acceptance testing

12.1.1 Integration testing

 All code units will be scheduled for integration testing based on the overall test schedule.
Integration testing will focus on testing the interfaces between code units, components, and
subsystems (Module). Integration tests will also be run manual. Any defects found during
integration testing will be entered into the defect tracking spreadsheet. It is the responsibility
of the developer who wrote the code module to find and fix the defect. If it is not known which
module produces the defect, the Test Manager will assign the task of finding the defect to a team
member. Once the defect has been found and fixed, the integration test must be repeated.
Once the integration test has been completed successfully, the test will become part of the
regression test suite.
The person responsible for running the integration test will be either the Test Manager or a team
member designated to be responsible for the test. This assignment of responsibility
will be included on the overall test schedule. The Test Manager, however, may reassign tests based
on the current workload throughout development.
There are four types of testing in the Integration Test:

 Structure Test
 Functional Test
 Stress Test
12.1.2 System testing:
 System testing will be done on the releases prior to delivery to the client and mentors.
This system test will include coverage of all functional requirements and quality attribute scenarios
covered by the completed code. The Test Manager has responsibility for the system test. Any
defects found during system testing will be entered into the defect tracking spreadsheet.

The Test Manager will assign the task of finding the defect to a team member. Once the defect has
been found and fixed, the system test must be repeated. Once the system test has been completed
successfully, the software will be packaged for release to the customer.

There are many types of testing in the system Test, the most popular are:
 Functional Test
 Configuration Test
 Security Test

12.1.3 Acceptance testing:

 Acceptance test will test by customer, it is a test conducted to determine if the requirements of a
specification or contract are met. It is final step of testing, acceptance tests are generally performed
as "black box" tests, and the tester uses specified inputs into the system and verifies that the
resulting outputs are correct, without knowledge of the system's internal workings.
 Associated with Acceptance Test phase is usually a group of services and documentation.
12.1.5 Test Result

12.1.5 Integration testing:

 System is executed Integration testing and meets requirements of integrating components

in SDS.
 Make sure Unit test must be tested fully and completely.
 Integration Test cases and Test reports must be clear and full. These documents will
be updated continuously in project lifecycle.
 Bug log report and outstanding bug list.
 Status of bugs and bug lifecycle must be reported regularly.

12.1.5.2 System testing:

 Qualities attributes in SRS document must be tested fully.
 Functionalities that are described in use cases of SRS document must be tested fully and
completely.
 System test cases and test reports must be completed fully. These documents will be
updated continuously in the project development cycle
 Bug log report and outstanding bugs list
 The status of the bug and bug life cycle must be reported regularly.

12.1.5.3 Acceptance testing:

 Acceptance test cases must be executed fully at the work environment of user.

Test Schedule

No Task description Start date Finish date Assigned to

Test documentation
1 HRMS Test Plan 01/05/2019 28/05/2019 Khatera
Integration testing (In house testing)
1 Execute HRMS All Members
Integration testing
 2 Report HRMS All Members
Integration testing
System testing (In – House Testing)
1 Execute HRMS 15/05/2019 17/05/2019 All Members
System testing
2 Report HRMS 18/05/2019 20/05/2019 All Members
System testing
Acceptance testing (In-house testing)
1 Execute HRMS 20/05/2019 23/05/2019 All Members
user Acceptance
testing
2 Report HRMS 24/05/2019 26/05/2019 All Members
User Acceptance
Testing

13. Human Resource

13.1 Team Information

NO Name Role Team Email

1 Frishta Team HRMS Frishta.mirzad2018@vitstudent.ac.in
Mirzad Leader Team
2 Khatera Team HRMS Khatera.mastanzada2018@vitstudent.ac.in
Mastanzada Member Team

Testing Group has 2 member in implements test documents phase. In System

testing phase, tester must be added
 Project Leader: Frishta Mirzad
 Test Leader : Khatera Mastanzada
 Tester: All Member
 Document writer : All Member
13.2 Training Schedule

Table Training Schedule

NO Description Start date End date Team Instructor
Members
1 Research & May June All Mentor
Training 30,2019 6,2019 Member

13.3 Roles & Responsibilities

 Project Leader: Responsible for schedule and the overall success of the project
 Test leader: Responsible for guidance, plan and track the progress o the work of the test
group.
 Tester: execute testing system following testing documents and discuss with testers about
Fixing bugs, reports to Test leader directly.

Document writer: responsible to develop testing documents (test plan, test cases, and test
report).

14. Test Environment

14.1 Hardware
Table 3 Requirement of Hardware

Test Item Minimum Configuration

1 PC/Laptop  Hard disk space: About 2 GB (full installation incl. two
language modules). About 1 GB (minimal installation incl.
two language modules)
  Memory: more than 512 MB free memory with default
cache settings
 CPU: Equal or more than Pentium 4-2.0 GHz

14.2 Software

Table 4 Requirement of Software

No Table Item Software

1 Work station  Windows XP SP2
 Windows Vista
 Windows 7
2 Development languages,  PHP
Databases, Application server  My SQL Server 2005
 HTML Pad / php my admin

14.3 Test tools

Using Internet Explorer browser to test system testing

14.4 Test Databases

All test results must be saved in the Configuration Management System.
Table 5 testing document deliverables

15. Entrance & Exit Criteria

No Item Description
1 <Human Resource This document describes Test
Management> Strategy and plan when executing
Test Plan Testing phase of Project.
2 < Human Resource This document describes all test
Management > cases for System test phase when
System Test Specification Executing Testing of this project.
3 < Human Resource This document describes all test
Management > cases for Integration test phases
Integration Test when executing Testing of this
Specification Project.
4 < Human Resource This document describes all test
Management> cases for Acceptance test phases
Acceptance Test when executing Testing of this
Specification Project.
5 Test report This document describes the
number of test pass and fails when
Executing test case.
6 Defect report This document describes detail
defect as type, location, tester

16.1 Entrance Criteria

These criteria should be defined before testing phase began and performance by Project
Management, Technical Leader and Test Leader.

16.1.1 Integration testing

 Integration test case has been approved.
 All others test had been successfully completed
 Integration test cases must be available
 Employee must be available
  Environment and test tools must be set up.
 Test documents must be reviewed
 Outstanding Bugs List

16.1.2 System testing

 System test plan has been approved.

 All others test had been successfully completed
 System test cases must be available
 Employee must be available
 Environment and test tools must be set up.
 Test documents must be reviewed
 Outstanding Bugs List

16.1.3 User acceptance testing (optional)

 User Acceptance Test Plan and test cases must be approved and available.
 List of outstanding bugs and issue list
 All others test had been successfully completed
 Employee must be available
 Environment test and test tools must be available
 Test documents must be reviewed

16.2 Exit Criteria

16.2.1 Integration testing

 100% integration test must be executed
 Pass rate: 95%
 All bugs are found that must repaired and retest must have completed.
 Don’t have bugs with Severity1, 2
 Issues list and outstanding bugs list

16.2.2 System testing

 100% System test cases must be executed.

 Pass rate: 95%
 Don’t have bugs with Severity1, 2
 Issues list and outstanding bugs list
16.2.3 User acceptance test (optional)

 100% User Acceptance test cases must be executed and passed if customer approves that
the HRM software meets their requirement.
 If some test cases failed, must have a report of issues that software product need to be
changed to fix the problems following customer’s expectation.

17.2 Defined Defect Life Cycle

In software development process, the defect has a life cycle. The defect should go through the life
cycle to be closed. A specific life cycle ensures that the process is standardized. The defect attains
different states in the life cycle.
The life cycle of the defect can be shown diagrammatically as follows:

17.2 Defect Life Cycle Description

The testers or test group will report the bug to the change control board and Project manager.
Statuses include:
 New
 Accepted
 Invalid or Duplicate
 Won’t Fix
 Started
 Fixed
  Verified
 Done or Won’t Fix

17.3Guidelines On Deciding the Severity of Bug

Indicate the impact each defect has on testing efforts or users and administrators of the application
under test. This information is used by developers and management as the basis for assigning
priority of work on defects.
A sample guideline for assignment of Priority Levels during the product test phase includes:

 Critical
 High
 Medium
 Low

18. Appendix Definition

Table 6: describing test case priority

Priority Description
1 Test case is very important and cannot fail. Bug must be fixed if test case fails.
2 Test case is not important and can be executed or not base on test schedule.
3 Test case is not important and do not need to test. However, when executing
this test case, it will help to improve quality of software.

Table7: Bug Description

Status Description
New when the defect is posted for the first time,
Tester approves that the bug is
new and change the status of defect as
“New”.
Tester will collect the number of new defect
every week.
After the defect is report, we have a special
team for analysis the impact and evaluate the
 benefit of benefit or change if we fix this
defect.

Accepted If the defect is real and impact on the project,

the defect status will be change to “Accepted”
Once the defect is change to “Approved”, lead
of testers assign the defect to corresponding
developer or developer team.

Invalid or Duplicate Whenever the developers receive the defect

and they do not approve that,
it really is the defect and has the reason to
believe that The status will be
changed to "Invalid or Duplicate”

Won’t fix We also have a special team to check all the

opened defects and decide or find the defect
that is not real defect. The status will be
changed to "Won’t Fix"

Started The developer start to fix the defect.

Fixed After he defect is assigned to developers,
developers start to resolve the defect with
provided solution from QA team. After the
defect is resolved by developers, the status of
defect will be changed to “Fixed”

verified After the developer fix the defect the tester will
verify to ensure that the defects are fixed
correctly.
Done After the developer fix the defect. The tester
will verify to ensure that the defects are fixed
correctly; the status will be changed to "Done”
Table 8: Bug Priority Level

Status Description
Critical An item that prevents further testing of
the product or function under test can be
classified as Critical Bug.
No workaround is possible for such
bugs Examples of this include a
missing menu option or security
permission required to access a function
under test.
High A defect that does not function as
expected / designed or cause other
functionality to fail to meet
requirements can be classified as Major
Bug. Examples of this include
inaccurate calculations; the wrong
field being updated, etc.
Medium The defects which do not conform to
standards and conventions can be
classified as Medium Bugs. Easy
workarounds exists to achieve
functionality objectives. Examples
include matching visual and text links
which lead to different end points.
Low Cosmetic defects which does not affect
the functionality of the system can be
classified as Minor Bugs.
19. Test case
Project Human Resource Management System For IT Center of Balkh University
Name
Reference Project Functional Requirement Specification
Document
Test case ID Test Objective Precondition Steps: Test Data Expected result Post-condition

TC_MI_01 "Successful 1. A valid ESS- 1. In the login 1.“A valid The user is logged For first time
Employee login User account to Panel, enter username” in successfully. users personal
to ITCB HRMS login to be the username There is only one information is
portal available expected result for displayed.
2. Enter the Enter the the entire test case.
Check the 2. Orange HRM Password for actual data However, that does Note: This info
screenshot to get 3.0 site is the ESS-User in your not have to be so. If is only
an idea of what launched on a account in the real time it makes sense that additional. Just
screen we are compatible password situation. for every step, you as a pointer to
testing browser field want to write the the tester
result of exactly
3. Click 2."A valid what happens with
""Login"" Password" it, please free to
button" have an expected
result for each test
step.

TC_MI_02 Error message on 1. A ESS-User 1. In the login 1.” A valid An Error message As you can see,
unsuccessful name to login to Panel, enter username” is displayed and the post condition
Employee login be available the username user is not logged in can be left
to ITCB HRMS to the ITCB HRMS empty when
portal portal. ""<Exact there is nothing
Error Message>" else to add

In the test case, it is

2. ITCB HRMS 2. Enter the 2.”A not enough when
site is launched Password for invalid we say, 'that an
on a compatible the ESS-User Password” error is displayed'-
browser account in the in addition to that,
password we will have to
field mention the exact
error message that
is going to be
encountered by the
3.Click user- This
"Login" information can
button generally be found
in FRD(SRS).
 If not, look in the
technical design
document or Use
cases.- Check the
test next case,
where we write
Expected result,
step wise.

TC_MI_MIM First time user 1. A ESS-User 1. In the login "A valid The user is logged These fields
_01 login- name to login to Panel, enter Password" in successfully and are grayed out
information be available for the username the personal and cannot be
display check a first time user information page is modified
of the site. displayed

2. ITCB HRMS 2. Enter the ” A valid Check if the

site is launched Password for Password” following fields are
on a compatible the ESS-User disabled for entry
browser account in the in Personal Details:
password
field ● Employee ID
● Email
3. Click ● Password
""Login"" ● age
button ●phone number
●salary
● Fist name
4. Check the ● Last name
fields on the ●Father Name
"Personal ● Date of Birth
information ● Gender
Page" ● Admission Date
● Related Section
● position
●Address
●Photo

TC_MI_MIM Personal details- 1. ITCB HRMS 1. Check the The users

_02 modification site is launched fields on the information is
with valid on a compatible "Personal displayed
values- "First browser and a information
Name” ESS User Page"
account holder
is logged in to
the site
 (The 2. Change the “A valid
precondition field, "First new value
can be used to Name" with for the
avoid repeating enter a valid first name The first name field
steps 1, 2 and 3 new name in filed” needs to now show
as in the this field the new value
previous test entered
case. However,
if you are more 3.Click on
comfortable “Save”
having the login
steps as well,
that is ok too.)

* This is how all the other field's modification can be tested. Be sure to include negative test cases, where an invalid data can
be entered as the new value and an error message is observed

TC_MI_P_01 Check the upload 1. ITCB HRMS 1.Click on the Name of The "Photograph This page will
of a JPG format site is launched photograph the image screen" will be contain options
image on a compatible displayed at Location- displayed to select and
browser and a the top left path on the upload
ESS User corner of the machine pictures.
account holder page
is logged in to
the site

2. A valid image 2. Click on You will be able to

to upload that is "Choose a browse your local
JPG in format file" button machine for images
and less than 1
MB in size is
available on the
local machine a
location

3. Choose a The file name is

image file of selected in the
type "JPG" "Choose a file" box
that is less
than 1 MB

4. Click on The file gets It takes 2-5

upload uploaded and the depending on
older image is the size of the
replaced image for this
change to
 complete and
the page to
refresh with
the new image.

TC_MI_P_02 Check the upload 1. ITCB HRMS 1.Click on the Name of The "Photograph This
of a PNG format site is launched photograph the image screen" will be page will
image on a compatible displayed at Location- displayed contain options
browser and a the top left path on the to select and
ESS User corner of the machine upload
account holder page pictures.
is logged in to
the site

2. A valid image 2. Click on You will be able to

to upload that is "Choose a browse your local
PNG in format file" button machine for images
and less than 1
MB in size is
available on the It takes 2-5
local machine a 3. Choose a The file name is depending on
location image file of selected in the the size of the
type "PNG" "Choose a file" box image for this
that is less change to
than 1 MB The file gets complete and
uploaded and the the page to
4. Click on older image is refresh with
upload replaced the new image.

*include another similar test cases for all the valid formats

TC_MI_P_03 Check the upload 1. ITCB HRMS 1.Click on the Name of The "Photograph Choose the doc
of a invalid site is launched photograph the image screen" will be file that is less
format of the on a compatible displayed at Location- displayed than 1 This
picture (may be a browser and a the top left path on the page will
.doc file) ESS User corner of the machine contain options
that is less than 1 account holder page to select and
MB is logged in to upload
the site pictures.

2. A doc file is 2. Click on You will be able to

available that is "Choose a browse your local
less than 1 MB file" button machine for images

3. Choose the The file name is

doc file that is selected in the
"Choose a file" box
 less than 1
MB

An error message is This page will

4. Click on displayed that the contain options
upload format is not to select and
supported- <The upload
exact error pictures.
message>

TC_MI_P_04 Check the upload 1. ITCB HRMS Click on the Name of The "Photograph
of a valid format site is launched photograph the image screen" will be
by over the size on a compatible displayed at Location- displayed
of 1 MB browser and a the top left path on the
ESS User corner of the machine
account holder page
is logged in to
the site

2. A JPG file is Click on You will be able to

available that is "Choose a browse your local
more than 1 MB file" button machine for images

Choose the The file name is

JPG file that selected in the
is more than 1 "Choose a file" box
MB
An error message is
displayed that the
Click on size is over <The
upload exact error
message>
20. Test Report
20.1 Database Table Report Testing

Login Table

Add Employee Details

Add Training Report
Login Screen Testing Report
 MAIN SCREEN
View employee details

View employee skill report

View employee replacement report

View employee compensation report

View employee compensation report

Employee logout page

21. Testing Report
21.1TESTING PHASE
The completion of a system is achieved only after it has been thoroughly tested.
Though this gives a feel the project is completed, there cannot be any project without
going through this stage. Hence in this stage it is decided whether the project can
undergo the real time environment execution without any break downs, therefore a
package can be rejected even at this stage.

21.2 SYSTEM TESTING

Testing is a set of activities that can be planned in advance and conducted
systematically. The proposed system is tested in parallel with the software that consists
of its own phases of analysis, implementation, testing and maintenance. Following are
the tests conducted on the system.

21.3 UNIT TESTING

During the implementation of the system each module of the system was tested
separately to uncover errors within its boundaries. User interface was used as a guide in
the process.

21.4 MODULE TESTING

A module is composed of various programs related to that module. Module testing is
done to check the module functionality and interaction between units within a module.

It checks the functionality of each program with relation to other programs within the
same module. It then tests the overall functionality of each module

21.5 INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure
while conducting tests to uncover errors associated with interfacing. The objective is to
take unit-tested module and build a program structure that has been dictated by design.
21.6 ACCEPTANCE TESTING

The software has been tested with the realistic data given by the client and produced
fruitful results. The client satisfying all the requirements specified by them has also
developed the software within the time limitation specified. A demonstration has been
given to the client and the end-user giving all the operational features.

21.7 IMPLEMENTATION PHASE

The implementation is the final and important phase. It involves User training, system
testing and successful running of the developed system. The users test the developed
system when changes are made according to the needs. The testing phase involves the
testing of the developed system using various kinds of data. An elaborate testing of
data is prepared and system is tested using the tests data.

Implementation is the stage where theoretical design turned into a working system.
Implementation is planed carefully to propose system to avoid unanticipated problems.
Many preparations involved before and during the implementation of proposed system.
The system needed to be plugged in to the organization’s network then it could be
accessed from anywhere, after a user logins into the portal. The tasks that had to be
done to implement the system were to create the database tables in the organization
database domain. Then the administrator was granted his role so that the system could
be accessed

The next phase in the implementation was to educate the system. A demonstration of
all the functions that can be carried out by the system was given to examination
department person, who will make extensive use of the system.

22. What Is Selenium?

Selenium is an open source tool which is used for automating the tests carried out on web browsers
(Web applications are tested using any web browser).

Wait, before you get carried away, let me re-iterate that, only testing of web applications is possible
with Selenium. We can neither test any desktop (software) application nor test any mobile
application using Selenium.

There are many tools for testing software and mobile applications like: IBM’s RFT, HP’s QPT,
Appium and many more.
Selenium is open-source, there is no licensing cost involved, which is a major advantage over other
testing tools. Other reasons behind Selenium’s ever growing popularity are:

 Test scripts can be written in any of these programming languages

:Java, Python, C#, PHP, Ruby, Perl & .Net

 Tests can be carried out in any of these OS: Windows, Mac or Linux

 Tests can be carried out using any browser: Mozilla Firefox, Internet Explorer, Google
Chrome, Safari or Opera

 It can be integrated with tools such as Test NG & JUnit for managing test cases and
generating reports
 It can be integrated with Maven, Jenkins & Docker to achieve Continuous Testing

Selenium has many advantages which are enlisted below and because of these benefits we
choose selenium for testing the Human Resource Management System for IT Center of
Balkh University that we build.

1. Open-Source:

As mentioned earlier, the biggest strength of Selenium is that it is a freeware and a portable tool.
It has no upfront direct costs involved. The tool can be freely downloaded and the support for it
is freely available, as it is community-based.
 2. Supports languages:

Selenium supports a range of languages, including Java, Perl, Python, C#, Ruby, Groovy, Java
Script, etc. It has its own script, but it doesn’t limit it to that language. It can work with various
languages and whatever the developers/testers are comfortable with.

3. Supports Operating Systems:

Selenium can operate and support across multiple Operating Systems (OS) like Windows, Mac,
Linux, UNIX, etc. With Selenium Suite of solutions, a tailored testing suite can be created over
any platform and then executed on another one. For instance, you can create test cases using
Windows OS and run it with ease on a Linux based system.

4. Support across browsers:

Selenium provides support across multiple browsers, namely, Internet Explorer, Chrome,
Firefox, Opera, Safari, etc. This becomes highly resourceful while executing tests and testing it
across various browsers simultaneously.

The browsers supported by the Selenium packages are:

 Selenium IDE can be used with Firefox as a plug-in

 Selenium RC and Web driver supports diverse browsers such as Internet Explorer

5. Support for programming language and framework

Selenium integrates with programming languages and various frameworks. For instance, it can
integrate with ANT or Maven type of framework for source code compilation. Further, it can
integrate with Test NG testing framework for testing applications and reporting purposes. It can
integrate with Jenkins or Hudson for Continuous Integration (CI) and can even integrate with
other Open-Source tools to supports other features.

6. Tests across devices

Selenium Test Automation can be implemented for Mobile web application automation on
Android, IPhone, and Blackberry. This can help in generating necessary results and address
issues on a continuous basis.
 7. Constant updates

Selenium support is community based and an active community support enable constant updates
and upgrades. These upgrades are readily available and do not require specific training. This
makes Selenium resourceful and cost-effective as well.

8. Loaded Selenium Suits

Selenium is not just a singular tool or utility, it a loaded package of various testing tools and so is
referred to as a Suite. Each tool is designed to cater to different testing needs and requirements of
test environments.

Additionally, Selenium comes with capabilities to support Selenium IDE, Selenium Grid, and
Selenium Remote Control (RC).

9. Ease of implementation

Selenium offers a user-friendly interface that helps create and execute tests easily and
effectively. Its Open-Source features help users to script their own extensions that makes them
easy to develop customized actions and even manipulate at an advanced level.

Tests run directly across browsers and the users can watch while the tests are being executed.
Additionally, Selenium’s reporting capabilities are one of the reasons for choosing it, as it allows
testers to extract the results and take follow-up actions.

10. Reusability and Add-ons

Selenium Test Automation Framework uses scripts that can be tested directly across multiple
browsers. Concurrently, it is possible to execute multiple tests with Selenium, as it covers almost
all aspects of functional testing by implementing add-on tools that broaden the scope of testing.

23. Future work

While this paper has demonstrated the design and implementation of HRMS, many opportunities
for extending the scope of this paper remain. This section presents some of these directions.

 It will be improved with analyzing more elements of websites and optimizing them more
effectively.
 It will be able to collect the user’s most searched keywords and suggest them to web
developers.
24. Conclusion
The project of Human Resource Management System is the requirement of almost all organization
to manage the men power in proper and efficient manner.

We were able to put in our efforts to make the project a success. The environment provided by the
company enabled us to work in a positive manner.

Reference
[1].Hartel, C.E.J., Fujimoto, Y., Strybosch, V.E., and Fitzpatrick, K. (2017), Human Resource
Management: Transforming Theory into Innovative Practice, Frenchs Forest, NSW:Pearson
Education Australia.

[2].Hall,M.L.,Hall,C.L.,and Andrade,L.,and Drake,B.(2009).Strategic human resource

management: The evolution of the field.Human Resource Management Journal,19 ,64–85.

[3].Harris,L.(2007). The changing nature of the HR function in UK local government and its role
as “employee champion” .Employee Relations Journal,30(1) , 34-47.

[4].Katou,A.,and Budhwar.P.(2015). Causal relationship between HRM policies and

organisational performance: Evidence from the Greek manufacturing sector European
Management Journal, 28, 25– 39.

[5].Keegan,A.,Huemann,M.,andTurner,J.R.,(2011) Beyond the line: exploring the HRM

responsibilities of line managers,project managers and the HRM department in four project-
oriented companies in the Netherlands, Austria,the UK and the USA. The International Journal of
Human Resource Management, 1, 1-20.

[6].http://www.sagepub.com/upm-data/25450_Ch1.pdf
[7].http://www.siop.org/tip/backissues/tipjan98/may.aspx

[8]. http://srmo.sagepub.com/view/the-human-resources-program-evaluation-handbook/n23.xml
[9]. B. Pattanayak, Human Resource Management(PHI Learning Private Limited,2009).

[10]. L.M. Prasad, Human Resource Management (Sultan Chand & Sons: Educational Publishers,
2016).

[11]. H John Bernardin, Human Resource Management (Tata McGraw-Hill Publishing Company
Limited, 2017) [16]. P.C. Tripathi, Human Resource Development (Sultan Chand & Sons:
Educational Publishers, 2015)

[12]. V S P Rao, Human resource Management (Excel Books, Second Edition, 2016) [18]. Mohan
Thite, Michael J. Kavanagh, Evolution of Human Resource Management and Human Resource
Information Systems