This chapter is a portal to the nonfunctional aspect of an application where it uses the Test Studio features for nonfunctional testing. In the general performance testing process, which is delimited by the successive activities of putting performance objectives, expectations, test execution, and results capturing and analysis, Test Studio automates the latter three activities.
So what are the variables that underlie this performance process and which of these do we want to address in this chapter?
For answering this question, let us first establish the criteria for a well-performing application. We are not seeking general principles in response to this question since it is highly bound to the application's contextual factors, such as the criticality of the operation carried out by the user, the potential financial loss, the amount of information that needs to be kept in the user memory until the next operation, and the operation type (whether it is two-sided, such as conversations...