Challenges & Solutions
Sr.No
Challenges
Description
Action Taken / To Be Taken / Solution
1
​
​
​​
​
​
​​​​​​​​​
​
2
​​​​​​
​
3
​
​
​
​
4
​
​
​​
​
5
​
​​
​
6
​
​
​
​
7
No Visibility on Mock Runs and Expectation from Mocks
​
​
​
​
​
​
​
​​​
No Availability of Requirement Documents
​​
​
Identification of Test Scenarios/Cases related to Branch
​
​
​
​
​
Understanding of Defect Tracking Tool - MANTIS to all Stakeholders
​
​
​
​
Knowledge on Product/Sub Products or Differentiators among the Various Schemes
​
​
​​
​Environment Set Up and related Issues
​
​
​
​
​
​
Freezing of Code Mapping - i.e. Mapping of certain Schemes, Codes, Pointers of Vijaya Bank in format of BOB
Team Performed Data Migration as well as Functional Testing on 6 Mock Runs and we had ample no of Open defects, but Bank persisted with Mock Run after Mock Run and there was lack on expectation and Visibility
​
​
​​​​
​
​
​​​
Neither Requirement Document/FSD/BRD document was Provided Nor Walkthrough was Provided.
​
​Few of our Test Scenarios were deemed as "NA" due to Branch Limitations
​
​​
​​
​
​
MANTIS as a Defect Tracking Too was new to most of our Team Members as well as to Bank Staff, which created lots of ambiguity in tracking Defect without knowing the Defect Life Cycle Maintained and Tracking of various Statuses
​
​​​​
We were provided with a Generic List of Schemes which Bank shall be working with, but we did not had the Differentiators among these schemes based on which our Test Cases could have been enriched in better way​​​​​​
​
​
As we started UAT, we encountered that there was too much inconsistency and Lag time which inadvertently impacted the Execution
Also, there was single UAT environment for Domestic Core and Non Core due to which Bank was reluctant to Run EODs & EOMs
​
​​​​
The Code Mapping sheet was getting Modified frequently which impacted the Data Migration Testing because every time the Issue Found in Data Migration Testing were mostly due to Code Mapping.
Team has to update the Code Mapping every time in Tool for it to run smoothly
We highlighted Bank about the Open Functional Defects which could be fixed without Mock Runs and hence we explained Bank the Effort is getting Duplicated and then we decided to execute the Test Cases Blocked due to Open Defects in Each Mock with some amount of Regression. Also, we pushed Bank to get the Issues Fixed without which the Execution would be rendered Meaningless
As for Data Migration Issues, we compelled Bank to have the Issues Fixed in each Mock Run
​
​
We tried gathering information related to BOB Functionalities and tried mapping the same with Finacle Menus
​
​Identified the Branch and its Nature and tried to scope the functionalities pertaining to it.
For Ref.
Agriculture Branch - Need to Focus on Agricultural Related Functionalities such as Agriculture Loan etc.
​
​​
Need to Understand working of MANTIS tool and to create a proper Defect Lifecycle or Workflow in it and providing Understanding of its working to all stakeholders
​
​​
​
We need to ensure that we get the Differentiators/ Product Features List from Bank
​
​​
​
​​​​​
We need to highlight Issue related to Environment upfront to Bank and relate the Dependencies
​
​
​​​​​​
​
Need to ensure the updated Code Mapping is inserted in tool every time before starting Data Validation Testing
.png)