Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
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

Integration of JMeter in the DevOps Tool Chain

Introduction

Nowadays, time to market is critical, and we have several solutions to reduce it:

  • Agile methods
  • Minimum Viable Product (MVP)
  • DevOps, etc

Load testing must support these changes. As a consequence, we need to test earlier and often.

The first point to consider is that the earlier the tests are performed, the better it is.

Indeed, a bug discovered early in a project life cycle:

  • Is easier to fix since it is ideally fixed within the development phase. Fixing a bug during the integration phase means digging into more layers to find the root cause, which leads to higher costs.
  • Costs less than a production bug, as it does not impact customers. Think of a bug on pricing as an illustration.

The second point to consider is that tests must be performed at all stages of the application's life cycle: from development to integration, to production.

This approach of testing earlier...

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 R$50/month. Cancel anytime