Scribd Logo
Upload

Welcome to Scribd!

  • 602 views

    Orange HRM: System Test Plan

    Uploaded by

    victor othugadi
    The document outlines the test plan for Orange HRM, a web-based HR management system. It describes the project overview, test scope, strategy, and environment. Key elements include testing the login, admin, and employee modules, but not the PIM or dashboard. Testing will include functional, load, performance, security, and compatibility tests. The plan defines test entry and exit criteria, risks, staffing, milestones, and deliverables such as test scenarios, cases, and reports.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    Orange HRM: System Test Plan

    Uploaded by

    victor othugadi
    602 views8 pages
    The document outlines the test plan for Orange HRM, a web-based HR management system. It describes the project overview, test scope, strategy, and environment. Key elements include testing the login, admin, and employee modules, but not the PIM or dashboard. Testing will include functional, load, performance, security, and compatibility tests. The plan defines test entry and exit criteria, risks, staffing, milestones, and deliverables such as test scenarios, cases, and reports.

    Original Title

    OrangeHRM Plan

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines the test plan for Orange HRM, a web-based HR management system. It describes the project overview, test scope, strategy, and environment. Key elements include testing the login, admin, and employee modules, but not the PIM or dashboard. Testing will include functional, load, performance, security, and compatibility tests. The plan defines test entry and exit criteria, risks, staffing, milestones, and deliverables such as test scenarios, cases, and reports.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    602 views8 pages

    Orange HRM: System Test Plan

    Uploaded by

    victor othugadi
    The document outlines the test plan for Orange HRM, a web-based HR management system. It describes the project overview, test scope, strategy, and environment. Key elements include testing the login, admin, and employee modules, but not the PIM or dashboard. Testing will include functional, load, performance, security, and compatibility tests. The plan defines test entry and exit criteria, risks, staffing, milestones, and deliverables such as test scenarios, cases, and reports.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 8
    At a glance
    Powered by AI
    The key takeaways are that Orange HRM is a web-based HR software that offers personal, corporate and international employee services. It has three major modules: Admin, Employee and PIM. Testing will include functional, system, load, performance, security, compatibility and regression testing. Test deliverables include the test plan, test scenarios, test cases, defect reports and test summary reports. Major milestones include developing the test plan, scenarios and cases as well as executing the tests and reporting results.

    The major modules of the Orange HRM system are the Admin Module, Employee Module and PIM Module.

    The types of testing that will be performed on the system are functional testing, system testing, load testing, performance testing, security testing, compatibility testing and regression testing.

    Orange HRM

    System Test Plan


    Version 2.0
    1.0 Project Overview

    Orange HRM is a web based Software, offers personal, corporate and International EMP
    Services. This Project comprises of 3 major modules such as 1.Admin Module, 2. EMP
    Module, 3. PIM Module.

    2.0 References

     Orange HRM Project Overview


     Orange HRM Functional Requirement Specifications

    3.0 Scope

    3.1 In scope

     Login Module
     Admin Module
     EMP Module

    3.2 Out Scope

     PIM
     Dashboard

    4.0 Test Strategy

    4.1 Testing Types

     Functional System Test


     Load Test
     Performance Test
     Security Test
     Compatibility Test

    4.2 Entry criteria (When to start testing)

    1. 100% Unit Testing and Integration Testing should be successful


    2. All Testcases should be Reviewed and Baselined.

    4.3 Suspension and Resumption Criteria

    Suspension Criteria Resumption Criteria

    1. When Show Stopper Defects If patch is releases against build


    Found. Rejection

    2. When there is a Change Request Once CR is implemented


    from the client.

    4.4 Exit Criteria (When to stop testing)

    1. When all Test cases executed successfully and passed.


    2. When all P0 and P1 defects are resolved and closed.

    4.5 Communication plan

    # Resource Name Responsible Email Contact No


    1 Ramakrishna Project Manager [email protected] 1111111
    2 Antony G Test Lead [email protected] 222222
    3 Srihari TestLead [email protected] 33333

    4.6 Status reporting

    Weekly Test status reporting model


    4.7 Test Execution

    Test Execution Flow

    Building the Smoke Test Functionality


    System Testing

    Regression
    Testing

    UI Testing Performance QA Delivery


    Testing to
    Orange HRM

    Gate A Gate B Gate C Gate D

    Quality Gates

    Quality Gate Description


    Gate A Build Verification Test – This is to ensure that the QA
    Release contains all the necessary source files to build the
    Orange HRM components and application.
    Gate B Smoke/Acceptance Test – The smoke test is designed to
    ensure that each built component is in a state where QA
    testing on the Orange HRM Insight application can be
    carried out effectively.
    Gate C Stability of the application – To ensure that the functional
    testing results does not have any high or critical defects
    prior to begin the performance testing.
    Gate D Customer Release Criteria – This is defined based on the
    Orange HRM management acceptance criteria. -TBD
    4.8 Defect Tracking

    4.8.1 Priority and Severity guidelines

    Severity Guidelines

    The Severity indicates the impact of the bug. Severity is decided by QA Manager or an individual
    or a group appointed by him/her.

    Severity Classification

    Very High
    High
    Medium
    Low

    Priority guidelines

    The Priority Scale indicates the Urgency to fix a fault. Priority is decided by Project Manager or an
    individual or a group appointed by him/her.

    Priority Classification

    Very High / P0
    High /P1
    Medium /P2
    Low /P3

    4.8.2 Remark Status

    Following are the different status of Defects in Bug tracking Tool

    Status Description
    NEW A new fault identified
    OPEN NEW defect has been accepted into the defect tracking
    system
    FIXED Defect is resolved
    CLOSED Re-Tested and defect is resolved in modified build.

    RE-OPEN Re-Tested and again same defect is present in


    modified build
    REJECTED Not a defect. Works as designed. An Invalid Defect.
    HOLD Defect is not clear
    DIFERRED Defect is postponed or considered for enhancements
    DUPLICATE Defect is already posted
    5.0 Test Environment
    The test environment outlined in this section is necessary for successful execution of test cases

    OS: Linux or Windows 2000/XP, Unix

    Web Server: Apache or IIS


    Database: SQL Server 2005/2008

    Application: Orange HRM

    Software and Hardware

    Computer System Software Requirements Hardware Configuration


    Application/ Web Server  X486 (or equivalent) with 128MB  Intel Pentium IV
    RAM or better  1 GB RAM
     Apache or IIS web server  30 GB HDD
     SQL Server 2005/2008

    Tools
    Following table lists the tools used by QA team:

    No. Purpose Tool


    1 Configuration management VSS
    2 Defect management QC
    3 Test automation QTP 10.0
    4 Performance testing Load Runner 9.5

    Test Data Requirements

    Test data needed to test the Orange HRM Product will be identified and created by QA Team.
    QA Team is responsible for creating test data in the system. Test Data created by QA Team will
    be sufficient to execute all Test case scenarios.

    6.0 Test Deliverables

     Test plan
     Test Scenarios,
     Test cases
     Defect Reports
     Test Summary Reports
    7.0 Staffing plan

    Name No of persons Responsibility

    Test Lead 2 Planning & Controlling QA activities


    Test Team 18 Executing planned QA Activities
    Members

    8.0 Risks & Contingences

    Risk Likelihood Impact Mitigation


    Application not accessible or Low High Perform an environment
    not responding properly sanity check before starting
    during test execution due to the formal testing
    environmental issue. Obtain Mobile numbers of
    IT team members to
    escalate P1 environment
    issues.
    Test team does not have Low High Organize extensive
    adequate knowledge of the knowledge transfer sessions
    application with offshore team
    Development team having Low High QA team will provide
    less knowledge of Quality clarifications to the
    Center. Development team.
    Presence of large number of Low High Daily defect meeting will be
    blocking Defect‘s during test utilized to prioritize defects
    execution, this would QA co-ordination will work
    prevent or delay testing. closely with the IT team
    lead to provide
    Changes to requirements Medium Medium All new Requirements that
    arise are initiated through
    Change Control process

    9.0 Mile stones

    Mile Task Effort Stat Date End Date Deliverables

    Test Plan 3 Hrs 26-02-2013 26-02-2013 Test plan Approval


    Test Scenarios 6 Hrs 28-02-2013 02-032013 Test Scenario Document
    Design
    Test Cases 15 Hrs 04-03-2013 08-03-2013 Test design document.
    Design
    Test case 6 Hrs 09-03-2013 11-03-2013 Test Pass/Fail
    Execution
    Test Report 3 Hrs 12-03-03 12-03-2013 Test Results Summary

    10.0 Approvals

    Project Manager

    You might also like