So, I’ve started learning a bit of Go, which seems to be a language in my taste (small, fast and not too high-level), but some things are a little tricky to wrap my head around. Like, me being an old C programmer, happily discovering pointers but then getting confused by not being able to do pointer arithmetics, by pointers getting dereferenced automatically, etc. Or some things around the package system that I haven’t quite grasped.
Tl;dr — We have redesigned the user scenario editor to create a better scripting experience in our web app. You could also use your own editor of choice with the Load Impact CLI. The focus in the Developer Experience (DX) is to create a productive platform for performance testing.
Tl;dr — Load Impact is growing, and one of the challenges with growth is making sure your infrastructure and development cycle mature with that success. This is Part 1 of our series, “The Road to Microservices.” Here’s what we’ll cover:
- Why we decided to make the change to a microservice-oriented approach
- We’re switching to Docker! (Isn’t everyone, at this point?)
- What we expect to get out of these changes
Tl;dr — We just updated our New Relic integration. You’ll be able to find more performance bottlenecks than ever before.
- In the application code or database transactions: Find where you can optimize your web performance
- More metrics means you’ll make better decisions
- You’ll see your New Relic metrics in our graphical interface during live load tests
- If you need help getting started with the New Relic integration, this Support article will help you!
One of our favorite aspects of working in performance and load testing is that we have the privilege of working with great companies across every industry.
Every so often we make contact with a user who’s not only building great products with great success, but someone who really understands the value of DevOps and Continuous Testing.
Tl;dr — We’re hosting a webinar at 1 p.m. EST June 15: “How to Manage Dynamic Values in Your Load Tests.”
- In order to create the most realistic user scenarios possible, you need to include dynamic values
- This webinar will be about an hour long and include a Q-and-A
Tl;dr — We're hosting an Ember-focused meetup at our HQ in Stockholm. The headline of the event is "Building real-world apps in Ember.js in no time" by Filippos Vasilakis.
We have been stuck on DRF (Django REST Framework) 2.2.4 for a long time, and upgrading has seemed like a huge undertaking. It's one of those things that turn into a PROJECT, and every dev meeting has some kind of tired mention of the PROJECT, although there is never time to actually start working on it.
In a recent round of community feedback, the ability to take Postman collections and use them in Load Impact was one of the most-requested features we heard, and here we are — delivering what our beloved users want (and need), once again.
Tl;dr — Your script is basically the brain of your load test. We’re always looking for ways to empower our users to write load testing scripts that provide actionable web performance data. We recently hosted a webinar that shows users how to use our “Advanced Mode” to write better scripts and get better data. In this tutorial, we’ll cover:
- Using our Chrome Extension to create load testing scripts
- Naming conventions in your scripts to make page data easily identifiable
- Why validating your load testing scripts is absolutely essential
- The importance of sleep time in your scripts