In DevOps, Collaboration & Communication is Key

Posted by Grant Engle on Feb 10, 2016

tl;dr — Load Impact loves DevOps, so we optimize our performance testing application with DevOps in mind.

  • Easily share results
  • Invite team members to run tests, script user scenarios and view data
  • Organize tests into projects to keep everyone on the same page

 DevOps, Continuous Delivery, Continuous Testing and all of the other “Continuous-es” you can name in software development stress communication and collaboration — and for good reason.

When it comes to performance testing, we know Continuous is the way to go, and we give developers the right tools to test early and test often on their mission to create great software.

So, it’s only right that we also make communication between teams easier, too.

Our latest feature update includes something that will greatly help testers share results with their teammates and organizations.

Results View State Persistence

When you share your test results with someone else, they’ll see all the metrics you’ve overlayed in your dashboard. For instance, if you added a throughput metric, such as “Requests/s” or “Bandwidth” and want to share a correlation to VU Load Time or VUs Active, those will appear in your shared test results, too.

Results_View_State_Persostance.png

We’ve seen firsthand that teams are sharing more performance testing data with each other than ever before, so this update is going to make communication much easier for those DevOps teams.

Customer feedback has led us to continue innovating ways to make sharing data easier, and the addition of Results View State Persistence is just our latest move. 

Team Members

We released our Team Members and Projects features in late 2015, and it was widely adopted by a large percentage of our awesome users.

Adding Team Members to your Organization in Load Impact is the first step in sharing results, but team members can also script load tests, upload data stores and create user scenarios and even run tests.

Also, account owners can add different team members to different Projects because we all know not everyone is always working on the same things — especially in larger companies and in the case of consultants.

Sometimes two (or more) heads are better than one when it comes to planning and executing load tests, and our users have definitely validated that idea with the way they’ve been using the new Team Members functionality.

After all, “performance testing is a team sport.”


 Learn more about Team Members and Projects from our Customer Success experts. Give us 15 minutes of your time, and you'll be empowered to take charge of performance testing in your organization!

Talk to Customer Success


Projects

Projects is our little way to help keep you organized.

Whether you’re the lone tester at your organization working on a hand-full of projects, or you’re a consultant juggling several companies in your  portfolio, our Projects functionality helps you folder-ize your work and keep you organized and efficient.

Much like Team Members, our subscribers jumped at the opportunity to start organizing with Projects — maybe because we’re always listening to customer feedback, and that’s how we got the idea in the first place!

Topics: DevOps, continuous testing

Recent Posts

Popular posts

Posts by Topic

see all

Subscribe to Email Updates