Loadium

Zeyneb Betül Yılmaz
5 min readDec 28, 2020

Hello Everyone! Due to the nature of my job, I needed to create some load tests. I usually prefer Jmeter, but I had a hard time when it comes to the exporting some reports. Therefore, it was the time for me to learn a new tool. My search finally led me to Ioadium, and when I tried it out, I noticed that this is the tool I have been waiting for.

What is Loadium?

To put it simply, it is a load test tool that uses Jmeter, New Relic, Jenkins, Selenium, and Appdynamics as its base.

There are three basic function.

1-) Create Performance Test

2-)Configure Performance Test

3-)Run Performance Test

First of all, we come across the screen below.

Loadium

1-New Test: This option allows you to run a JMeter Test, Gatling Test, HTTP Test, Webdriver Test and Convert to JMX based performance test projects. The most important option that works for me here is Convert to JMX. Because I already had postman collections, so I could import them immediately.

Project Screen

2-Projects: This option allows the tests to be grouped.

Test Screen

3-Test: This option lists all performance test projects you have created.

Running Test Screen

4-Running Test: This option shows your active tests.

Now we are ready to create the first HTTP Test for our company’s website.

Creating HTTP Test

HTTP Test Screen

Creating a HTTP test is a quite straightforward process. First you should choose Create HTTP Test option on main screen. After then there are three basic steps to create an HTTP test.

Test Setup screen allows user to create POST, PUT, GET and DELETE request via web editor. Every HTTP request type has its own configuration screen as follows:

HTTP request type has its own configuration screen as follows:

· Name: Name of the request.

· URL: URL or End-point of the service. Note that Name and URL are mandatory fields that should be entered for every HTTP Test.

· Response Timeout, Connect Timeout: Since they are not necessary for every request, these fields are optional in case you are not sure what to do with them. If they are given some specific values, they will be used as an assertion for the request, and if those values are seen during execution of a test, request will be marked as failed.

· Header name, Header Value: These fields are also optional and must be set according to your request

I choose to give the name of BCFM Test here, you can choose whatever you want though. For URL we entered https://www.bestcloudfor.me/ . Since our request is GET, as you can see GET is marked. For now, we do not require Response Timeout and Connection Timeout, therefore we are leaving them blank.

Now it is time to configure our test.

· Engine Count: Using this parameter, you can create engines on Loadium’s server aligned with its subscription type. The parameter is 1 by default, but you can change your subscription type by going to the web site.

· Thread Count: With this parameter you can change number of threads that can be created in each generated Engine. Maximum thread count per engine is 500 by default.

· Ramp Up Time: This parameter lets you specify the duration required for all Threads to start. For example, if you have 500 threads and 10 seconds ramp-up time, this means that in each second, 50 threads will be generated by Loadium.

· Iteration: This parameter sets the number of iterations for each thread to be executed in the test scripts.

· Duration: And finally, this parameter defines the test time for Loadium to execute. As you can see in the figure above, you can use textbox, and sliders to manipulate these configurations.

Significant Notes: Test execution time of a script is defined by Duration or Iteration parameters, whichever comes first. In case not all iterations are completed during the period of “Duration” time, test execution will stop anyway. Same rule applies the other way around, meaning that if all “Iterations” are completed before “Duration” time, test will again stop.

I want to focus on tests menu in this section.

When we click on an existing test, we can see when it was last run and its test status.

Summary Report: This screen shows KPI’s such as

· Total Hits

· Total Throughput

· Average Max Response Time

· Average Response Time

· Percentage Error

· Total Response Time

· Total Error Hits

· Average Min Response Time

· Average Max Bandwidth

· Average Latency

Test Screen

When we click any of them, report event expands as well.

Overview of Test Screen

We can see the Test Status, Response times and even time intervals, just like in new relic.

Similarly it is possible to see the errors and received data.

Graphic Screens

We can enlarge part of it and even download it as well.

Graphic Screens

As for response codes;

Response Code of Screen

And finally, there is a Logs tab that we can use to display test logs.

Logs of Screen

In this blog, I tried to examine Loadiumdan as best as I can. I hope you enjoyed it as much as I did. I hope we can meet in our next issue. Farewell! 😊

--

--