The testing approach is governed by the identification of the fundamental want and addressing that want. Our experts follow the below five step process to ensure the completeness of the testing procedure.

The testing approach is governed by the identification of the fundamental want and addressing that want. Our experts follow the below five step process to ensure the completeness of the testing procedure.

• Purpose of the product
• Major supporting functionalities – primary functions and contributing functions
• Identification of potential in-stability
• Testing the functions and recording the issues
• Consistency verification test and reporting

The product is reviewed along with Bank’s business users/vendors to determine the fundamental services it is supposed to provide. Test strategy is kept well diversified in terms considering multiple dimensions of coverage, including structural, functional, data, platform, operations, and requirements.

Each primary function should be tested to operate in a manner apparently consistent with its purpose and the stability of the product should be tested to continue to function, over time and over its full range of use, without failing or causing failure.

Areas of potential instability include functions handling huge amount of data, functions interfacing with external third party systems, functions of unusual complexity, functions that needs huge complicated user input was identified and tested for their functionality and the consistency.

With the above guidelines, our team of experts analyses the product and prepares a product coverage outline document including the product operations, functionality, data, platform and understanding of the gaps. From the above analysis our experts split the modules into individual line items covering all the functionalities and the operations/events associated with the life cycle of the product. Run charts are prepared including every line item as applicable.

Test execution and support efforts are estimated and scheduled in co-ordination with various teams including steering committee, Bank’s project managers, vendors and the product development/support teams. Test entry criteria, Deliverables, Test environment acquisition and configuration plan, Test cycle administration, Problem reporting system and protocol, Test status reporting protocol, Code freezing and incremental testing protocol, Test exit criteria and Sign-off protocol are discussed and agreed between the various parties involved.

Test Execution 

Our expert team executes all the test cases as per the test plan/run chart and observed for the expected results. All the cases where the product is incapable of operating in a manner consistent with the expected result, work in-correctly in a manner that seriously impact the normal usage of the function, hang, crash, lose data and observed to become inoperable or obstructed the course of testing are recorded and reported/circulated to the intended participants of the project.

Also, our team records the steps to stimulate the problem, if feasible and provide the percentage of reproducing, check for additional failures of similar kind and determine whether it is a linked or an isolated issue. This may give enough detail to allow the support team to reproduce the issues or otherwise get a clear idea of symptoms. Once the issues are fixed and released to the testing environment, our experts retest the case in exactly the same fashion as before to observe the consistent expected results in line with the functionality and the stability of the product.

Our expert team will establish an effective coordination, collaboration, and relationship among members of the test team, and between the test teams and the rest of the project to rectify and retest the identified failures.