What’s New In Loadero (June 2024)

We are here to deliver another blog post of two months’ worth of updates for the price of reading just one article. These updates will cover changes implemented in Loadero during May and June 2024.

New feature: Test labels

Loadero now allows organizing and categorizing tests in your project through the use of test labels.  You can think of labels as tags for a test, they allow you to categorize tests by different properties, such as “Sanity”, “Audio”, “Load”, and others. In order to label a test, you will first need to create the label in your project first. This can be achieved in two ways.

Method #1: Project settings -> Labels

When you navigate to the “Project settings” tab in the app, you will see a new item on the left sidebar – “Labels”. In this page you can create labels that you would like to assign to your tests. Loadero provides you with 10 color options so that the labels are easier to tell apart.

Adding a new label

Only members with the Administrator role are able to create, edit and delete these labels in the scope of the project. However, assigning them to a test is possible for members with the Developer role as well.

After creating a label, you can then assign it to any tests that you would like to categorize by it. This can be done in the “Tests” tab of your project (or the “Favorites” tab, if the test you want to label can be found there), by clicking on a test’s “…” button for more options and selecting “Assign label”. You can then assign any label that exists in the project to the test. A test can possess multiple labels, not just one.

After you have assigned labels to a test, they will appear at the bottom of the test card.

Tests with labels

Method #2 – Directly through the “Assign label” option

Labels can also be created directly through the “Assign label” window. There is an input field within the window which has two functions. Firstly, it is a search bar, so if your project has a lot of labels it will quickly help you find the label you want to assign by typing in part of its name. Secondly, it allows you to just type in the name of the label you want to create and then press the “Create” button that appears. Upon doing so, the label will be created in the project, the labels available for assigning will be reloaded and you can immediately assign it right then and there.

While this method is quicker, it is only an alternative method to creating labels. Editing and deleting these labels will only be possible in the “Labels” page in project settings.

When creating a label via this method, the color will be selected randomly. But this can be edited afterwards in the dedicated “Labels” page.

More regular invoicing

Loadero has adopted a new strategy for invoice generation. This change does not affect the total cost, only the frequency at which you will be asked to pay for compute units consumed since the previous invoice.

Instead of being charged once at the end of the billing period, invoices may start being generated mid-way through the billing period as well. For example, you may be using an Ultimate plan and you end up consuming 20’000 compute units – an invoice could be generated very soon after instead of only at the end of the billing period. Alternatively, you may be using a Monthly plan – if you consume 20’000 additional compute units to the base amount (so 30’000 in total), then an invoice might be generated following the same logic.

If you’re using a plan where compute unit price is tiered and goes down the more compute units you have consumed, then this tiering will reset only at the end of the billing period. Paying an invoice generated in the middle of the billing period will still preserve the current compute unit price.

If such an invoice is generated, you will not be able to run any more tests until it is paid. Note that if you are using a Monthly or Yearly plan and never exceed the base 10’000 compute units then you will be totally unaffected by this change.

Nightwatch upgrade from 2.5.2 to 3.6.1

We have upgraded the version of Nightwatch.js on Loadero’s side, so now any tests run in a Nightwatch.js project will now be using this newer version. You can go over the framework’s changelog to see what new options this has unlocked for tests run in Loadero. Though we tried to avoid any regressions, some may have slipped through the cracks. If you notice that your tests don’t work the way they used to, please, reach out to us and let us know.

This also means that you should have an easier time writing up a script in a local project and then migrating the script to Loadero. Before you may have experienced issues where something that works locally wouldn’t work in Loadero because something in the script had not been supported by Nightwatch.js back in version 2.5.2. This should not be as much of a concern anymore.

Lastly, and sadly, we have taken note of the fact that Selenium logs in the run report of tests run with Nightwatch.js 3.6.1 are no longer as neatly formatted as before. However, we deemed this a necessary sacrifice to make in order to keep the framework up-to-date in Loadero.

Upgraded AWS instances used in test execution

We have also upgraded the instances that are used for test execution. Our own observations have indicated that across the board a lot of reported metrics in tests have improved because of this. We ran several tests before and after this upgrade and observed drastic improvements in network metrics, as well as significant improvements in FPS and some reduction in the amount of CPU used during tests. If by chance you have observed within the past month that metrics inexplicably improved in your tests – this might be the explanation you were looking for.

UI improvements

Dropdown option sorting. The options list in dropdowns when creating a participant or assert will now be sorted far more intuitively, instead of the lexicographic sort that had been used previously. The previous sorting resulted in some awkward cases where options that didn’t make much sense to be next to each other in the list (such as the G12 compute unit option being between G1 and G2).

Submission via ENTER and keyboard shortcuts: Additionally, we have been shifting to supporting input submission via ENTER instead of having to always click the button. A recently updated example is that when duplicating a test and inputting the name of this new duplicate you will now be able to create it immediately via ENTER instead of having to interact with the button. Lastly, we have enabled keyboard shortcuts to save progress in the test builder, such as Ctrl+S and Cmd+S.

Support for new browser versions

Loadero now allows simulating participants via the following browsers:

  • Google Chrome 125 and Google Chrome 126;
  • Mozilla Firefox 126 and Mozilla Firefox 127.

We look forward to delivering another batch of updates soon!