Dashboard
Documents
Archive
Settings
New Project
New Proposal
New Document
Code Review
Code Documenter

System Test Plan

Table of Contents

  1. Introduction
  2. Objectives
  3. Scope
  4. Test Strategy
  5. Test Plan
  1. Test Schedule
  2. Resources
  3. Roles and Responsibilities
  4. Defect Management
  5. Risk Management
  6. Communication Plan
  7. Approval

Introduction

This System Test Plan outlines the testing approach for the Balance Scorecard Setup project. The primary objective of this project is to align projects monitored by the PMO with the business strategy of the tourism industry organization. This document will provide a structured approach to ensure all aspects of the balance scorecard (financial, customer, internal business process, and innovation and learning perspectives) are thoroughly tested.

Objectives

The objectives of the system testing are to:

  • Validate that the balance scorecard includes and correctly implements the financial, customer, internal business process, and innovation and learning perspectives.
  • Ensure that the goals, measures, and success/failure criteria are correctly defined and implemented.
  • Confirm that the balance scorecard ensures alignment of projects with the strategic goals of the organization.
  • Ensure that the system is user-friendly and meets the needs of the business stakeholders.

Scope

The scope of system testing includes:

  • Financial perspective: Goals, measures, success and failure criteria.
  • Customer perspective: Goals, measures, success and failure criteria.
  • Internal business process perspective: Goals, measures, success and failure criteria.
  • Innovation and learning perspective: Goals, measures, success and failure criteria.
  • Integration of the balanced scorecard with the PMO monitoring system.
  • User interface and usability testing.

Test Strategy

The test strategy includes:

  • Functional Testing: To ensure all features and functionalities are working as expected.
  • Integration Testing: To ensure the balance scorecard integrates well with the PMO monitoring system.
  • Performance Testing: To ensure the system performs well under expected load conditions.
  • Usability Testing: To ensure the system is user-friendly and meets the needs of the business stakeholders.
  • Security Testing: To ensure the system is secure and protects sensitive business information.

Test Plan

Test Environment

The test environment will include:

  • Hardware: Standard office desktops/laptops with minimum configurations as per the system requirements.
  • Software: Windows 10, Microsoft Office Suite, Web Browsers (Chrome, Firefox, Edge), PMO Monitoring Software.
  • Network Configurations: Standard office network with access to necessary servers and databases.

Test Criteria

  • Entry Criteria:

    • Complete and approved requirements documentation.
    • Test environment setup and ready.
    • Test data prepared and available.
    • Test cases reviewed and approved.

  • Exit Criteria:

    • All test cases executed.
    • All critical and high defects resolved.
    • Test summary report prepared and reviewed.
    • Stakeholder approval for test completion.

Test Deliverables

The test deliverables include:

  • Test Plan Document
  • Test Cases
  • Test Scripts
  • Test Data
  • Test Execution Report
  • Defect Log
  • Test Summary Report

Test Schedule

Activity Start Date End Date Responsible
Test Planning 12/01/2024 12/07/2024 Test Manager
Test Case Design 12/08/2024 12/14/2024 Test Engineers
Test Environment Setup 12/08/2024 12/10/2024 IT Support
Test Execution 12/15/2024 12/28/2024 Test Engineers
Defect Fixes and Re-testing 12/29/2024 01/04/2025 Developers, Test Engineers
Test Summary Report 01/05/2025 01/07/2025 Test Manager

Resources

Resource Quantity Description
Test Engineers 3 Responsible for designing and executing test cases.
Test Manager 1 Oversees the testing process and manages resources.
IT Support 2 Responsible for setting up the test environment.
Developer 2 Responsible for fixing defects and providing technical support.
Business Analyst 1 Ensures test cases align with business requirements.

Roles and Responsibilities

Role Responsibility
Test Manager Oversee the testing process, manage resources, and ensure adherence to the test plan
Test Lead Coordinate testing activities and manage the test team
Test Engineer Design and execute test cases, report defects
Developer Fix defects and provide technical support
Business Analyst Ensure test cases align with business requirements

Defect Management

Defects will be recorded, tracked, and resolved using the following process:

  • Defects will be logged in the defect tracking tool (e.g., JIRA, Bugzilla).
  • Each defect will be assigned a severity and priority level.
  • Defects will be assigned to the appropriate developer for resolution.
  • Resolved defects will be re-tested by the test engineer.
  • Defect status will be updated in the tracking tool until closure.

Risk Management

Potential risks and mitigation strategies include:

  • Risk: Delays in test environment setup.
    • Mitigation: Plan and coordinate with IT support well in advance.
  • Risk: Unavailability of key resources.
    • Mitigation: Have backup resources identified and trained.
  • Risk: High number of defects found during testing.
    • Mitigation: Prioritize defect resolution based on severity and impact.

Communication Plan

Communication Type Audience Frequency Medium Owner
Status Report Project Team Weekly Email Test Manager
Defect Review Meeting Key Stakeholders Bi-weekly Meeting Test Lead
Test Summary Report All Stakeholders End of Testing Phase Document Test Manager

Approval

  • Prepared by: Wayne Sheridan
  • Email: wayne.sheridan@gmail.com
  • Date: 12/18/2024
  • Approved by: [Approver's Name]
  • Date: [Approval Date]
Document Link
Balance Scorecard Setup System Test Plan