...
Keeping these databases are very useful since we want to trace the tests` results.
4th Step:
Now the tests need to be run for different profiles.
Then for each configuration profiles using the Switch Profile button:
An EVAL popup appears indicating what are the configuration or settings to apply to the reader, as for example
...
Then for each EVAL configuration part of the current Profile
{
1 in ACE Client in the SETUP tab, adapt the tags to overload from the ACE Server configuration:
...
1.a Check the Use Default (Overload tags value with …)
1.b Enter the value for tag 9F35, 9F33 …
1.b.1 Overload tag 9F33 in ENTRY POINT for these options:
(leave Byte 2, bit 8 to 0)
Other interface: byte 1, bit 6 ICC with Contact, bit 7 for magnetic Strip
Online Pin: Byte 2 bit 7
Signature: Byte 2 bit 6
SDA: Byte 2 bit 8
DDA: Byte 2, bit 7
CDA: Byte 2, bit 4
Overload tag 9F35 in ENTRYPOINT for these values (Offline Only/Online Only):
Merchant Controlled
21 – Attended, Online only
22 – Attended, Online with offline capability
23 – Attended, Offline only
24 – Unattended, Online only
25 – Unattended, Online with offline capability
26 – Unattended, Offline only
2 in ACE Client in the CONFIGURATION/ENTRYPOINT once you have loaded the ACE Server Configuration:
1.b.2 Use tag DF1B in ENTRY POINT for these options:
Mobile CVM: Byte 5, bit 3
Terminal Exempt Of No CVM Checks: No CVM Check exempt: Byte 5, bit 2
Delay Authorization: Byte 2 bit 2
Transit Terminal: Byte 5 bit 1
Only EMV Mode: Byte and bit to define
1.b.3 Use tag DF30 in ENTRY POINT for these options:
Zero Amount Checking Flag: Byte 1 bit 7
Status Check: Byte 1 bit 8
1.b.3 Use tag 9F40 in ENTRY POINT for these options:
Goods: Byte 1 bit 7
Services: Byte 1 bit 6
3 Send the ENTRY POINT configuration to the device
4 Execute the tests
5 Check if another configuration is expected in this Profile
} Next Config
If end of all configs or per config, change the library to make the profile tests for both library.
} Next Profile