Scalability testing

One example is if a web page can be accessed in a timely fashion with a limited delay in response.

For example, if you have 100,000 new visitors, it's not just access to the application that could be a problem; you might also experience issues with the database where you need to store all the data of these new customers.

[5] The environment should be constant throughout testing in order to provide accurate and reliable results.

[6] Alternatively, if measuring system statistics such as memory or CPU usage over time, this may have a different graph that is not proportional as users are not being plotted on either axis.

Once data from all stages is collected, we can proceed to plot the results using various graphs tailored to the specific variables and metrics being analyzed.

In Figure 1, we can see a graph showing a resources usage (in this case, memory) over time.

The graph is not proportionate but can still be considered a passed test as initially there is a ramp up phase as the system begins to run, however, as more users are added, there is little change in memory usage.

In figure 2, we can see a more proportional increase, comparing the number of users to the time taken to execute a report.