Performance Testing

From Gcube Wiki
Jump to: navigation, search


The main objective of gCube performance testing is to weight gCube services in a properly configured infrastructure, in which the number of data stored are similarly to the infrastructures in production.

The procedure and the testing tool is the same as what is used in functionality testing, extended with additional ability that enables the production of numerical results, describing various aspects of gCube software's performance. During performance test executions, sequences of these numerical values have to be collected and kept for later analysis and also for providing feedback to Developers. These numerical values describe throughput and capacity of the software.

  • Throughput describes the number of completed requests/submissions/transactions per second. In gCube performance testing this measures how many requests/submissions/transactions are finished in each second.
  • Capacity describes the highest number of requests/submissions/transactions per second that can be completed by gCube and the number of concurrent clients that gCube can handle at a certain level of load.

Performance testing needs configurations describing the maximum number of executions per time unit and the maximum number of parallel clients that are expected to be performed without erroneous behavior caused by possible overload of the whole software, or a particular set of gCube services.


The performance testing activity foresees the involvement of the following roles:

  • Testers:
    • responsible for the execution of the performance tests and to submit performance test bugs
  • Developers:
    • responsible for fixing performance test bugs


The execution of SA performance tests requires a gCube testing infrastructure fully functional. A detailed description of the testing infrastructure can be found here