Skip to content

1.15 Testing your TI functionalities for host protocols

Source: TI_Host_to_Host_Client_User_Manual_v52.pdf Document pages: 40 PDF pages: 40

F. The 'Client Specific' Template group

a) Near real time templates

  • None currently available

b) Real time templates

  • Vodacom - PTI

A. Process for quality assurance (QA) testing

Due to the complexity of the TI environment, all organisations must go through a testing phase before going into production with the system. This is mainly to verify connectivity, data integrity and client system changes and/or development. During the test phase the following key aspects must be verified:

  • Connectivity using your chosen delivery protocol must be stable and in place
  • Specified file layout must be adhered to
  • Business processes align with business requirements

The organisation must meet the following requirements before testing may begin:

  • The TI file layouts must be set up
  • The organisation and Nedbank must have parallel QA environments in place

During testing the following naming convention will be used:

Example: QNGG00.CDTIPK.A13OP678.EN0610.I1234C.SQ1234

  • A Q is used instead of a P.
  • (Q refers to a QA testing file, while P refers to a production file)

B. Testing scenarios

Tests could possibly cover the following scenarios, but can be tailored to your needs:

  • The sending of high-volume files (inclusive of high- and low-volume data)
  • The integrity of the data contained in the files sent (layout of data and file format)
  • The use of a nominated account(s) set up in accordance with the intended production profile
  • The transfer of corrupt files and/or transactions (file-handling process)

Note: QA data is for testing purposes only and is not to be used for any decision-making processes regarding your customers.