The Transaction Tester is used to build scripts and execute test plans. The proprietary scripting language is used across all message formats making your script building much simpler when you need to test multiple formats as you only learn one set of tools. Special functions exist to add to the robustness of the scripting capabilities; as well as variables that can be accessed by each script. For example, if you are doing a lot of testing with a single card, create a variable to be used for the PAN and reference that variable from each script. To change the card number being used for testing, simply change the value of the variable and all scripts using that variable are automatically affected. A card registry can be created to hold any reasonable number of cards you wish to test with. This makes card data much more accessible to the test plan. It also allows for load testing without reusing the same card number too frequently.
The Issuer Simulator simulates the system the message is being sent to. This can be a network, host or any other system that receives the specific message format being used. Specific result codes can be configured in order to fulfill the business requirement. You can also configure specific response field values based on configured parameters.
The Stress Tester allows you to put load on the network directed to the payments system being tested. This is helpful to identify performance issues and also provides important information regarding the potential scalability of the system.
The Message Viewer parses raw messages and displays the data based on the ISO message format selected. This is extremely valuable when looking at transaction logs that only contain the raw data.
Copyright ©2022 Story Business Solutions, Inc. All Rights Reserved.