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 provides a comprehensive System Test Plan for the implementation of Temenos' Transact core banking product at Test Republic Bank. The purpose of this plan is to ensure the seamless transition from the legacy Cobol-based mainframe system to the cloud-based SaaS solution provided by Temenos without disrupting client access to their accounts.

Objectives

The objectives of the system testing are to:

• Verify the successful migration of all account information from the legacy mainframe system to Temenos' Transact.
• Ensure that all functionalities of Temenos' Transact are operational and meet business requirements.
• Validate the integration with third-party systems, including Paymentus and LendingPad.
• Ensure that accounts with $100 or less are purged and closed, with owners refunded by check.
• Confirm that the UX adheres to the requirement of using only different shades of blue.
• Achieve a smooth go-live on New Year's Eve, 2025, with no impact on client access to their accounts.

Scope

The scope of the system testing includes:

• Migration of 100,000 retail checking and savings accounts, and other account types (CDs, Money Market accounts, mortgages, credit cards, car loans, and personal loans) to Temenos' Transact.
• Functional testing of all features and functionalities of Temenos' Transact.
• Integration testing with Paymentus and LendingPad.
• Validation of automated testing scripts using Selenium.
• UX testing to ensure compliance with the color scheme requirement.

Test Strategy

The overall test strategy will include:

• Functional Testing
• Integration Testing
• Performance Testing
• Security Testing
• User Acceptance Testing (UAT)
• Automated Testing using Selenium

Test Plan

Test Environment

The testing environment will include:

• Hardware: Cloud-based servers for Temenos' Transact
• Software: Temenos' Transact core banking product, Paymentus, LendingPad, Selenium for automated testing
• Network Configurations: Secure connections between Temenos' Transact and third-party systems

Test Criteria

• Entry Criteria:
  • Completion of data migration scripts
  • Availability of testing environment
  • Test cases and scripts ready for execution
• Exit Criteria:
  • All test cases executed with no critical defects
  • Successful completion of UAT
  • Approval from key stakeholders

Test Deliverables

• Test Cases
• Test Scripts (Selenium)
• Test Data
• Test Reports
• Defect Logs
• UAT Sign-off

Test Schedule

• Test Planning: 05/01/2025 - 05/15/2025
• Test Case Development: 05/16/2025 - 06/15/2025
• Test Execution: 06/16/2025 - 12/15/2025
• UAT: 12/16/2025 - 12/22/2025
• Go-Live Preparation: 12/23/2025 - 12/30/2025
• Go-Live: 12/31/2025

Resources

• Personnel: Test Manager, Test Lead, Test Engineers, Developers, Business Analyst
• Tools: Selenium, Test Management Tools, Defect Tracking Tools

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
• Prioritizing and assigning defects
• Tracking defect status
• Retesting and closing defects

Risk Management

Potential risks and mitigation strategies:

• Data Migration Issues: Conduct thorough data validation and reconciliation
• Integration Failures: Perform extensive integration testing with Paymentus and LendingPad
• Performance Bottlenecks: Conduct performance testing under peak load conditions
• UX Non-Compliance: Regular UX reviews and adherence to design guidelines

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/29/2025

Approved by: [Approver's Name]
Date: [Approval Date]