AMEX has an official ICS word document. That document needs to be filled according to the terminal specifications.
Here are the steps needed to fill the ICS and run the test cases for different profiles:
1st Step:
AMEX Official winword document needs to filled according to the terminal`s specifications. The ICS configuration is a state machine implementing the ICS configuration and running the tests for different profiles:
strictly dependent on the kernel functionality and it may differ from customer to customer according to purchased kernel and device capabilities.
2nd Step:
After the ICS configuration is ready the winword document needs to be imported into the EVAL tool.
...
After importing the ICS winword document check the imported ICS flags should be checked. The word document may fail to fill some configurations:
...
Since the configuration is different for each terminal the attached image is an example.
Each configuration flag has 2 columns: 1) Value 2) Configuration
Value: It can be assigned value of Y or N. The value used here is the default value of the terminal.
Configuration: It can be assigned value of Y or N. It states whether that option of the terminal can be toggled.
After the import is completed “Inconsistency Check” needs to be done.
...
The inconsistency check finds the conflicts in the ICS file. If there is any inconsistency in any of the profiles it needs to be fixed before starting the tests.
After the checks are completed save a copy of the ICS. That will be useful when the EVAL tool is restarted. When a .tre file is already available there will be no need to import the winword document again.
3rd Step:
At that point configuration EVAL tool is complete.
EVAL tool has 2 libraries for AMEX kernel testing. One is for EXPRESSPAY and one is for COMMON library.
We suggest you save different test result database for each library. The naming convention we use is:
CustomerNameDeviceNameDateAmex4_0LibraryName.mdb