Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Post Trade Complexity and Disruptive Testing

Post Trade Complexity and Disruptive Testing

Marina Kudryavtseva, Senior QA Project Manager, Exactpro

EXTENT Software Testing and Trading Technology Trends Meetup 2018

5206c19df417b8876825b5561344c1a0?s=128

Exactpro
PRO

June 20, 2018
Tweet

Transcript

  1. Build Software to Test Software exactpro.com Post Trade Complexity and

    Disruptive Testing Marina Kudryavtseva 20th June 2018
  2. 2 Build Software to Test Software exactpro.com Three principles to

    test technology platforms NO TRUST FEAR BEGGING NO NO
  3. 3 Build Software to Test Software exactpro.com What is the

    main difference between incumbent and disruptive?
  4. 4 Build Software to Test Software exactpro.com Components of complex

    Post-Trade systems
  5. 5 Build Software to Test Software exactpro.com Key challenges in

    providing QA for Post-Trade platforms
  6. 6 Build Software to Test Software exactpro.com Get Off the

    Hook With incumbent testing, you are on the hook of pre-conceptions of how your system under test is supposed to work. It's only when you do disruptive testing that you really gain new knowledge about the system and learn from it.
  7. 7 Build Software to Test Software exactpro.com Holistic Integrated Automation

    Test Framework
  8. 8 Build Software to Test Software exactpro.com Agile Transformation Most

    of the large financial sector organization are going through an Agile transformation. Waterfall Model Agile Model
  9. 9 Build Software to Test Software exactpro.com What Agile Development

    Should Be… and Not NOT LIKE THIS LIKE THIS
  10. 10 Build Software to Test Software exactpro.com Testing Critical Infrastructures

  11. 11 Build Software to Test Software exactpro.com Testing Critical Infrastructures

    Safety Rule #1 with Submarines: don't open portholes when underwater!
  12. 12 Build Software to Test Software exactpro.com Testing Critical Infrastructures

    Safety Rule #1 with Submarines: don't open portholes when underwater! Functional testing: iterate through a finite number of scenarios to prove that the porthole won't open Non-Functional testing: iterate through a smaller number of scenarios to prove that it won't open by brute force
  13. 13 Build Software to Test Software exactpro.com Testing Critical Infrastructures

    Safety Rule #1 with Submarines: don't open portholes when underwater! Functional testing: iterate through a finite number of scenarios to prove that the porthole won't open Non-Functional testing: iterate through a smaller number of scenarios to prove that it won't open by brute force Disruptive testing: 1) iterate through a huge number of random diverse scenarios under load to prove that it won't open
  14. 14 Build Software to Test Software exactpro.com Testing Critical Infrastructures

    Safety Rule #1 with Submarines: don't open portholes when underwater! Functional testing: iterate through a finite number of scenarios to prove that the porthole won't open Non-Functional testing: iterate through a smaller number of scenarios to prove that it won't open by brute force Disruptive testing: 1) iterate through a huge number of random diverse scenarios under load to prove that it won't open 2) open the porthole
  15. 15 Build Software to Test Software exactpro.com Thank you!