TEMPLATE - Pay At Table - SPI Library 2.9 Integration - Certification Run Sheet v3.5.xlsx

	A	B	C	D	E
1	What is this?	This spreadsheet is used to manage the certification process for the integration of your POS with mx51 Instore Terminals. You should have received the certification test cases with instructions to replicate them and what to expect as a result. Before mx51 can start the official certification process, you are required to run through the test cases and report on them in this spreadsheet. You can make as many runs as you like. The latest versions of the certification test cases are located here: https://developer.mx51.io/docs/certification-test-suite mx51 will also use this spreadsheet to report to you the results from the run that we do ourselves during the certification. It is used to give feedback on any failed test cases and to track any required action.
2
3	To start a new run:	1. Simply complete the POS Run sheet against the mx51 test suite.
4		2. Record your results in the run sheet and leave any comments in the comments column
5
6
7	Prerequisites
8	- SPI Library 2.8x
9	- A VX 690 Terminal for testing running App Ver 2.8x or later. (To see the version press Enter + 8 on your EFTPOS terminal. If the Terminal is running an older version contact your mx51 Integration Engineer)
10	- A valid API Key. Contact your mx51 Integration Engineer if you have not been provided with a key.
11	- A POS Printer configured to print EFTPOS receipts
12	- The POS should set the currency to AUD for all transactions
13	- If upgrading from an older version of the SPI Library it is recommended to unpair the POS before the upgrade
14	Note: This document only contains test cases for the Basic Feature Set which are required for integration. If you are integrating optional features (such as Cashout, Tipping, Get Transaction, Split Transactions, Pre-Authorisation, etc) you should
15	also run through the test cases in the Additional test section
16
17	Pay at Table Additional Requirements:
18	- EFTPOS terminal which has a built in Printer (VX690)
19
20	Test Data
21	The test environment uses a financial simulator, and the amounts entered will determine whether the transaction is successful or not.
22	- For successful transactions ensure that an amount $1.00 or higher is used
23	- To ensure a declined response is returned when entering an invalid pin the transaction amount has to be for $0.55
24	- To ensure a declined response is returned for MOTO transactions ensure the transaction amount is for $0.05
25	- Any 4 digit pin can be entered when making transactions. E.g. 1111
26	- Merchant Password = 123456
27
28	Pay at Table Additional Test Data
29	- Table numbers should be restricted to 20 characters or less (alphanumeric), and not contain special characters or spaces
30	- Valid Operator Id/s. These are numerical values and are controlled in the Pay at Table config. Validating on the Operator Id is optional.
31
32
33	Table of Contents
34
35	Pay at Table
36	Configurations
37	Single Transactions
38	Even Split Transactions
39	Split by Amount (Dollar Split) Transactions
40	Merging tables*
41	Retrieve Open Orders (Tables)
42	Transaction Recovery
43	Table Locking*
44
45	Exploratory Testing
46	Every POS is different, and the mx51 Integration team realises that it is not always possible to predict in advance how every integrated feature will be used. Therefore we also perform exploratory testing to try to uncover any issues with the integration which may not be covered by the standard test cases. The reason for this is to prevent these issues from reaching production, and from affecting your customers. We will list any issues we find during exploratory testing in the General Feedback section of the Certification Test Run spreadsheet.
47
48
49	Production readiness
50	Note: Prior to deploying the POS application to Production the Test mode should be disabled from the POS UI. If the Test mode is set in the backend then it should be set to false. The reason for this is that Test mode will not work with production terminals, which will result in pairing failures.
51
52
53	Document History
54	List of test cases changes with each version
55	Document Version	New Test Cases / Testing Notes Added	Modified Test Cases	Test Cases Removed	Date Published
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100