System Under Test (SUT)
Perfana’s subscription model and pricing are based on the number of Systems-Under-Test (SUTs) that are analyzed using Perfana. While others primarily use metrics like vUsers or VUserHours, we believe that this model goes against the objectives of Perfana and especially its users.
Perfana aims to make performance testing and performance engineering possible as early as possible in the software delivery pipeline. This allows for faster feedback to developers and gives them more responsibility and ownership.
Therefore, Perfana uses the number of SUTs as its basis, so that users can test as often as they want at a fixed cost.
A SUT is any system, or system of systems, that is tested and analyzed under one name using Perfana.
Possible forms of a SUT:
1) A microservice with an API, possibly with “mock” dependencies.
2) A collection of microservices, working together and interdependent.
3) A front-end application with multiple backend microservices and multiple data sources.
This definition gives users the freedom to decide for themselves which form best suits the organization and development model: “large-scale performance tests with a minimum of defined SUTs” and “a collection of small SUTs”.
Example: 6 Systems-Under-Test (SUTs) are defined
- In the CICD-TST environment, a performance test and analysis are performed for each of the applications/services, for example, with each commit. These are 5 different SUTs, despite the fact that multiple components or instances are involved in some.
- In the ACC environment, a performance integration test takes place. Although each of the 5 SUTs from the CICD-TST environment is tested again here, they are tested and analyzed together as a whole in this case. Therefore, 1 SUT.
