Testing

The testing process involves User Acceptance Testing in the Test environment, and Low-value Live Testing in the Production environment.

User acceptance testing

The purpose of UAT is to test the entire solution as thoroughly as possible. The tests are carried out by the relevant participants from your business. We recommend you create a test plan which details the scenarios your verification team need to cover during their testing.

To support the testing process a test environment is provided. This environment is also known as the 'support environment' or 'support'. It simulates the banking system, allowing you to test card payments without affecting any live bank accounts.

The following is a sample test plan that spans the QuickStream modules.

Payment tests should include:

• Approved transactions.
• Declined transactions.
• Invalid payment details (eg, reference number too short; invalid card number or BSB.)
• Duplicate payments.
• Upper limit and lower limit transaction amount tests.

Bank account payment tests should include:

• Rejected payments that are reported in the Exception Disbursement Response file.
• Declined payments that are reported in the Returns Response file.

Batch payment tests should include:

• Sending Request files to QuickBatch.
• Retrieving your Response file.

Reporting tests should include:

• Retrieving your daily payment report.
• Uploading the payment report into your system.

Administration tests should include:

• Creating users.
• Assigning roles to users.
• Searching for payments.
• Refunding and voiding payments.
• Re-sending receipts.
• Search for customers.
• Creating customers.
• Modifying customers.
• Adding recurring payments to customers.
• Modifying recurring payments.
• Stopping recurring payments.

QuickVault tests should include:

• Registering an account for a customer
• Replacing an account with a new account
• Attempting to register an account with invalid details
• Registering an account that is already registered.
• Sending Registration Request Files to QuickVault.

The test environment will remain in place after you go live. This will enable you to test any future changes before they are released into production. The test environment is provided on a best-efforts basis. It will occasionally be unavailable due to upgrades without notice. Please factor this into your testing time lines.

Low-value live testing

You must test the end to end solution in the production environment. You will perform a few small value transactions. This test will take a number of days to complete and will test all of your card merchants and bank account facilities. You must use a real account for your company for these tests.

Low-value card testing

The test consists of the following steps:

1. On day 1, make two small test payments for each card merchant.

2. On day 2, check your bank statement. Make sure:

• the bulk settlement amount is correct,
• the narrative is correct,
• the money has been deposited into the correct bank account.

3. Also on day 2, check your customer's card statements. Make sure:

• The amount is correct,
• The narrative is correct.

4. On day 3, refund all of the payments.

5. On day 4, check your bank statement. Make sure:

• The bulk settlement amount is correct,
• The narrative is correct,
• The money has been withdrawn from the correct bank account.

6. Also on day 4, check your customer's card statements. Make sure:

• The amount is correct,
• The narrative is correct.

Low-value bank account testing

The purpose of this test is to ensure your bank account solution is working correctly in production. We recommend using low value amounts (for example $0.20) because these are real payments using real bank accounts.

The low value tests involve a number of steps:

1. On day 1 do the following:

• Make 2 customer payments per bank account. For example, if your organisation has 3 bank accounts accepting payments, you should submit a total of 6 payments: 2 for the first bank account, 2 for the second bank account and 2 for the third bank account.
• Check the night time transaction report. Make sure it includes all 6 payments with a status of approved.

2. On day 2 do the following:

• Check your bank statement(s). Make sure the bulk settlement amount is correct, the narrative is correct and the money has been deposited into the correct bank account.
• Check the morning transaction report. Make sure there are no errors.

3. On day 3 check the morning transaction report. Make sure there are no errors.

4. On day 4 do the following:

• Check the morning transaction report. Make sure there are no errors.
• If refunds are in scope, refund all of the payments from step 1.