Payment Testing Services
Blend of testing experience and domain expertise for a strategic testing process
Impactful Testing Efforts across Multiple Payment Channels
Yethi’s domain experts offer comprehensive payment testing to help you maintain error-free functionality, stringent security, and smooth performance of diverse payment platforms across retail, corporate, other banks and clearing houses.
Payment Testing Service Highlights
Scheme Testing
- IMPS, RTGS, NEFT, UPI
- UAEFTS, KNPS, QIPS, QATCH
- KASSIP
- SEPA
- LYNX, RTR
- SWIFT FIN
- KATS, LankaClear, LANKAAQR
- TISS, TACH
Testing Phases
- Manual and Automated Testing
- Regression testing, UAT, SIT, Interface and Channel testing
Product Diversity
- OBPM
- Finacle
- EASTNETS
- Intellect
- Montran
- Temenos
- VolPay
- Finastra
Testing Vision
Testing Experience
- Maximum reusability
- Minimum coding efforts
- One solution for various types of automation solutions
- SIT, Regression, E2E Testing/ UAT
- Test Assessment & Planning (Analyze the requirement, Define Test Strategy, Develop Master Test Plan, Environment Readiness Review)
- Test Design (Design SIT, UAT Specification, Prepare for Test Environment Setup
- Prepare functional test scripts and execution
- Report and complete test
Payments Testing Phases and Activities
Payment Testing Methodology
Testing Objectives:
- Ensure the Application Under Test confirms to the functional requirements
- Client Samples for each SPRINT to be shared upfront
- The shared samples will be considered as part of QA Exit Criteria without which the release will not be certified
- Test cases are reviewed by BA/SME
- There will be RTM (Requirement Traceability Matrix) maintained to ensure complete coverage in testing
- Perform review session with Client BA on the Test cases once reviewed internally
Acceptance Criteria for Client Deliverable:
- Entry and Exit criteria met
- No Critical and High severity defects open
- Successful Demo and acceptance criteria met
- 100% Test execution done, Above 90% pass and maximum 10% fail
Automation Goals:
- 100% Automation Coverage
- No Manual intervention
- Integrate with build automation tool CI\CD Setup
- Tenjin will be used for Automation
Defect Life Cycle:
- JIRA/ Bugzilla will be used as Defect tracking tool in the project
- JIRA/ Bugzilla will be primarily used to create task, log and track defects, so as a Project management tool for the project
Tools:
- All Test Scenarios, Test Cases, Test Data and Test Result will be captured in Tenjin Vault
- Test Plan & Test Cycle will be maintained with in the Tenjin Test Management tool/ 3rd party Test Management tool
