Testing Process

The QA team in Xponse consists of Computer Post-Graduates, B.Tech, BCA and MCA professionals who are dedicated, determined and responsible individuals and have successfully tested complex softwares for various clients.

Xponse Software Testing Process

The Testing process in Xponse is highly detailed and comprises 4 painstaking steps:

  1. Test Plan
  2. Test Strategy
  3. Test Case
  4. Test Execution & Automated Defect Tracking
  5. Test Metrics

Test Plan involves:

  • Product Overview
  • Test Plan Objective
  • Relevant Related Document
  • Test Organization
  • Test Strategy (Given as a separate document)
  • Testing Environment
  • Functions to Test
  • Test Schedule
  • Review
  • Change Request
  • Defect Reporting
  • Resources & Responsibilities
  • Deliverables
  • Suspension & Exit Criteria
  • Resumption Criteria
  • Risks
  • Tools
  • Personal Pre-Training Needs
  • Open Issues
  • Out of Scope
  • Approvals

Test Strategy Document consists of:

  • Introduction
  • Purpose and structure of this document
  • Glossary
  • Project Overview
  • Project Quality Management Overview
  • Quality Management Deliverables & Owners
  • Supporting Project Activities & Owners
  • Risks, Assumptions and Out of scope
  • Unit Testing
    • Definitions & Objectives
    • Scope
    • Deliverables
    • Entry Criteria
    • Exit Criteria
    • Test Environment
    • Test Data
  • Integration Testing
    • Definitions & Objectives
    • Scope
    • Deliverables
    • Entry Criteria
    • Exit Criteria
    • Test Environment
    • Test Data
  • Functional Testing
    • Deliverables
    • Entry Criteria
    • Exit Criteria
    • Test Environment
    • Test Data
  • Smoke Testing
  • Regression Testing
  • External Interface Testing
  • Performance Testing
  • Recovery & Failover Testing

Test Case consists of three sections

  • Test Scenario
    • Scenario Number
    • Scenario
    • Scenario Description
    • Reference Document
    • Requirement Id
  • Traceability
    • Test Requirement
    • Test Cases
  • Test Cases
    • Test Case Id
    • Test Case
    • Steps
    • Test Data
    • Expected Result
    • Actual Result
    • Pass/Fail
    • Bug Id
    • Remarks

Test Execution consists of the following steps:

  1. Executing Test Cases
  2. Find the Bug.
  3. Post the Bug with proper information with the reference of test cases id also . Bug status is changed with an icon. Such as Read bug, Progress status with different color scheme as well as different picture scheme.
  4. Review the bug by the QA manager / PM / Team leader to set the priority level.
  5. Assign the bug to the proper developer by the PM / Team leader / QA manager
  6. Fix the bug
  7. Retest the bug and carry on with the cycle until bug is closed.

Currently the following Test Metrics are made in Xponse. But it varies with the requirement of the client.

  • Bugs per Man Month
    Calculated with the Formula: (No. of Bugs in the Project) / Effort In Man-month

  • Mean Time to Repair
    Mean Time to Repair = Sum (Date of Resolving the Error- Date of Reporting Error + 1)/ Total Defects

  • Defect Density
    Defect Density = Sum (No. of Defects of Severity 'High' * 2+ No. of defects of Severity "Medium"*1 + No. of Defects of severity "Low"*0.2)/Size

  • Effort spent on Defect Prevention Activity
    Effort Spent on Defect Prevention Activity = Effort Spent on Defect Prevention Activity (in Hours)/Total Effort Spent (In Hours)

CLOSE