Posted on 9th Nov 2017 6347 views
When you need to customize your own test case, you need to follow some simple steps all the time.
In order to obtain this, you need to alter test data in Excel, save your new test data, export for the simulator, restart simulator with new test cases.
Changing test cases with the neaPay ISO8583 simulator is really easy because you just need to work with Excel.
1. Go to the deployment folder, for example C:/neaPaySimulator
2. Go inside the Acquirer instance(for example neapay_ACQ_client)
3. Go inside folder test_data (E.g. C:/neaPaySimulator/neapay_ACQ_client).
4. Open spreadsheet ISO8583_TestCases_v3.1.xlsm.
Warning: It is advised to NEVER edit the CSV files.
5. Go to sheet ISO8583_Acquirer to edit Acquirer test cases (These are messages that the simulator builds)
We will refer to this as the Acquirer Sheet from now on.
6. Update the columns to the corresponding fields. For example, Amount in Filed 4 (DE04) on column R.
7. The simulator can populate the fields with values, if values are inserted
8. The simulator can use some keywords to trigger a specific javascript behaviour
Below are some standard values that you may want to remember. They are checked in the following script:
script_acquirer.js:function buildField(name, field, caseField, isoMessageAcqRq) {
**SYSTEM** means that the simulator will use script logic to build that field. It is used to retrueve system time and date, generate random values, perform complex operations, or perform cryptography, or make external calls; So the value will be populated by the system. Script reference:
script_acquirer.js:function buildSystemField(name, field, caseField) {
**NOVALUE** means that the simulator will not use that field, and will not include it in the message. The Bitmap will NOT be activated for this field.
**CARDFILE** means that the simulator will use the Cards Sheet any to build that field, and will look up the card key selected set for that transaction;
script_acquirer.js:function buildCardField(name, field, currentCard) {
**TERMFILE** means that the simulator will use the Terminals Sheet to build that field, and will look up the Terminal set for that transaction; You can also use Excel's sheet reference information to retrieve information from another sheet, whoch may prove easier
12345 - if a text value is set, that value will be loaded in the message exactly from the spreadsheet. If the value is longer than defined, the simulator will trim it; if it is shorter, the simulator will pad it as defined. If you use binary data, paste the hex representation of the binary data and the simulator will convert it automatically when loaded in a binary field.
9. Edit column AW (DE 35) and change it from **SYSTEM** to a value of "12345678910"
10. Press the "Save Test Data CSV" button inside the sheet, next to the neaPay logo. It will ask you about saving the excel file and exporting a .csv. Answer Yes.
Warning: It is advised to NEVER edit the CSV files. This button will generate the CSV files
11. Close the Excel file (optional).
12. Close the Acquirer simulator. The server can keep running.
13. Open and Start again the Acquirer simulator, check that it has connected.
14. When the Transactions List window opens, check that your new transaction is available in the list.
15. Select your configured transaction and click the Send button.
16. Check the Acquirer Console for the text Test case: and check that after that, the field 35 has the value you wrote above.
Congratulations! You have successfully configured your own test case!
BIN List & Range for MasterCard, Visa, Amex, Diners, Discover, JCB, CUP
149396 views
Read smart card chip data with APDU commands ISO 7816
59863 views
ISO8583 Response Codes for Transaction processing
55939 views
ISO8583 Message Types for Transaction Processing
28227 views
ISO8583 Processing Codes for Transaction Processing
27817 views
Run the neaPay ISO8583 simulator
19843 views
Deploy, run and generate with neaPay Card Data Generator
19739 views
MCC Codes - Merchant Category Codes to use in ISO8583 Field 18
18677 views
ISO8583 payments message format, programmers guide
17480 views
ISO8583 message: The list of ISO 4217 currency codes for data elements 49 and 52
15954 views
ISO8583 Message Converter JSON and XML interface specification mapping
12880 views
Cards and Banks Training
12462 views
Support for the neaPay products: Authorization, Switch, Converter, Simulator, Issuer
9149 views
Log Files in BASE24 classic
8950 views
Create a new test case in the neaPay ISO8583 simulator Video guide
8578 views
Java version for neapay products Simulator Converter Switch Authorization Cards Issuer
8155 views
Deploy the neaPay ISO8583 simulator - video guide
8120 views
BASE24 classic vs BASE24-eps
7907 views
BASE24 documentation to read
7840 views
BASE24 classic interview questions
7688 views
Performance testing at 500, 1000 and 1500 TPS
7552 views
EMV explained for programmers
7351 views
ISO8583 converter to JSON XML SQL to HTTP host - message flow - video guide - Part.2
7103 views
ISO8583 ATM POS Crypto API integration with exchanges like Coinbase or Binance
6780 views
Adding your own card to the Payments simulator to test your system
6597 views
ISO8583 converter to JSON XML SQL to HTTP Host - host unavailable - video guide- Part.3
6531 views
Card readers supported by neaPay payments simulator, CHIP and NFC
6519 views
Connect the neaPay ISO8583 Acquirer simulator to your own host or Issuer
6511 views
ISO8583 converter to JSON XML SQL to HTTP host - start& run - video guide - Part.1
6492 views
Run the neaPay ISO8583 converter to JSON, XML, SQL, in a test environment
6372 views
Load Test enabling and performance testing at 1TPS and 100TPS
6357 views
Changing fields definitions in the ISO8583 simulator and message converter
6350 views
Altering test cases in Excel for the ISO8583 simulator
6348 views
Deploy the neaPay ISO8583 Payments converter in a test environment
6343 views
Sample Recommended design for an Acquirer test cases suite, Scenarios and Regression
6342 views
How the fingerprint reader works in the ISO8583 payments simulator
6341 views
Enabling traces in the payments simulator
6339 views
Run One, Run Scenario, Run All, Run Load in the neaPay ISO8583 Simulator - Use guide
6339 views
BASE24 classic screens examples explained
6335 views
Regression Testing in 1 click with instant Analytics and CSV report
6207 views
Deploy the neaPay HSM simulator in a test environment
6065 views
BASE24-eps interview questions
6016 views
Deploy the Payments Switch Router in a test environment
5922 views
BASE24 classic ATM configuration Tutorial in ATD and XPNET with examples
5671 views
Add extra custom fields to the ISO8583 simulator
5504 views
BASE24 classic cards configuration tutorial with Examples
5321 views
PCI compliant with neapay switch
5103 views
BASE24-EPS ACI DESKTOP tutorial - Getting started
4915 views
ISO8583 Message Converter to XML SQL CSV interface specification mapping
4757 views
Trace configuration in neaPay Simulator, Converter, Switch, Authorization and Cards Issuer
4550 views
BASE24 classic prefix configuration tutorial CPF with examples
3656 views
BASE24 classic tracing of transactions. Audits, configuration, enabling and opening
3551 views
ACI BASE24 classic automatic extract configuration
3378 views
BASE24 classic Institution configuration Tutorial with example
3227 views
BASE24 classic balance file configuration PBF with example
3188 views
First steps with BASE24 Classic
2959 views
Getting started with using Prognosis for BASE24 and BASE24-eps
2723 views
POS simulator format SPDH HPDH Verifone and custom
2514 views