The Art Of Testing Trading Platforms From AppLabs

4,777 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
4,777
On SlideShare
0
From Embeds
0
Number of Embeds
19
Actions
Shares
0
Downloads
225
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

The Art Of Testing Trading Platforms From AppLabs

  1. 2. The Art of Testing Trading Platforms 23 rd July 2008 Ravi Gurrapadi
  2. 3. Agenda <ul><li>Exchange/Trading Platform Overview </li></ul><ul><li>Key Challenges/Risks </li></ul><ul><li>Acceptance Criteria </li></ul><ul><li>Test Governance/Management </li></ul><ul><li>Functional Testing/Complex scenarios </li></ul><ul><li>Integration Testing </li></ul><ul><li>Performance Testing </li></ul><ul><li>Failover/Recovery Testing </li></ul><ul><li>Summary </li></ul><ul><li>Questions </li></ul>
  3. 4. Typical Stock Exchange/ Trading Platform Overview
  4. 5. Key Challenges/Risks <ul><li>Business Challenges </li></ul><ul><ul><li>Developing complex trading scenarios & test cases </li></ul></ul><ul><ul><ul><li>To reflect real time trading </li></ul></ul></ul><ul><ul><ul><li>Integrating different modules (Front, Middle and Back office functions) </li></ul></ul></ul><ul><ul><li>Compliance to evolving regulations like RegNMS, MiFID </li></ul></ul><ul><ul><li>Building & maintaining the domain competence </li></ul></ul><ul><li>Technical Challenges </li></ul><ul><ul><li>Interaction of multiple systems through several interfaces and gateways </li></ul></ul><ul><ul><li>Automation of the complex scenarios & interface gateways </li></ul></ul><ul><ul><li>Performance testing to ensure acceptable levels of latency as per the SLAs </li></ul></ul><ul><li>Risks </li></ul><ul><ul><li>Business – changes in business model, rules & regulatory requirements, introduction of new products, down time (revenue lost), time to market </li></ul></ul><ul><ul><li>Technology – risk of failure, new technology integration, legacy applications, migration to a new application, 3 rd party application issues affecting your own system </li></ul></ul>
  5. 6. Acceptance Criteria <ul><li>Testing for core functionalities as specified in the functional requirements </li></ul><ul><ul><li>User Management </li></ul></ul><ul><ul><li>Instrument Management </li></ul></ul><ul><ul><li>Quote/Order Management </li></ul></ul><ul><ul><li>Session Management </li></ul></ul><ul><ul><li>Trade Management </li></ul></ul><ul><ul><li>Risk Management </li></ul></ul><ul><ul><li>Compliance to Regulations </li></ul></ul><ul><li>Testing for agreed specifications as per SLAs </li></ul><ul><ul><li>Performance </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Network </li></ul></ul><ul><ul><li>Reliability </li></ul></ul>
  6. 7. Governance Structure
  7. 8. Test Governance/Management <ul><li>Major stakeholders </li></ul><ul><ul><li>Client organization, development organization </li></ul></ul><ul><ul><ul><li>Management </li></ul></ul></ul><ul><ul><ul><li>Domain </li></ul></ul></ul><ul><ul><ul><li>Technical </li></ul></ul></ul><ul><ul><ul><li>Client's clients/vendors </li></ul></ul></ul><ul><li>Adherence to agreements with all the stakeholders </li></ul><ul><ul><li>Test Plans </li></ul></ul><ul><ul><ul><li>Deliverables </li></ul></ul></ul><ul><ul><ul><li>Schedule </li></ul></ul></ul><ul><ul><ul><li>Change management </li></ul></ul></ul><ul><ul><li>SLAs </li></ul></ul><ul><ul><ul><li>Metrics </li></ul></ul></ul><ul><ul><ul><li>Escalation procedures </li></ul></ul></ul><ul><ul><li>Sub contracts </li></ul></ul>
  8. 9. Test Planning & Design
  9. 10. Level 1 Business Process Flows
  10. 11. Level 2 Test Scenarios Test Scenario
  11. 12. Level 2 Test Scenarios
  12. 13. Level 3 Test Cases Test Case
  13. 14. Integration Testing/Interface Testing
  14. 15. Performance Testing <ul><li>Response times are critical </li></ul><ul><ul><li>New generation systems have minimal latency </li></ul></ul><ul><ul><li>Time is literally money </li></ul></ul><ul><li>Highly complex </li></ul><ul><ul><li>Multiple API’s and connections to external systems </li></ul></ul><ul><ul><li>Need to performance test sub-systems </li></ul></ul><ul><li>Variety of scenarios </li></ul><ul><ul><li>Examples: day in life of, daily peaks, fast markets </li></ul></ul><ul><ul><li>Soak tests for memory leaks, etc. </li></ul></ul><ul><li>Performance test data </li></ul><ul><ul><li>Huge volumes of test data required </li></ul></ul><ul><ul><li>Needs to be generated and managed efficiently </li></ul></ul>
  15. 16. Failover/Recovery Testing <ul><li>Test system resilience to failure and the ability to continue to provide service during failure & recovery </li></ul><ul><li>Test standard operating procedures to ensure they are robust and comprehensive </li></ul><ul><li>Ensure recovery is with acceptable time scales and performance criteria </li></ul><ul><li>Areas to cover: </li></ul><ul><ul><li>Software (operating system, process and application) </li></ul></ul><ul><ul><li>Hardware  </li></ul></ul><ul><ul><li>Power Failure </li></ul></ul><ul><ul><li>Network  </li></ul></ul>
  16. 17. Summary <ul><li>Stock Exchanges have inherent complexity in terms of business flow and business rules – testing is a critical element in ensuring business delivery </li></ul><ul><li>Key areas of interest for stock exchanges: </li></ul><ul><ul><li>Increased volumes </li></ul></ul><ul><ul><li>Speedy execution </li></ul></ul><ul><ul><li>Effective surveillance to safeguard investor and market interest </li></ul></ul><ul><li>These go in as requirements to a trading application and the testing process to ensure the implementation is a business success </li></ul><ul><li>Having a well tested application that doesn't fail in real time gives an edge over the competition – areas of failure in this area become public news </li></ul>
  17. 18. Questions? <ul><li>For any questions following the presentation, then please e-mail [email_address] </li></ul>

×