Managing Financial Network Mandate Testing

Verifying the reversal processing
Do account totals reflect reversals or partial reversals? Are reversed transactions correctly recorded by the system? The system must include the original transaction data as well as the reversal of that transaction. For partial reversals, ensure the system correctly reflects any applicable overage or shortage.
Scheduling meetings to report and resolve issues
Do you have processes in place for reporting and resolving issues discovered during testing? Early during your testing, establish a schedule of meetings with developers (and other personnel, if needed) to discuss issues and possible solutions or workarounds. Remember to include clearing and settlement, reconciliation, or other personnel involved in "back-office" processes. The number of issues will determine the frequency of these meetings.
Performing negative tests
Is invalid input handled correctly? Does the system recognize invalid data elements? Are invalid messages declined without affecting system performance? Can the system handle declines, rejects, and denials correctly?
Performing regression testing (to test existing functionality)
Do existing transactions continue to flow as expected? Do reports and batch files continue to reflect all client activity?
Regression testing is a combination of science and art. All testers realize you cannot test the entire system. The hallmark of good QA or QC test planners is their ability to determine the areas of the system in which errors could result in the highest risk to the organization and rigorously test those areas, and then supplement those tests with broader-spectrum testing designed to adequately test areas where errors present lower risk. An organization’s regression testing framework must grow to encompass recent changes to the system. For example, a regression test plan for testing changes to withdrawal transaction processing means not only testing withdrawals from various account types (checking and savings), but also testing withdrawals with cash back, and withdrawals conducted with and without a PIN—and then testing a number of other similar transactions.
In some cases, stress testing (to test your system’s load capacity)
Some changes (for example, mandated EMV support) may translate into additional processing overhead. For these mandates, stress testing may be advisable to ensure your processing system can support your anticipated transaction volume.

Page 5 of 6

< Previous Page 1 2 3 4 5 6 Next >