Test your Temenos upgrade project with resilience and performance
An upgrade or transformation project can take too long, cost a lot, and setting up the right environments can be an excruciating process – and can extend projects by weeks.
Validata simplifies the upgrade process by removing complexity and risk and enables Temenos clients to successfully execute an upgrade with minimal business disruption.
Our risk-based testing approach powered by AI-powered, model-based test automation, agile test data management and provisioning, service virtualization, etc, enables Temenos clients to control risk, delivering on the promise of full automation and predictive analytics and ensuring they achieve agility @ scale to unlock and accelerate their upgrade and digital transformation initiatives.
Validata has the ability to perform end-to-end upgrade testing incorporating
Exploratory Business Testing
Like for Like financial comparison and audit (Reconciliation)
Environment Management and comparison
The approach we follow includes the creation of a test pack based on specific transaction load as per business need. Risk assessment and risk registration is also suggested in order to create risk-based test pack that will be executed against the different Components, subject to testing or if existing the desired copies of the Production environments for both (current and Target) releases.
This approach provides flexibility and easy maintenance against changes, as we keep the test cases independent from the environment - logical - changes e.g. Rates changes (which happens daily), which can lead to incompatibility and failures (problems appearing in record-and-playback approaches).
End to-end, Like-for-Like Financial Reconciliation
Both financial and non-financial data from the legacy system must be properly migrated to ensure data sanctity. With complex business rules and large volumes of data, reconciliation becomes an onerous task.
Validata performs Reconciliation between aggregated amounts per area/product in the source systems and the total of this area/product in GL Level in the main system.
Depending on the project and the project strategy that is envisaged by the bank the reconciliation process can vary as it might have to cater for additional or historical accruals, corrections of amounts that are not in the legacy system or even the timing when the exact balances will be available e.g. suspended interest.
For that reason, our approach is flexible, robust and with no dependency on Temenos or any other GL system as the extraction is independent.
Stage 1
Extraction Reconciliation
Report population based on comparison between extracted Legacy data. Also all mismatches as per business validation rules.
Stage 2
Transformation Reconciliation
Report population based on extracted transformed data. The process is using the defined business transformation rules.
Stage 3
Load Reconciliation
Report population based on data that should be loaded against data actually loaded in T24.
Stage 4
Reconcile
Report population based extracted data from T24 against data that should have been loaded.
Environments Comparison
Ability to compare Environments as well as different versions of the same environment on:
Build Control and DL Define
Applications
Records
Fields
Values
Parameterization
Performance & Load Testing
In the context of an upgrade scenario, the goal of performance testing is to verify that the system’s performance is maintained or improved by the upgrade. Core Banking applications are mission critical systems involving millions of transactions carried on daily basis and the new system must be validated to offer “optimal performance” and reliability.
Validata’s Performance Testing solution brings to light shortcomings and failings in the applications’ performance such as response time problems; it identifies all design issues and performance bottlenecks well before production, and ensures that the bank’s applications are reliable before they go live.
Our website uses cookies. By continuing to use this website you are giving consent to cookies being used. For more information on how we use cookies, please read our privacy policy