System Test Plan

Table of Contents

1. Introduction
2. Objectives
3. Scope
4. Test Strategy
5. Test Plan
   • Test Environment
   • Test Criteria
   • Test Deliverables
6. Test Schedule
7. Resources
8. Roles and Responsibilities
9. Defect Management
10. Risk Management
11. Communication Plan
12. Approval

Introduction

This document outlines the System Test Plan for the project "Transact New Implementation II". The objective of this project is to install Temenos' Transact core banking product with our legacy mainframe banking system. The legacy system, which is over 30 years old and Cobol-based, holds account information for Test Republic Bank's 100,000 retail checking and savings accounts. The transition to the cloud-based SaaS solution must be seamless, ensuring no disruption to client access. The project also includes specific requirements such as purging accounts with $100 or less, integrating with Paymentus and LendingPad, and ensuring the UX uses only different shades of blue.

Objectives

The objectives of the system testing are:

• Ensure Temenos' Transact core banking product integrates seamlessly with the legacy mainframe system.
• Validate the migration of accounts without disrupting client access.
• Verify the purging and refund process for accounts with $100 or less.
• Confirm the integration with third-party software (Paymentus and LendingPad).
• Ensure the UX meets the specified color requirements.
• Automate testing using Selenium.

Scope

The scope of the system testing includes:

• Migrating account information from the legacy mainframe system to Temenos' Transact.
• Testing the functionality of Temenos' Transact core banking product.
• Verifying the integration with Paymentus and LendingPad.
• Checking the purging and refund process for accounts with $100 or less.
• Ensuring the UX adheres to the color scheme requirement.
• Automating the testing process using Selenium.

Test Strategy

The test strategy includes the following types of testing:

• Functional Testing: To verify the functionality of Temenos' Transact and its integration with the legacy system.
• Performance Testing: To ensure the system can handle the load of 100,000 accounts without any performance degradation.
• Security Testing: To confirm that the system is secure and meets all regulatory requirements.
• Integration Testing: To verify the seamless integration with Paymentus and LendingPad.
• UX Testing: To ensure the user interface adheres to the specified color scheme.
• Automation Testing: To automate the testing process using Selenium.

Test Plan

Test Environment

The test environment will include:

• Hardware: Servers configured to host Temenos' Transact and the legacy mainframe system.
• Software: Temenos' Transact, Paymentus, LendingPad, Selenium, and necessary testing tools.
• Network Configurations: Proper network setup to simulate the live environment.

Test Criteria

• Entry Criteria:

  • Test environment is set up and configured.
  • Test data is prepared and available.
  • Test cases and scripts are reviewed and approved.

• Exit Criteria:

  • All test cases are executed.
  • All critical defects are resolved.
  • Test summary report is reviewed and approved.

Test Deliverables

• Test Plan
• Test Cases
• Test Scripts
• Test Data
• Test Reports
• Defect Logs
• Test Summary Report

Test Schedule

• Test Planning: 05/01/2025 - 05/15/2025
• Test Case Development: 05/16/2025 - 06/15/2025
• Test Environment Setup: 06/16/2025 - 06/30/2025
• Test Execution: 07/01/2025 - 12/15/2025
• Defect Resolution: 07/01/2025 - 12/31/2025
• Test Closure: 12/16/2025 - 12/31/2025

Resources

• Personnel: Test Manager, Test Lead, Test Engineers, Developers, Business Analyst
• Tools: Selenium, Test Management Tool, Defect Tracking Tool
• Other Materials: Test Data, Documentation

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 managed through a defect tracking tool. The process includes:

• Recording defects with detailed information.
• Assigning defects to the appropriate team members.
• Tracking the status of defects until resolution.
• Retesting resolved defects.

Risk Management

Potential risks and mitigation strategies:

• Risk: Data migration issues.
  • Mitigation: Perform thorough data validation and reconciliation.
• Risk: Integration failures with third-party software.
  • Mitigation: Conduct extensive integration testing.
• Risk: Performance degradation.
  • Mitigation: Perform load and performance testing.
• Risk: UX non-compliance.
  • Mitigation: Perform UX testing and reviews.

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: Mike Meier
• Email: mikemeier@mad-tech.ai
• Date: 04/28/2025
• Approved by: [Approver's Name]
• Date: [Approval Date]