Software is available everywhere we look. Any machinery we use associates itself with code that controls the way it works. Software teams work to write these applications, and many software developers band together to work on a single project. They keep working on ensuring that the application should work just as designed for the end-user when they deploy the code.
In financial services, data is essential for storing product information, capturing customer details, processing transactions and keeping records of accounts; the relationship between products and their underlying data has always been symbiotic. A significant amount of data infrastructure is static, fragmented across data silos or based on legacy platforms. This has created an impedance mismatch between products and the underlying data.
Introduction Once upon a time documentation was one of the most important aspects of Quality Assurance and this was not limited to the functional test efforts but the non-functional testing as well. We spent days, weeks, months even creating Performance Test Strategies, Approaches, Plans, Test Case, Completion Reports etc. Most of these documents were required before any automation could be written and before a sensible performance testing framework could be considered.
