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

The purpose of this document is to outline the System Test Plan for the installation of Temenos' Transact core banking product with our legacy mainframe banking system at Test Republic Bank. The document details the objectives, scope, strategy, and plan for testing to ensure a seamless transition to the new system without disrupting client access to their accounts.

Objectives

The main objectives of the system testing are:

• To ensure the successful installation and integration of Temenos' Transact with the legacy mainframe banking system.
• To verify that all account information is accurately migrated to the new system.
• To ensure continuous client access to accounts during the transition.
• To validate that accounts with $100 or less are closed and owners refunded.
• To ensure compatibility with third-party software (Paymentus and LendingPad).
• To automate test cases using Selenium.
• To verify that the UX uses only different shades of blue.

Scope

The scope of the system testing includes:

• Migration of account information for 100,000 retail checking and savings accounts, as well as CDs, Money Market accounts, mortgages, credit cards, car loans, and other personal loans.
• Validation of data integrity and accuracy post-migration.
• Functional testing of Temenos' Transact features.
• Integration testing with Paymentus and LendingPad.
• UX testing for color scheme compliance.
• Performance, security, and regression testing.

Test Strategy

The overall test strategy includes the following types of testing:

• Functional Testing: To verify that all functionalities of Temenos' Transact work as expected.
• Integration Testing: To ensure seamless integration between Temenos' Transact, Paymentus, and LendingPad.
• Performance Testing: To assess the system's performance under load.
• Security Testing: To ensure the system is secure from vulnerabilities.
• Regression Testing: To ensure new changes do not impact existing functionalities.
• UX Testing: To check compliance with the color scheme requirements.
• Automated Testing: Utilizing Selenium for test automation.

Test Plan

Test Environment

The testing environment will include:

• Hardware: Cloud-based servers for Temenos' Transact.
• Software: Temenos' Transact, legacy mainframe system, Paymentus, LendingPad.
• Network Configurations: Secure connections between all integrated systems.
• Other Components: Test data representing all account types.

Test Criteria

• Entry Criteria:
  • Test environment setup is complete.
  • Test data is prepared and loaded.
  • All testing tools (including Selenium) are ready.
• Exit Criteria:
  • All test cases are executed.
  • All critical and high-priority defects are resolved.
  • Test Summary Report is reviewed and approved.

Test Deliverables

• Test Plan
• Test Cases
• Test Scripts (Selenium)
• Test Data
• Test Execution Logs
• Defect Reports
• Test Summary Report

Test Schedule

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

Resources

• Personnel: Test Manager, Test Leads, Test Engineers, Developers, Business Analysts.
• Tools: Selenium, test management tools, defect tracking tools.
• Test Data: Representative data for all account types.

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

• Recording defects with detailed information.
• Prioritizing defects based on severity.
• Assigning defects to developers for resolution.
• Retesting resolved defects.
• Updating defect status in the tracking tool.

Risk Management

Potential risks and mitigation strategies include:

• Data Migration Issues: Perform thorough data validation post-migration.
• System Downtime: Schedule testing during off-peak hours and ensure rollback plans are in place.
• Integration Failures: Conduct early integration testing and have technical support on standby.
• Performance Degradation: Perform load testing and optimize system performance.

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
• Date: 05/07/2025
• Approved by: [Approver's Name]
• Date: [Approval Date]