Michael Sage is Chief Evangelist for BlazeMeter. He has over 15 years experience as a solutions architect and consultant helping teams of all sizes with software delivery and performance management. Prior to joining BlazeMeter, Michael worked with industry-leading companies like Mercury Interactive, Hewlett-Packard, and New Relic. A native of Philadelphia, he’s made San Francisco his home for over 10 years.

Become a JMeter and Continuous Testing Pro

Start Learning

Test Your Website Performance NOW!

arrow Please enter a URL with http(s)

Continuous Performance Testing at Every Stage - Watch the Video from the AWS Loft

According to a huge amount of data, user expectations for website speed and performance are growing. According to a report by Akamai, 49% of respondents expected web pages to load in under 2 seconds, while 30% expect a 1-second response and 18% expected a site to load immediately. 50% of frustrated users will visit another website to accomplish their activity, while finally, 22% will leave and won't return to a website where problems have occurred.


As software teams have gotten faster with iterative development and continuous integration (CI), load testing has gotten harder to do, largely because the tools available for load testing were created for a different time, the old “Waterfall” days. Back then, specialists would run big, complex tests toward the very end of the release cycle, find the performance bottlenecks, fix the problems and do it again. Many people still think this is the only way to do load testing, and it's often seen as a big headache. Needless to say, this process is completely inefficient in the new development cycle. 


In the era of DevOps and continuous delivery, we need new tools to help us make performance testing - more critical then ever - work better and easier. And these tools need to:


- incrementally build tests from commit to commit

- build tests in code, keep them in the repository and run them in parallel

- work with the existing tools we are using


I recently gave a presentation at the AWS Loft in San Francisco, where we looked at some of the available open source load testing tools, including Apache JMeter, Locust, Gatling and more. Mostly though, I presented on Taurus, an open source test automation platform, where in everything is in YAML or JSON formats, that works perfectly in modern DevOps practices.


I looked at how to create a Taurus test, defining the execution conditions including concurrency and ramp time, defining the scenarios that run the test logic, setting pass/fail criteria for the test, and more. I also went into where Taurus can fit into the continuous delivery (CD) workflow. 


You can view the full recording of the presentation below (about 15 minutes total). 



If you are looking to learn more about Taurus, I encourage you to read:



Feel free to leave a comment or question below. 


arrow Please enter a URL with http(s)

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