Test Plan: Created Date
Test Plan: Created Date
Test Plan: Created Date
Created Date :
Contents
Purpose 3
General Project Overview 3
Testing Approach 5
In scope 5
Out of scope 5
Main functionality Under Test 5
Testing strategy 6
Test scenario/Test cases Creation 6
Test execution 6
Defect Log 6
Types of Testing 7
Functional Testing 7
Regression Testing 7
Retesting 7
Team and Roles 8
Test Deliverables 7
Page 2|8
Test Plan
Purpose :
This document provides strategy for testing and tells how testing will be done. It
includes scope, out of scope, entry criteria, exit criteria, testing plan and resource.
This also describes process for testing, bug tacking flow and deliverable. It gives idea
to stakeholders about planning to achieve success in testing. As this is high level
strategy, based on decision and change, this article will be changed.
Features
Administration Module
o The Admin Module provides you with full control of all settings that affect the
action of your OrangeHRM implementation.
o The Admin Module is the central control of the system and setting it up
accurately is important for smooth operation.
o This module consists User Management , Job, Organization , Qualifications ,
Nationalities, Configuration.
Page 3|8
Test Plan
Leave Module
Time-Attendance Module
Performance Module
o This module manages and reviews the performance of all employees where a
company can understand how well an employee is performing in relation to
their strategic goals and objectives.
o This module consists Configure ,Manage reviews ,Employee trackers
Directory Module
o This module return directory based on Name, Job title ,Location.
Page 4|8
Test Plan
Testing Approach :
In scope:
Type of testing to be done
Regression Testing
Retesting
Out of Scope:
Security Testing, Acceptance Testing, Non-functional Testing , Automation Testing
Page 5|8
Test Plan
Testing strategy:
Test scenario/Test cases Creation:
Test scenario/Test cases will be prepared according to functionality.
Test scenario/cases will be managed in Excel tool.
Test execution:
Test execution will be execute after test-case/scenario creation
Functional Testing and Regression testing will be performed.
QA will execute all (Medium, Low) priority test cases during functional testing cycle.
After test-case execution demo will be take place.
Defect Log:
All identified issues/bug/improvement will be logged in Word.
Retesting of bug will be take place.
Page 6|8
Test Plan
Types of Testing:
Functional Testing: In functional testing, Testing based on an analysis of the specification of the
functionality of a component or system Functions are tested by feeding them input and
examining the output. Functional Testing usually describes what the system does.
Regression Testing: Regression testing will be take place after functional testing at the end of
execution. It is considering the testing of a previously tested program following modification
to ensure that defects have not been introduced or uncovered in unchanged areas of the
software, because of the changes made.
Retesting: When a test fails because of the defect then that defect is reported, and a new version
of the software is expected that has had the defect fixed. In this case we need to execute the
test again to confirm that whether the defect got fixed or not.
Page 7|8
Test Plan
Test Deliverables :
Test Strategy/Plan – This document
Defect Management – When defects will be identified ,they will be logged in word.
Page 8|8