Technical Testing Introduction

233 views
192 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
233
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Technical Testing Introduction

  1. 1. Technical Testing Alexey Zverev EXTENT February 2011
  2. 2. Contents <ul><li>Technical Testing </li></ul><ul><li>Our world of trading systems </li></ul><ul><li>Approach – Performance Testing </li></ul><ul><li>Approach – Stability Testing </li></ul><ul><li>Approach – Operability Testing </li></ul><ul><li>Approach – Debugging </li></ul><ul><li>Tasks – Test Tools </li></ul><ul><li>Tasks – Test Preparation/Load Shape </li></ul><ul><li>Tasks – Test Execution </li></ul><ul><li>Tasks – Result analysis </li></ul>
  3. 3. Technical Testing <ul><li>Technical Testing or NFT </li></ul><ul><ul><li>Validation of Non-functional Requirements </li></ul></ul><ul><ul><ul><li>Performance </li></ul></ul></ul><ul><ul><ul><li>Stability </li></ul></ul></ul><ul><ul><ul><li>Operability </li></ul></ul></ul><ul><li>These requirements are usually applied to complex distributed server applications </li></ul><ul><ul><li>Supports many interactive users </li></ul></ul><ul><ul><li>Processing high volume of data coming from and disseminated to several sources </li></ul></ul><ul><li>Example: Web Sites or Web Services </li></ul><ul><li>Our world – Trading Systems, Exchanges, SOR, DMS, Brokerage, Trading Desks </li></ul>
  4. 4. Our world of Trading Systems
  5. 5. The Approach to Performance Testing <ul><li>Load Test </li></ul><ul><ul><li>Emulate load </li></ul></ul><ul><ul><li>Measure KPIs (Latency, Throughput, Capacity) </li></ul></ul><ul><ul><li>Determine the load, under which the KPIs become worse than required </li></ul></ul><ul><li>Stress Test </li></ul><ul><ul><li>Emulate extreme load </li></ul></ul><ul><ul><li>Monitor system behaviour </li></ul></ul><ul><ul><li>Ensure that we sustain it </li></ul></ul><ul><li>Soak Test (Long Running Test) </li></ul><ul><ul><li>Emulate load for a long time </li></ul></ul><ul><ul><li>Check whether we have any deterioration </li></ul></ul>
  6. 6. Approach <ul><li>Stability Testing </li></ul><ul><ul><li>Apply Load </li></ul></ul><ul><ul><ul><li>kill </li></ul></ul></ul><ul><ul><ul><li>unplug </li></ul></ul></ul><ul><ul><ul><li>do something crazy </li></ul></ul></ul><ul><ul><li>Operability Testing </li></ul></ul><ul><ul><ul><li>Manage the environment </li></ul></ul></ul><ul><ul><li>Debugging </li></ul></ul><ul><ul><ul><li>Help developers identify issues </li></ul></ul></ul><ul><ul><ul><li>Complex vs. Simple load </li></ul></ul></ul>
  7. 7. Tasks Test Tools <ul><li>Load injector </li></ul><ul><li>PCAP analyzer </li></ul><ul><li>These are some of the most essential pieces of any NFT project: </li></ul><ul><ul><li>Correctly emulate the connections, implement protocol, use API </li></ul></ul><ul><ul><li>Make sure that KPI measurements are valid and accurate </li></ul></ul><ul><ul><li>Make sure that a tool does not experience performance issues itself and doesn’t influence KPI measurements </li></ul></ul><ul><ul><li>Developers whose application you are testing will blame your tools! You will require a proof of your figures based on valid sources (as the developers think) </li></ul></ul>
  8. 8. Tasks Test Preparation Load Shape <ul><li>Live production system is the ultimate source of information </li></ul>
  9. 9. Tasks Test Execution <ul><li>Automated system restart and test execution is a good idea </li></ul><ul><li>Our system is a complex look at what’s going on </li></ul><ul><li>Be ready to run tests again and again </li></ul>
  10. 10. Tasks Result Analysis <ul><li>Monitoring hardware reconciles your latency and hardware results </li></ul><ul><li>Be ready to advocate test results </li></ul><ul><li>Perform in-depth analysis </li></ul><ul><li>Make sure results are repeatable – unicorns are non-existent </li></ul><ul><ul><li>Most of your odd results are probably invalid test runs </li></ul></ul>
  11. 11. Questions & Answers <ul><li>Thank you. </li></ul>

×