LoadTest Tool for ARAS

ARAS Load Test Tool is testing how the system behaves once simulation of real user interaction.

It is..

• console application (command line tool)
• multi-threaded environment (simulates real work scenario)
• configuration based (connection definition, queries count, thread count, configuration files locations, output log location, test result file location, etc)
• queries with placeholders

FUNCTIONAL POINT OF VIEW

From a functional point of view, we can assume that:
 

Thread = Single User
Query = Action/Click that a user performs on ARAS UI

So if we configure 100 threads that use 500 queries, it will
mean that we will simulate the work of 100 users who click on
actions in ARAS Web UI 500 times.

These users can perform actions simultaneously, so it may be that some actions will be sent to ARAS at the same time - in this configuration.

Additionally, the load test tool can be installed on any number of servers or client machines. This allows the simulation of geographically distributed usage scenarios.

Example: four servers; one each in Frankfurt, Virginia,
London, Beijing; additionally four client machines. Each
machine runs 200 threads. The total test then simulates 8 *
200 = 1600 users

TEST RESULT

In the current Load Test implementation, we are testing how the
system behaves during the simulation of real user interaction.

Load Test answers questions like:

• does the target system handle that amount of users?
• does the target system handle that amount of simultaneous

queries?

• what is the maximum rate of users and queries that the system can handle (without error or with an acceptable error rate)?

CREATING REPORTS

So, in order to create reports based on this data, we would need to:

• perform load tests in a scheduled manner
• compare load test results (with the same configuration) with each other
• use the same machine in compared results (the load test machine may have an impact on results)

We can create a dashboard that presents:

• list of machines/sources where load tests were run
• configuration of compared tests (used threads and count of queries)
• timeline of tests with test result duration in a certain time period