Noga Cohen is a Sr. Product Marketing Manager for CA BlazeMeter. She manages the BlazeMeter blog and other content activities. Noga focuses on creating technological content in the fields of performance, load testing and API testing, both independently and by managing writers who are developers. Noga has more than 5 years of experience in a wide scope of writing techniques: hi-tech, business, journalist and academic.

Become a JMeter and Continuous Testing Pro

Start Learning

Test Your Website Performance NOW!

arrow Please enter a URL with http(s)
May 23 2018

Are You Ready for Black Friday? 8 Load Testing Best Practices for Your App or Site

Black Friday is approximately six months from now, and this is the perfect time to start preparing your website and application for the expected Black Friday crowds. Hey, your competitors are already doing it.


To make sure you are ready for November 23rd, here are 8 Best Practices for making sure you are ready.



1. Define Your Load Goals from a Business Perspective


To ensure your website can handle the load, you first need to determine what your loads are. You will need to define the number of concurrent users, the hold time or times,  traffic spikes and complex user scenarios. Take into consideration your traffic from last year, the changes in your traffic over the past months, your marketing efforts for Black Friday, any special offers you have that might spike your traffic and your users’ behaviour.


2. Involve the Whole Technical Team


After deciding what you want, you now need to plan how it can be done. Get your technical team together: developers, QA engineers, DevOps, product managers, etc. Get them involved in the Black Friday spirit and share your business goals with them. They are the ones that will be running the tests and preparing your infrastructure, application and site for Black Friday. Get an overview of the current performance status, so you can prepare for the next step - planning the tests.


3. Plan the Tests


Now you can plan how to execute your business goals. Together with your team, determine which tests you need.


Here are the types of tests you can run:


- Load Tests - for understanding system behavior under an expected load.

- Stress Tests - for understanding the system’s capacity limits.

- Soak Tests - for examining the system’s abilities to hold a continuous expected load.

- Spike Tests - for examining the system’s abilities to hold a heavy load that was abruptly and quickly generated.

- Isolation Tests - a repeated test for examining if a known and detected system error or issue previously detected by the same test, was fixed.


Take your business goals as well as your knowledge of where your product performs better and not-so-well, and fit the right tests to them.


4. Choose Your Load Testing Tools


There are different open source tools you can use for load testing, such as JMeter, Gatling, Locust, The Grinder and Selenium (for low-scale browser loads). For a quick guide on the similarities and differences between them, see here. BlazeMeter offers additional advantages, such as larger scalability from multiple geo-locations, it’s a cloud service, it has sophisticated and elegant reporting abilities and it enables work collaboration.


5. Run the Tests


You are now ready to run the tests! Go for it. We recommend that if your system successfully handles your goals - go farther. Know when your system breaks. This could come in handy for unexpected real-time traffic spikes. If you know what your system can do, you also know how to manage it in real-time.


6. Analyze the Results


Identify bottlenecks and errors and determine which solutions are needed to fix them, and fix them. Set aside dedicated technical resources for this. Look at KPIs like response time, throughput,  latency and connect time; and also at the correlations between them.


7. Run Your Tests Again


After committing changes, fixing bugs, servers are ready, etc., calibrate your tests and run them again to see if the changes improved your system’s abilities.


8. Plan and Implement Continuous Delivery (CD), Continuous Testing and Continuous Integration (CI) Methodologies


Load testing doesn’t start and end before special events. Implement Continuous Testing into your development strategy. Ensure any changes in your code don’t affect other parts of your product, and make sure you are always prepared. Jenkins is an open source tool for automating tests and Continuous Integration, which enables load testing as part of its process. 


Black Friday is a great opportunity for many businesses. With proper preparation, you can ensure you will be prepared.


Interested in learning more about how to best prepare for a high-scale load test on your website or app for Black Friday and Cyber Monday (or really any big event with expected traffic spikes)? View our on-demand webcast Running a Large Scale Load Test Ahead of Black Friday & Cyber Monday.


To try out BlazeMeter, put your URL in the box below and your test will start in minutes.


arrow Please enter a URL with http(s)

Interested in writing for our Blog?Send us a pitch!