A method for managing a performance for at least one use case in a software application, the method comprising: - executing, for a first instance of execution, 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; - collecting first performance metrics pertaining to the first instance of execution of the given use case; - executing, for a second instance of execution, the plurality of statements on the target database; - collecting second performance metrics pertaining to the second instance of execution of the given use case; - comparing the first performance metrics and the second performance metrics to determine at least one difference therebetween; - executing at least one alarm action when the at least one difference is greater than a predefined threshold, characterised in that the at least one use case comprises a plurality of use cases, and wherein the method further comprises: - enabling, via an interactive user interface, a user to add a set of configuration rules for generating an alert and/or for breaking a build of the software application in a case of a failure of at least one critical use case that is important for successful performance of the software application from amongst the plurality of use cases; and - employing the set of configuration rules for testing the performance of the software application. - executing, for a first instance of execution, 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; - collecting first performance metrics pertaining to the first instance of execution of the given use case; - executing, for a second instance of execution, the plurality of statements on the target database; - collecting second performance metrics pertaining to the second instance of execution of the given use case; - comparing the first performance metrics and the second performance metrics to determine at least one difference therebetween; - executing at least one alarm action when the at least one difference is greater than a predefined threshold, characterised in that the at least one use case comprises a plurality of use cases, and wherein the method further comprises: - enabling, via an interactive user interface, a user to add a set of configuration rules for generating an alert and/or for breaking a build of the software application in a case of a failure of at least one critical use case that is important for successful performance of the software application from amongst the plurality of use cases; and - employing the set of configuration rules for testing the performance of the software application. - enabling, via an interactive user interface, a user to add a set of configuration rules for generating an alert and/or for breaking a build of the software application in a case of a failure of at least one critical use case that is important for successful performance of the software application from amongst the plurality of use cases; and - employing the set of configuration rules for testing the performance of the software application.