Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Master Apache JMeter - From Load Testing to DevOps

You're reading from   Master Apache JMeter - From Load Testing to DevOps Master performance testing with JMeter

Arrow left icon
Product type Paperback
Published in Aug 2019
Publisher
ISBN-13 9781839217647
Length 468 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (3):
Arrow left icon
Bruno Demion (Milamber) Bruno Demion (Milamber)
Author Profile Icon Bruno Demion (Milamber)
Bruno Demion (Milamber)
Antonio Gomes Rodrigues Antonio Gomes Rodrigues
Author Profile Icon Antonio Gomes Rodrigues
Antonio Gomes Rodrigues
Philippe Mouawad Philippe Mouawad
Author Profile Icon Philippe Mouawad
Philippe Mouawad
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

About the Book 1. Quick Start with JMeter FREE CHAPTER 2. JMeter Overview 3. Designing a Test Case 4. Important Concepts in JMeter 5. Preparing the Test Environment (Injectors and Tested Systems) 6. Being Productive with JMeter 7. Load Testing a Website 8. Load Testing Web Services 9. Load Testing a Database Server 10. Load Testing Message-Oriented Middleware (MOM) via JMS 11. Performing a Load Test 12. Visualizing and Analyzing the Load Testing Results 13. Integration of JMeter in the DevOps Tool Chain

Setting Up Shift-Left Strategy

In load testing, Shift-Left would result in:

  • Early load tests across project phases, particularly in the development and testing phases
  • The automation of load tests and integration in the build pipeline

Still, Shift-Left is not that easy for many reasons:

  • The ability to load test depends, at minimum, on the environment and the availability of test data. As we have seen in previous chapters, data has a huge impact on load test quality.
  • The ability to automate load tests depends, at minimum, on the availability of environments, the automation cost (which depends on the application architecture), and the ability to mock third parties.
  • Return of investment (ROI) of tested features. You may hold that 100 percent of the application should be tested, but that's probably impossible for the majority of applications.

Here are a few examples of how much testing technologies can cost a company (the more "'+"' signs there...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image