Skip to content

Load Testing Blog

Collaborative JMeter Testing

Performance Tester Teams struggle to share their work when using JMeter. Sharing JMeter projects can be a tedious task. OctoPerf solves this issue by allowing Teams to share their load tests.

Workspaces allow teams to share JMeter projects (Virtual Users, Scenarios and test reports). A Workspace is a collection of projects accessible by one or more people with different rights.

Workspace members have different rights depending on their role:

  • Administrators has access to everything,
  • Testers can do anything except managing the workspace members,
  • Viewers can only view the content of a workspace.

OctoPerf becomes a JMeter Performance Center for QA Testing Teams who want to scale.

Load testing without think times?

There are a few key parameters that you must control in order to launch relevant tests. I believe think time is one of those, and it is so often overlooked that I would like to take some time to highlight what it stands for. Any quick search on your favorite search engine will tell you that think times in load testing are meant to reproduce human interaction time. As a load testing script is usually composed of a list of requests, it's easy to understand how replaying them with think time is one more step toward a realistic behavior. But this doesn't mean it's easy to understand how to use and configure it.

JMeter vs OctoPerf

Today's blog will be a short video to demonstrate how quick the recording process is with OctoPerf when compared to JMeter. We always say that OctoPerf makes JMeter easier from the design to the test results, this video will show you how the recording process can be done twice as fast with OctoPerf.

And that is not counting how we cut the complexity of the recording process to a few clicks compared to all you have to do with JMeter.

With OctoPerf:

  • From your browser press F12 and activate persistent log
  • Navigate
  • Export as HAR file
  • Connect to OctoPerf and import the HAR file

Upgrade to AngularJs 1.6

When we started developing our load testing solution we had to choose a technology to create the UI. Most of us had previous experiences with GWT or Vaadin but we were not satisfied with it. It took us too much effort to create a sketch of the application and it didn't even look good.

So, we gave a try to AngularJS, even though none of us knew a bit of JavaScript. It felt really productive and a few weeks later we had a nice first version of OctoPerf that could start performance tests and display reports.

Three years later we added lots of features to our load testing solution and the code base reaches almost 10K lines of JS. In the meantime, Angular2 came out and AngularJS evolved to close the gap.

So, during the past months we took some time to upgrade our frontend to AngularJS 1.6 and to prepare the ground for Angular2: