run_test.py

The run_test.py script calls a number of scripts that are generated by the create_demo.py script to perform all operations necessary to test and run a demonstration of the MATRIXX Engine functionality. The run_test.py script requires that the MATRIXX Engine is started.

The run_test.py script loads the pricing and subscriber data generated by the create_demo.py script and runs each individual run_test_#.py script that exists. As the script runs, all transactions are logged so the results and performance statistics can be verified. To run a test that calls a specific script while the engine is running, without starting and stopping a MATRIXX server or reloading data into it, you can call the input script directly rather than call the run_test.py script, or use the run_test_#.py scripts to run each step. You specify the number of the test to run in the # variable. For example, if you already have subscriber data created and loaded into a running system, you can run the run_test1.py script directly.

Note: The sed files are empty on a new installation based on the answers in the create_demo.info file. Site-specific answers during a demonstration configuration can cause these files to be non-empty.

Syntax

run_test_#.py -h | -b | -C check_type | -c | -D | -E | -e events | -F | -G | -i devices | -M | -n maximum_events | -o | -P | -Q | -q subs_queries | -r | -S | -s subscribers | -T services | -y | -v

Options

: Shows information about the script options and exits.
-h: Displays help information for this script.
-b: Specifies the number of wallets to use. The default is to use the same number of wallets as the number of subscribers.
-C check_type: Specifies the type of debugging interface to use: values are: cache, calls, kdbg, memory, threads, and threads_drd. Use this option with the -T option.
-c: Compares the results file with the expected results.
-D: Creates the configuration files used by the Diameter Gateway.
-E: Creates the file containing the event types to use.
-e events: Specifies the number of events to use.
-F: Creates subscribers with a fixed number of balances.
-G: Creates configuration files for Seagull software.
-i devices: Specifies the number of devices to create for each subscriber.
-M: Creates the mtx_config*.xml files.
-n maximum_events: Specifies the maximum number of events that can be written to the input event file.
-O: Specifies the maximum number of open sessions that can occur.
-p: Creates the pricing configuration files.
-Q: Creates the files containing the subscriber queries.
-q subs_queries: Specifies the number of subscriber queries to create.
-r: Specifies the call rate in messages-per-second to use during system runtime.
-S: Creates the file containing the subscribers.
-s subscribers: Specifies the number of subscribers to create.
-T: Identifies the programs files to check during debugging.
-y: Specifies the number of services per subscriber to use.
-v services: Displays more information as the script runs.