As outlined in our rebranding announcement post from Feb 24th, today we're disabling access to v4 projects in the LoadImpact web app at app.loadimpact.com (v3 projects will continue to be available until Dec 31st, 2020). All v4 projects, tests, and test results will henceforth only be accessible from app.k6.io. The same login credentials are valid across the two web apps. Rest assured, no data is going away, it's technically an older of two frontends being sunsetted.
If you want to jump straight to installing the marketplace extension, you can find it here. Performance issues can quickly turn expensive. Reasons can vary from unexpected traffic surges, pieces of non-performant code acting as bottlenecks, or misconfigured network components. Integrating load- and performance testing into your CI pipeline will allow you to know about performance degradations early, in most cases, even before it has any impact on your users in the production environment.
This article demonstrates how to Load Test an application deployed in a Kubernetes cluster, verify that the autoscaling is working, and identify potential performance bottlenecks. When you deploy an application to production on Kubernetes, you'll need to monitor traffic and scale up the application to meet heavy workloads during various times of the day. You'll also need to scale down your application to avoid incurring unnecessary costs.
This blog post is a guide to help you write Gatling scripts in order to load test web applications efficiently. It follows our second Gatling Simulation scripts parameterization article. We will continue to load test a fake e-commerce, and so we are going to improve our Virtual User to make it browse the store in a more humanly way. We start where the previous blog post ended, with a simulation script that uses a CSV feeder and a Regular Expression extractor to visit dynamic pages of the pet store.
In this article, I'll explain how to use a Postman collection I have created to load test our instance of our test API. The process is pretty straightforward, as is shown below. You need to feed your exported Postman collection to our postman-to-k6 converter, and use the generated k6 script to load test your own API.
This new release of OctoPerf brings a lot of long awaited features. This is all based on your feedback, so make sure to let us know what you would like to see in OctoPerf next! Of course we have a few plans of our own for the future, but I strongly believe that a good software can only result from a good collaboration between users and developers.
The principles behind performance testing API’s does not differ from the principles behind the performance testing of any application. Many API’s however are Asynchronous and a valid response from the API does not necessarily mean the transaction is complete which can cause a problem when measuring the performance of API’s. There are however ways around this and we will explore these in this post.
Cypress is one of the best web testing frameworks created so far. With more and more new web development frameworks on the market, it’s harder and harder to find an end to end testing or integration testing framework that would work well in any situation. In the recent years, we’ve seen a spike in web development frameworks, from Angular 1 or Angular 2, to the more popular React and VueJs, to new one like Svelte, and less popular like EmberJs and BackboneJs.
At the end of 2018, Microsoft stated that Visual Studio 2019 is the last version with load testing features. A few months later they formally announced that Azure load testing is closing down on March 31st, 2020. This announcement came as a bomb to the community. But for those who follow this market, the news was not a complete surprise.
In this tutorial, we will look into how to integrate performance testing with k6 in your TeamCity build setup. k6 is a free and open-source performance testing tool for testing the performance of APIs, microservices and websites. TeamCity is a continuous integration and delivery server built by JetBrains.
