Quite often we get requests to provide support to migrate tests from the testRTC testing tool to our service. We try to provide support to our users to help make this transition as easy and flawless as possible. To ease the process further for other users with similar needs this blog post was created.
This article shows some of the complexity that the k6 cloud backend handles when you run a k6 Cloud test.
Hi there, Here at k6, we’re constantly shipping new features to help our users get the most out of k6. In case you missed it, here’s a roundup of all the k6 and k6 Cloud news, updates, and improvements you should know about.
In this Postman load testing tutorial, you'll learn how to run a large scale load test in Kubernetes using your existing Postman collections. Because HTTP services don't have a graphical user interface, it's common to build collections of requests using Postman during the development process. These collections are useful for running quick functionality tests as you develop each endpoint. However, as the service grows you eventually need to test it in a more realistic way with larger volume. This is called a load or stress test. Speedscale is a Production Data Simulation Platform that includes this stress/load testing capability out of the box.
At a former employer, my Vice President of Engineering and Operations had a reputation for his language. He also had a reputation for his deep passion for things like site availability, incidents, downtime, and almost anything related to making sure the company's website was up and running, and especially that the end users were having a good experience using it.
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.
I'm the technical writer at k6. If you're on this site, you probably know what k6 is. But, to reiterate the essentials: When I started five months ago, I knew I had some work to do because: Really, my "professional programming experience" culminated in some shell two-liners. Fortunately, the k6 team gave me a set of challenges to get up to speed. In this article, I go over the eight challenges the k6 team gave me and present the ways I solved them (I don't promise elegance).
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.
