Disruptive Functional Testing

Happy to have delivered a presentation at @Sibos 2017 Toronto 

The operators of complex back office and post-trade systems interconnected by SWIFT and other communication protocols are trying to keep pace with the front office technology advances, rising data volumes and changing regulatory landscape. The industry actively adopts flexible development methodologies to speed up the software delivery process. What aspects of software quality are not covered by regular performance / failover testing and the agile development life cycle? Disruptive functional testing is a way to prepare your mission-critical infrastructure for any challenges the future may bring. Ideas for this presentation are drawn from our work with LCH, T2S, clearing and settlement systems worldwide.

What is the main difference between incumbent and disruptive? Incumbent means something you already know and expect. Disruptive is when we encounter new things that will re-define what we already know.

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. 

The goal of disruptive testing is to find defects that are unlikely to be found if testing is done with other methods. We see ourselves as a mining operation extracting defects hidden in complex scalable technology platforms.

I am going to cover some of these slides in more details in consequent posts

Thank you