The goal is to detect problems, that cause performance issues with iTasks application running for a long time. This is done by measuring response time and memory consumption of a number of stress tests. Examples of stress tests are starting a large number of sessions and having a task with a large recursion depth.
The results of stress tests should be visualised to make it easy to spot issues, i.e. an increase in response time or memory consumption that is larger than one would reasonably expect for the test given.
The results of stress tests should be stored, such that new results can straightforwardly be compared with previous ones. This gives a mean to quickly measure the success of optimisations. Additionally, this helps to detect performance issues, accidentally introduced.
Finally, stress testing should be integrated into the automated testing process, such that modifications with a negative impact on performance, are detected early.