The traditional approach to performance and stress testing is:
Define objective >Create test>Run test> Analyse results>Go back to #2 and repeat until clear conclusion
But modern load testing tools such as Validata Performance Tester have rich ‘dynamic test control’ functionality which allows the tester to change the test at run-time. For example, increase the number of virtual users, vary the number of virtual users or keep them at a constant rate or start monitoring of performance indicators (Memory, CPU, HardDrives, Network..etc) of all servers in the infrastructure during the whole period of execution of Performance testing. By combining these data with the data of the execution of test cases, a full picture of how the system is performing under certain loads will be available at a glance.
‘Dynamic test control’ enables a very different approach to performance and stress testing which is far less structured. A tester can now run up the system-under-test, start the load testing tool, until they have achieved their objective and clearly understood the system behaviour. This more flexible approach to load testing is increasingly popular, with almost 50% of our customers’ testing being done this way, but is that a good thing?
‘Dynamic test control’ was primarily introduced to deal with limited test windows against production systems. Performance and stress testing, for various reasons, often has to be done against the production system, and obviously no-one will allow testers to do this while their customers (or employees) are also trying to use the system. So testers are often given a short window (usually in the middle of the night) to do their testing. In such environments a tester needs the quick flexibility that ‘dynamic test control’ gives to adapt to new information – and ‘dynamic test control’ is a very good thing. Retesting different versions of the application or after patches are applied is very important, in order to understand if the system is performing better or worse in all aspects.
Validata Performance Tester is using adapters which have built-in support for the specifics of Temenos T24 transaction execution – commit, validation, authorization, reversal, etc. There is also built-in support for T24 enquiries, hot fields, re-key functionalities, default values, etc. The lead time required to fine-tune a performance testing application to test T24 web interface is set to none.
The tool uses an integrated data loader functionality that guides the user and automatically creates the T24 test data. By leveraging the dynamic data metadata model and dynamic parametirisation of test cases, the cost of preparing and maintaining performance tests for execution on a newer version of T24 system, is significantly reduced.
Tagged under
Related items
- CRM Testing: Ensure quality for optimal customer experiences
- Integrating Continuous Performance Testing into your DevOps process
- Combining agile practices with performance testing
- Why should Performance Testing be high on the agenda?
- Fine-tune your Temenos T24™ Performance with Validata Performance Tester!