There are many programming languages that can be used for test automation. Loadero supports 3: Java (TestUI framework), Python (Py-TestUI framework), and JavaScript (Nightwatch.js framework). Test automation with Java is quite popular, in fact, the second most popular framework of choice when it comes to writing test scripts in Loadero is TestUI.
When using a testing tool, it is only logical to trust its results. And the more well-known the tool is, the more trust we put in it. Furthermore, how could we know it is wrong? After all, who is in a position to judge the judge? This phenomenon is particularly true in the load testing community, since the field is still something of a niche among the testing world. Finding deep-dive studies about the actual technical aspect of load testing is difficult.
In Loadero we always look for ways to improve our product and make it more robust, secure, and maintainable. As we add more features to our product, the complexity of our code base increases and it makes it more difficult to add or refactor the code without introducing regressions of the functionality. Since our frontend was written in plain Javascript and React, there was no way to ensure type safety of passed data between components and functions.
LoadFocus now provides easy testing for services that are using OAuth authorization (we support OAuth2.0 as OAuth1.0 was retired in 2012). We support all the OAuth 2.0 grant types: For testing a service that is behind a login (that has OAuth authorization) the only thing the user needs to do is: The call to the authorization server will be done only once before the performance testing of the API endpoints starts.
It’s been a while since we published our latest product updates, but the work on Loadero wasn’t paused. Our team was busy working on the newest features to make your performance testing with Loadero more convenient and effective.
When developing web applications, one of the important things is to provide smooth accessibility of your product to the clients. But that is not an easy task to accomplish as several factors come into play. Software testing requires coverage of many different devices, environments, and conditions. We in Loadero provide features to use different browsers, run tests from different locations, set different fake media for webcam and mic simulation, etc.
There are various reasons for running Python browser automation tests locally, the most common one for us is saving time. Loadero test runs usually take no more than 5 minutes to initialize and start execution but can reach up to 10 minutes or more depending on how busy is the test run queue. To increase the speed of development, it’s often quicker to create the test script on your local machine and then run tests on Loadero.
April was a busy month with some significant improvements made to Loadero. While most of them aren’t really visible in the tool itself, they make Loadero work better and allow to use it even more efficiently. Here’s a list of the main updates in Loadero this month.
Loadero is a SaaS (software as a service) for testing web applications and our main target is to provide a powerful tool to our users, so they can create load tests, performance tests, and WebRTC tests for their needs. But sometimes a proper tool is not enough to execute tests: some companies don’t have enough manpower, others might not have enough expertise in the QA field, yet testing is required for every web application.
