Why Simulate the OMS Client-side Application?
A number of options are traditionally used when testing trading systems, any combination of which might be used for testing a given type of release.
These traditional testing methods are limited in a number of ways:
- Manual input via the standard user interface, following test scripts and comparing against expected results
- high risk of human error, especially where the scope is large
- unnecessarily high cost, even for low-rate testing outfits
- complex areas of the system may not receive as much attention as they could
- timing of data input is unpredictable and may be unrealistic vs production systems
- Spreadsheet input to load batches of orders
- difficult to control speed of data entry
- Server-side scripts
- usually not located in the same physical location as the PCs that would be running the client-side application.
- can be difficult to manage on a different server to the server-side application. If run on the same physical machine as the server, performance tests may affect the performance response.
- A general-purpose FIX client simulator
- generally focussed on field-level functional testing.
- not always capable of loading the server sufficiently
- often will not provide analysis of the response, especially on performance
- A general-purpose automated GUI testing tool
- usually require full control of the PC on which they are running. So simulating 30 client-side applications requires 30 PCs.
- test setup requires expert knowledge and can be prohibitively time consuming & expensive
- in some cases the client-side application makes it very difficult for these tools to be effective
With CSim™ we will approach testing in a new way, addressing all of these limitations to provide an effective set of tests. Contact us now to discuss how you can shape the development of CSim to fit your testing methodology.