• Execute, for a first instance, a plurality of statements pertaining to a given use case on a target database, the plurality of statements being a part of the software application
• Collect first performance metrics pertaining to the first instance of execution of the given use case
• Execute, for a second instance, the plurality of statements on the target database
• Collect second performance metrics pertaining to the second instance of execution of the given use case
• Compare the first performance metrics and the second performance metrics to determine at least one difference therebetween
• Execute at least one alarm action when the at least one difference is greater than a predefined threshold.

Devaten’s tool analyzes and stores performance metrics from all executed test use cases and shows them on a dashboard for each case. Load testing or batch run testing of use cases like these, during development rather than after release, a lot of time and money can be saved. “These cost factors come into play in a big way when the database is at least 10 gigabytes in size. That’s where IT projects can save 10 to 20 percent in cost by using our tools,” Larkela says.