Time flies by and Q1 of 2021 has already passed. Our team was busy working on improving Loadero to make it easier to use and provide more insightful testing results to our users. We are proud to announce some long-anticipated updates that were done during the last months, make sure to use them for your benefit.
Welcome to the “A beginners guide to test automation with Javascript(Nightwatch.js)” blog series part 2! If you have missed out on the first part, you can read it here. In this article we will look into the following and as always – feel free to skip to any part you are the most interested in: Code used in this article can be found in Loadero’s public GitHub examples repository here.
Setting a correct increment strategy for load generation is crucial when you are load testing a website or service. It’s especially important to make sure your website will not be bombarded by a huge number of participants all at once. Choosing correct increment strategy helps you organize your test run flow. You are making sure that participants start exactly how you expect. That can be especially useful for WebRTC service testing.
We have set some ambitious targets for 2021 in making Loadero an even better service to help our customers testing web applications easier, write scripts more comfortably and get detailed results reports that can be analyzed quickly for valuable insights about their app’s performance. With the first month of 2021 just ended, we would like to share some recently added improvements to Loadero application.
Countless things should be tested within web applications but among them, one of the most important scenarios to be tested and even load tested is the user login process. User login serves as a medium between providing users with most of the product features and therefore requires careful and thorough testing. If your website allows users to log in, a login page test is necessary. An automated test for this can be easily created for this.
Welcome to the “A beginners guide to test automation with Javascript(Nightwatch.js)”! This is a three-part blog series to kick start writing web UI automation using Nightwatch.js. In the following parts you will learn: Sounds exciting? Let’s get started! Writing a script in JavaScript (JS) and Nightwatch.js, aka Nightwatch (NW), is simple once you get started and this guide will help anyone regardless of their skill level.
November was a big month for Loadero in terms of updates. We were working on the compute units feature for a long time and are very happy that now we provide our customers even more control over configuring test participants. We improved our test runner stability and made some important fixes. We are proud to share what has been updated and are sure that this will help you to run even better tests with us.
Previously Loadero had the same amount of compute power assigned to each participant in every test, but applications that our customers test are different and have different demands for end user machine resources. That is why we added compute units to give our customers better flexibility in test creation. This also allows to run much larger load tests as well as optimize cost of running the tests for the applications that don’t use much compute power.
Loadero customers around the world take quality assurance and testing seriously, we understand this and work hard to provide a cloud-hosted testing service to fit client’s needs. Over the past couple months we added new features and browser support to make sure Loadero users can achieve their testing needs. We are proud to share our latest updates in this blog post.
Have you abandoned a web service, because it took too long to load? I bet you have, everyone does that every now and then with slow applications. There are a lot of services to check load times, but is it the only thing to check about website’s performance worldwide? Certainly not! It is just one thing to check, not the only one. You may have performance tested the service locally and validated that everything works just fine.
