1.

AIM/OBJECTIVE:
- The Orange HRM Demo website is a human resource management system
(HRMS) that includes HR administrations and other common features such as
time-off management, recruitment and performance management.
2. SCOPE OF TESTING:
a. Within the scope of testing: Admin/User management, PIM, Leave
management, Time/Timesheet, Recruitment, Performanace/Manage reviews,
Buzz.
b. Out of scope: Maintenance section.
3. TEST STRATEGY
a. Levels of Testing: System Testing, Acceptance Testing
b. Types of Testing: Functional testing
 Smoke Testing
 Regression Testing
c. Test Design Techniques: Black Box Testing Techniques
 ECP (Equvalence Class Partitioning)
 BVA (Boundary Value Analysis)
 Decision Table
d. Terminology Used:
 Add User: Admin users can assign a specific work role to an employee.
Go to Admin-> User Management-> Users.
 Add an Employee: Admin users can add employees to the system and
create login details (username and password). Go to PIM-> Employee
List.
 Terminate Employee: Allow admin users can terminate an employee due
to: Contract Not Renewed, Deceased, Resigned, Retired. Go to PIM->
Employee List.
 Assign Leave: Allow admin users to assign a day-off for an employee. To
assign leave, select Leave>Assign Leave.
 Leave List: Allow admin users to see all the leave request. Admin can
cancel/approve/reject an employee’s request. To see Leave List, go to
Leave>Leave List.
 Employee Timesheets: A timesheet is a record of the amount of time an
employee has spent, on a particular job, project, or specific client.
Employees have the ability to submit timesheets and the admin or the
supervisors are able to review them accordingly. Select Time >
Timesheets > Employee Timesheets to see this features.
 PIM: Personal information management.

e. Configuration Management Tool: Github

f. Area Planner for Automation: Admin/User management module, PIM
module, Leave module.
g. List of Automation tools: Java Selenium.

4. ENTRY AND EXIT CRITERIA:

In order to start testing:
1. Have approved test plan.
2. Test environment is ready.
3. Test data is ready.
4. Application documents is ready.
In order to stop testing:
1. All requirements have been met.
2. All testing has been completed.
3. All defects have been resolved.
4. All documentation has been completed.
5. The project has been approved for release.
5. TEST DELIVERABLES:
- Test Plan
- Test Scenario
- Test Case
- Defect
6. ROLES AND RESPONSIBILITIES:
Roles Responsibilities
Test Lead 1. Prepare the test plan,
2. Allocate the task to the testing team
 3. Co-ordinate with the testing team to complete the task
4. Represent the team work to the stack holders
Automation 1. Prepare automation test plan
Test Lead 2. Recognize the areas need to be automated
3. Recognize the level of automation in that area
4. Selection of automation tools
Performance 1. Prepare the performance plan.
Test Lead 2. Recognize the tool used for performance testing
3. Educate the team about the user performance testing tool.
Test Engineer 1. Prepare the test cases
2. Prepare the defect report
3. Complete the task aligned by the test lead
Business 1. Prepare the requirements document
Analyst 2. Address all the issues related to requirements.
3. Communicate with team w.r.t. updates.
Project 1. Prepare the project plan.
Manager 2. Decide the duration.
3. Represent team work to the stack holders.
4. Address the challenges of the team

7. RISK AND MITIGATION:

What are all the unexpected events in the projects need to be recognized
and addressed early in the project life cycle.
a. Risks and Contingency:
 Risk Impact Mitigation Plan

SCHEDULE  The testing team can

Testing schedule is tight. control the preparation
The testing schedule cannot tasks (in advance) and the
be extended High early communication with
teammate.
 Prioritize testing based on
risk.
RESOURCES  Use automation testing.
Not enough personnel in the  Work on the weekends.
High
testing team

DEFECTS Identify potential risks to a

Defects are found at a late project and then plan for the
stage of the cycle or at a late risk by implementing
cycle; defects discovered strategies to help lessen or
late are most likely be due to halt the risk. By using risk-
High
unclear specifications and based testing.
are time consuming to
resolve.

SCOPE Scope is well defined but the

Scope completely defined changes are in the
Mediu
functionality are not yet
m
finalized or keep on
changing.
New Issues During testing, there is a
Delayed Testing Due To good chance that some
new Issues “new” defects may be
identified and may become
an issue that will take time to
resolve.
There are defects that can be
raised during testing because
of unclear document
specification. These defects
can yield to an issue that will
High
need time to be resolved.
If these issues become
showstoppers, it will greatly
impact on the overall project
schedule.
If new defects are
discovered, the defect
management and issue
management procedures are
in place to immediately
provide a resolution.
 b. Risks and Mitigation: Some of the risks might not be avoided but we
can reduce the impact of the risk. Ex: Requirements are not clear for
the stack holders. We cannot avoid this risk, but we can avoid the
level of impact by completing the known information.
8. SCHEDULE:
Task Duration
Test Plan Preparation 1 week
Test case preparation 2 weeks
Test case Execution 1 week
Defect Reporting Continuous process
Regression Test 1 week
9. TEST ENVIRONMENT:
The Hard-ware and Soft-Ware required for the project will be specified
here. Ex: System Configuration, Server Configuration, Operating System,
Tools etc.
Hardware:
 Processor: i7-9750H, I7 4810MQ
 Ram: 16GB
Software:
 Operating System: windows 10 LTSC 2019, Windows 11 Home
22H2
 Testing browser: Microsoft edge Version 113.0, Google Chrome
Version 113.0A windows environment with Microsoft Edge Version 113,
and with Firefox 27.0, as well as Google Chrome 32.0 and later should be available to
each tester.

10. TEST METRICS:

Different metrics (measuring quality) used for the project will be
specified here. Ex. Test case metric, Defect metric, KLOC metric.

Testing Metric Release 1 Release 2

TOTAL NO OF TESTCASES
NO OF TESTCASES EXECUTED
NO OF TESTCASES NOT EXECUTED
NO OF TESTCASES PASSED
NO OF TESTCASES FAILED
NO OF TESTCASES BLOCKED
% Test cases Executed
% Test cases not Executed
% Test cases Passed
% Test cases Failed
% Test cases Blocked