Heroku Integration Bug Fixed


We pushed a change recently to our Heroku integration and accidentally introduced a bug. In some cases, the provisioning process would fail against our API with an error of “Could not communicate with vendor, please try again later.

We have published a fix to the integration and it should be working properly again. We apologize for the inconvenience. Please let us know if you have any other issues, and thank you for using Blitz!

New versions of Blitz for Chrome and Firefox

We’ve just released new versions of Blitz for Chrome and Firefox. If you signed up using our registration form you can now login without a problem. We’ve also refreshed the designs to match our website.

Grab the new extensions to start rushing and sprinting your app from around the world in the easiest way possible: Blitz for Chrome and Blitz for Firefox.


FirefoxLearn more about browser add-ons at https://www.blitz.io/docs/browser-add-ons/chrome/ and https://www.blitz.io/docs/browser-add-ons/firefox/.


3 Steps To Create A Robust App With Load Testing

Robust App

So you’ve heard about load testing and you know it’s the right course of action, but how do you use load testing effectively to get the results you need for your app? You’re in luck, because today, we’re talking about building up a Robust App; and, we’ve broken it down into some simple lists to help you get started.

What Makes Up A Robust App Anyway?

Here are 5 ingredients that are must-haves for any app in today’s online experience:

  1. Fast Load Time
  2. Scales to the target audience size and beyond
  3. Optimal Performance
  4. Always Available
  5. Minimal to No Downtime

A truly robust app will wield all of these components in addition to providing fantastic content, and superior services. We want to help you build just such an app, because thoroughly load tested apps make the world a better place. Below we’ve provided some steps to help you do just that.

3 Steps To Perfecting A Robust App

We see a consistent pattern of testing with our Blitz users, and we can break it down to a simple three-step method that will get your app running its best under stress. These steps will help you strengthen your app- so when your audience goes through the roof, your app won’t crash through the floor. Here’s the formula:

1. Deploy
Deploy a preliminary version of the web app to staging, and setup your tools.

2. Rush
Run a Rush consisting of your target number of concurrent users. This is a load test on the rough draft of all of that hard work you’ve put into building your site, so on your first couple of Rushes, your site is likely to fall over when Blitz gives it a push, so…

3. Fix
Dust it off, and take this opportunity to fix any outright issues that caused the fall of your app during this round of testing and…


Now that you’ve located, assessed, and corrected the problems with your app, you can repeat this 3 Step Method: Deploy, Rush, and Fix, until your app is well above your acceptable threshold of performance. With each pass, you can eliminate issues, and laser focus optimal site performance with each round of tests. We cannot stress enough how important it is test during this stage before it goes live. More on this topic here: Stress Your App, Not Your Users

Rush your site with Blitz to build a better app today!

Stress Your App, Not Your Users


With intense loads of traffic parading through your site, stress will manifest itself somewhere. Hopefully, not in between your user and his chair. There are many reasons to test your app’s performance before it goes live, but your user is the most important.

Stress Your App

Remember our post about building a Robust App? We talked about the 3-Step method to building a stronger app. Now we’re here to tell you to begin using that method as early in your development process as possible.

We’re developers here, but imagine if car manufacturers didn’t test their vehicles before they let their customers use them? You can imagine some of the nuisances the new car owners might experience: failure to start, failure to go, engine failure, failure of locking mechanisms, break failure… etc., and you would expect a car manufacturer to have some kind of check in place to make sure that all of those important details operate properly before handing over the keys.

For a car manufacturer, it’s more than just customer experience, it’s a safety issue. As for developers, the same thought process still applies. Handing over the keys to your site when you haven’t checked to see if it might crash? Not a good idea.

Don’t Stress The Users

The users are your audience, your bread and butter. They pay money and time for the content you provide, and you owe it to them, and yourself to “kick the tires” before presenting your app to the public.

You may have a top-notch marketing team that’s successfully bringing visitors to your site in droves, only to have a high bounce back rate due to performance issues. You may be silently thinking to yourself, “We don’t have the best performance, but our audience loves us so much that they’ll be patient with our slow loading, off and on again content…,” and you would be sadly mistaken. Hopefully (at least I would like to think), this isn’t you.

You already understand from personal experience: users hate waiting, they hate having to try multiple times to make one thing happen, and they have absolutely no tolerance for things that crash or are just plain unavailable. We use the internet. We get it.

There is hope- with load testing, comes the ability to spare your users the agony of waiting to reach your content, by helping you make sure it always gets there on time.

Alleviate user stress today! Performance test with Blitz, and load test away your load time.

Benefits Of Load Testing Your App For Black Friday 2014

Black Friday

Black Friday is swiftly approaching, along with promotional offers, record blasts of traffic, and unprecedented online sales for your business. At least, that’s why we’re in business, right? Well, we’re here to make sure your app stays in business as it faces your swarms of adoring customers. Have you already load tested your site? Great! Have you tested it under the assumption that bargain shoppers will give you more than you bargained for this shopping season? It’s time to test again, and here’s why:

Continue reading

Benefits Of Testing From The Cloud

Load Test

So, you want to see what it’s like to have a large amount of visitors hit your website… How do you test that? You could go buy a bunch of expensive hardware, and install some cumbersome software, or you could wing it and see how your site performs under the stress… Ridiculous? We thought so too.

Today, we’ll be talking about some advantages of load testing from the cloud.

The feeling of relief, A light breeze on a warm day, a fire on a cold night, the sensation of a burden being lifted. This is the experience of the weary developer who discovers all he needs to have in order to load test his website is a login, password, and an accurate test configuration. No bulky, harddrive consuming software. No additional server room in the back to provide him with horsepower.  And, there’s the added benefit of actually being able to test the capacity of his site against visits from people all over the world, not just unrealistic simulations from his luxurious internal network.

Load test your site with Blitz today and find out if your app can handle your audience.

Here are the benefits of testing from the cloud:

Testing your application from your own network is testing in a vacuum. Even if you can generate the traffic, your simulation is benefiting from the direct-line access you’d expect from being on-site. The real-world traffic your site will encounter will originate from multiple locations, sometimes locally, sometimes nationally and even globally, but your audience will most likely not be originating from your internal network. Testing from the cloud gives you the benefit of a more realistic scenario in which your simulated load is actually originating from multiple locations and making its way to your endpoint to provide the most realistic test results possible.

Testing from the cloud not only provides more realistic results, it’s a simpler solution for your company moving forward. You use cloud service instead of creating an in-house solution, acquire the best possible test results, and can focus on the bigger picture of reaching your audience and delivering content and making money.

You can schedule your tests to be recurring, at certain times, and push different amounts of traffic. Need to know how your app responds to 1000 users at 2am in your time zone, but don’t want to be sitting in the office to push the “run test” button? No problem, that’s what scheduling is for. With cloud-based testing, the world is at your fingertips, and you can set it up to test without you.

In addition to timing your tests, you can set up your tests from anywhere. Because this cloud based service is online, your login and password will get you into your test configurations, whether you’re at the office or not.

These are a few of the major advantages of testing from the cloud, and we hope you have found them helpful.

Sign up for Blitz today, and discover first-hand why load testing from the cloud is the best solution for your web app.

Give Yourself Credit – And Get Your Tests Rolling

Sprint and Rush

You have some tests to run and a limited amount of credits to make them happen. How do you best leverage the Sprint and the Rush? What is the difference between the two, and how are they going to help me prepare my web app for what’s ahead?

When you’re done reading this article, you’ll be able to load test your site with confidence, knowing that you’re getting the most out of your Blitz credits.

There’s always that nervous tension that comes about whenever you’re about to spend something of value. When economic strings are tied to a task, you want to ensure that you’re getting the most mileage out of each action you take. No one wants to look back at a job and say “I could have done better,” or “I wish I had done that differently.” We understand that here at Spirent, and we want to help you get the most Blitz for your buck.

How To Best Leverage Sprints And Rushes

Now we’re going to give you a tactical strategy for attacking your website with virtual users from multiple locations all at once to test your scalability. Ready? Let’s go:

Step One: The Sprint

Sprints are like having your own personal reconnaissance team. Use the Sprint to check to see if your endpoint or resource is valid, and that you’ve configured your request, request headers, and cookie correctly. In short, you can use the Sprint, free of charge, to make sure your Rush is ready for take-off. The Sprint will help you ensure your credits will be of good use when you spend them on a Rush.

Step Two: The Rush

Now that you have your settings configured and functioning properly in your Sprint, Rushing is as simple as hitting the “replay” button. From here, you will be able to change your Sprint to a Rush and adjust your settings to the standards of your final test. You can run your configured Rush as a one-time load test, or schedule it to recur on a regular or irregular basis.

Step Three: The Results

Now that you’ve laid the groundwork with a Sprint, hit “replay,” and run a Rush on your web app, it’s time to take a look at the results. After you’ve run your test, you can see in-depth analytics on the performance of your web app under the conditions of your test(s).

By tactically Sprinting first and Rushing second, you can “look before you leap” and ensure that you squeeze every last drop of Blitzing power out of those wonderful credits. Get the results you’re looking for efficiently, and Sprint before you Rush.

Running low on credits? Pick up more credits here.