1. New Trading Platform
|
Our client needed to improve the time-to-market for a new trading platform and to broaden the scope of testing for the application. This had to be done in a tough cost-cutting environment which required in-depth knowledge of securities trading and familiarity with brokers’ mid- and back-end systems because the new trading platform had to be integrated with the client’s existing trading infrastructure, including customer account databases, P&L databases, market data, etc.
|
 |
2. Our ability to work with QA groups
|
Due to the need to cut costs to stay ahead of the competition, our client was presented with the following challenge: how to relocate the majority of internal QA staff to other departments, while preserving and raising the level of development and maintaining product quality. QA outsourcing was chosen as a solution. The transition of testing from the internal QA to vendor QA needed to be done within a strict time frame. In addition, during the transition, internal team morale needed to be preserved in order to avoid potential conflicts related to the profound changes in the customer’s team structure.
|
|
3. Multi-Server Testing Automation
|
Our client normally increases the volume of its developed functionality by 10 – 15% each year. As a result, the amount of testing and maintenance work it entrusts to Allied Testing increases at the same rate but the client requires us to deliver this increasing workload within a fixed budget. We succeeded in meeting our client’s expectations by decreasing the amount of manual testing and increasing automated testing.
|
|
4. Performance Testing
|
Our customer is a leading online broker. Well recognizable trading platform provides Direct Market Access (DMA) to its customers via a set of front end applications. The front end suite consists of desktop applications, web applications and XML web services. Trading activities are supported by a large distributed back-end with several dozen of services hosted on hundreds of servers. The key factors of such system success are: ability to process extremely high volumes of data, low response times and system high availability. The platform is constantly improved with cutting-edge electronic trading technologies.
|
|
5. Unit Testing Automation Tool
|
One of our clients employs over 2,000 staff developing solutions and software applications that anticipate customer needs and help keep operations running smoothly, day and night, while handling up to more than a million transactions /hour. Developers need to be able automatically to unit test newly developed applications.
|
|
6. Testing Automation Tool
|
Our client supports many releases for a number of products (both internal and customer facing) and was concerned about the large amount of regression testing required for these releases. The client also wanted this workload to be handled within tight deadlines. The challenge was to meet our client’s expectations by automating their regression testing requirements.
|
|
7. Exchange Simulator/Backtester
|
BackTester is an exchange simulator or back-testing application that simulates a stock exchange: users connect to it, receive market data, send orders and get status updates in the same way as they do when trading on real markets. This tool can be used to train human traders, to develop & test trading applications, to validate strategies, etc.
|
|
8. SILK Automated Testing
|
Why do we use automated testing?
Cuts costs and the testing speed is greatly increased;
Increase the scope of testing, without additional cost;
Decrease the possibility of human error;
Opportunity for detailed testing results, either as .log file compact reports or in any way convenient for clients;
Optimise use and allocation of resources during testing
|
|
9. SIEBEL-based CRM testing
|
Our client needed to implement a Siebel-based CRM solution and integrate it into their existing back-office. It wanted:
Web applications for both new account opening applications and for existing customers modifying their accounts;
A system to synchronise data between Siebel and their existing customers’ account databases;
To maintain its frequently changing web site;
|
|
10. Order Audit Trail System Testing
|
One of our clients asked us to test their Order Audit Trail System (OATS). Previously, the system had been tested manually, which was highly labour intensive and involved:
1. The creation of a model file for OATS testing, which used to take five man-days;
2. The comparison of actual vs. expected results, took four man-days;
3. The design & presentation of the testing results, took one man-day;
The manual testing itself used to take eight man-days and, in the process of comparing expected vs. actual results, the possibility of human error could never be completely discounted. That’s why it was decided to automate the whole OATS testing process.
|
|
