OctoPerf's report engine provides many graphs to sort and presents test metrics in a comprehensive way. We've tried to improve it over the years so that you can access critical information very quickly. But requirements vary from one project to the other.
In this post we will look at how you can configure the report to show your preferred metrics, and also all the shortcuts you can take to achieve this goal.
The best example is the Report summary, it allows you to navigate between all the items in a few clicks:
You may have spent a considerable amount of time configuring Postman requests for your in-house API tests, and you wish to use them without having to create them again from scratch on Octoperf.
That's one of the many situations where Octoperf's compatibility with Jmeter is going to come in a handy.
Warning
A new and faster way to import Postman Collections has been implemented in Octoperf.
When we think of performance testing we normally think of thousands of requests with thousands of users generating huge volumes on our application under test or increasing the load until the application under test fails or runs out of resources.
This is not a good approach when determining load for your performance tests for several reasons and can in some cases render your performance testing meaningless.
This post will outline some of the pitfalls that are commonly made when it comes to generating load and will look at ways to suggest improvements to your approach to load profiles.
JMeter has many plug-ins and downloadable JAR Files you can use to support your testing, it is also possible to write your own custom Jar files and use these as well.
Why would you want to do that, you may say, well whilst it is unlikely that you would need to create anything too complicated.
You may feel the need to create utilities to support your own in-house performance testing or just something to make your testing process easier.
We could easily write a custom Jar file to push the results of test run to any reporting tools your organisation uses, if they expose their API's, at the end of the test execution cycle.
Alternatively, you could write something that sends your results to a mail server or web server for the purposes of results distribution.
For the purposes of this post lets imagine a situation where your company has a dashboard technology that displays the status of development builds or testing progress through a series of APIs, there are many examples of these type of status boards and they are common in many technology departments.
And let’s write a JAR file to output our JMeter test results in the form of JSON which can be sent to this imaginary endpoint we will then use the Custom Class we create in a JMeter test script.
Here we are for yet another new release of OctoPerf. We've actually released two minor versions since the last update post, but this time we will also release a long awaited feature, Microsoft Azure on demand load generators!
We kept it in our beta version for a while since we wanted to be absolutely sure it can be used for proper testing. We are quite satisfied with it at the moment, but note that the agent startup time is much longer on azure than on other providers, you should expect to wait a few more minutes if you are using it.
Of course we also have other new and exciting features to share, so let's dive into it.
As stated in the introduction, you can now select Azure load generators from the locations tab of your runtime profile. This opens up a lot of new locations and will help you test your applications under even more realistic conditions than before.
Of course it comes with all the usual features like retry on agent startup failed and load generator monitoring live during the test.
