Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

JMeter Cookbook

By : Erinle

3.6 (8)

JMeter Cookbook

3.6 (8)

By: Erinle

Overview of this book

This book is great for you if you are a developer, quality assurance engineer, tester, or test manager who is looking to get a firmer grasp of elementary, deep, and advanced testing concepts using Apache JMeter. It’s assumed you have access to a computer and an Internet connection. No prior testing or programming experience is required, but would be helpful.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. JMeter Fundamentals

1. JMeter Fundamentals

Introduction

Executing a test script

Recording a script via HTTP(S) Test Script Recorder

Recording scripts via the Chrome browser extension

Converting HTTP web archives (HAR) to JMeter test plans

Viewing and analyzing test results

Feeding data into a script

Using timers

Managing HTTP user sessions

Testing Single Page Applications (SPAs)

Testing AJAX-centric applications

2. Handling Responses

2. Handling Responses

Introduction

Using Regular Expression Extractor

Using Regular Expression Tester

Using CSS/jQuery Extractor

Using XPath Extractor

Dealing with file downloads

Handling XML responses

Handling JSON responses

Handling HTML responses

Using Response Assertion

Using Duration Assertion

Uploading files with your scripts

3. Building Robust Test Plans with Controllers

3. Building Robust Test Plans with Controllers

Introduction

Using Transaction Controller in test plans

Using Loop Controller in test plans

Leveraging ForEach Controller in test plans

Using Interleave and Random Controller in test plans

Using Runtime Controller in test plans

4. Testing Services

4. Testing Services

Introduction

Testing REST web services

Testing SOAP web services

Testing FTP services

Testing relational databases

Testing NoSQL databases

Testing JMS services

5. Diving into Distributed Testing

5. Diving into Distributed Testing

Introduction

Testing applications with JMeter's master-slave setup

Testing internal applications using JMeter and Vagrant

Testing external facing applications using JMeter, Vagrant, and AWS

Testing external facing applications using Flood.IO

Testing external facing applications using BlazeMeter

6. Extending JMeter

6. Extending JMeter

Introduction

Using REST Sampler

Using Ultimate Thread Group

Using Throughput Shaping Timer

Using Console Status Logger

Using Dummy Sampler

Developing custom JMeter plugins

Testing WebSocket-enabled applications

7. Building, Debugging, and Analyzing the Results of Test Plans

7. Building, Debugging, and Analyzing the Results of Test Plans

Introduction

Using the View Results Tree listener

Using the Aggregate Report listener

Debugging with Debug Sampler

Using Constant Throughput Timer

Using the JSR223 postprocessor

Analyzing Response Times Over Time

Analyzing transactions per second

Using User Defined Variables (UDV)

8. Beyond the Basics

8. Beyond the Basics

Introduction

Continuous Integration with JMeter

Testing with different bandwidths

Using the HTTP Cache Manager component

Using script languages within test plans

Writing Test scripts through Ruby DSL

Understanding JMeter properties

Monitoring servers while executing tests (using VisualVM)

Monitoring servers while executing tests (using YourKit Profiler)

Monitoring servers while executing tests (using New Relic)

Performance tips to scale JMeter

A. Installing the Supporting Software Needed for this Book

A. Installing the Supporting Software Needed for this Book

Introduction

Installing JMeter

Installing Java Development Kit (JDK)

Installing JMeter plugins

Installing Vagrant

Installing VirtualBox

Installing Maven

Installing Git

Obtaining AWS keys for EC2

Index

Index

Customer Reviews

3.6 (8)

5 star

25%

4 star

50%

3 star

0

2 star

12.5%

1 star

12.5%

Testing AJAX-centric applications

In today's stack of web applications, it is almost unthinkable to build an application without some dynamic content being retrieved from a backend service. Most of the time, these applications tend to lean towards partial page fresh. That is, only the needed sections of a rendered page are refreshed as opposed to the whole page loading its entire content again. This leads to more responsive pages, which improves the overall experience of the user.

How to do it…

In this recipe, we will walk through how you can test such applications using JMeter. Perform the following steps:

Launch JMeter.
Add HTTP(S) Test Script Recorder and set it up for recording (see the Recording a script via JMeter HTTP proxy recipe).
Click the Add suggested Excludes button.
Start the HTTP(S) Test Script Recorder.
Point your browser to https://maps.google.com.
Perform a couple of searches in the provided search box (for example, pizza, restaurants, hotels, and so on).
Click on a few of the returned results.
Repeat steps 6 and 7 two more times.
Stop the HTTP(S) Test Script Recorder.
Add a listener to your test plan.
Save and run the test plan.

How it works…

The actions of the user are tracked and recorded via the script recorder we set up in step 2. Like traditional web applications, we record all actions and exclude irrelevant static resources, such as images, JavaScript, and style sheets. Calls that trigger backend server calls are trapped and are available for replay later. At the end, we have a script that is almost identical to what we would get when recording a traditional web application.

There's more...

AJAX-centric applications tend to involve a lot of asynchronous server requests made from within the client (frontend). These calls are normally made from embedded script tags within a view technology, for example, HTML, Java Server Pages (JSP), Groovy Server Pages (GSP), or from an included JavaScript file in the page. As such, JMeter records all such server requests and they can be played back at the time of running our test plans. This allows us to simulate the intended load on our servers, as though the application was the one making the AJAX calls.

Search

Your notes and bookmarks