Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Book Review: Apache JMeter 53

MassDosage writes "Apache JMeter written by Emily H. Halili is very much an introductory guide to using Apache's open source JMeter testing tool. Unfortunately a book that should have been good fodder to whet the appetites of testers is spoiled by shoddy editing, poor writing and very little content that isn't already included in JMeter's own user manual." Read below for the rest of MassDosage's review.
Apache JMeter
author Emily H.Halili
pages 129
publisher Packt Publishing
rating 3/10
reviewer Mass Dosage
ISBN 978-1-847192-95-0
summary A practical beginner's guide to automated testing and performance measurement for your websites.
I am one of those (fairly) rare software developers with a genuine interest in testing and first tried using JMeter many years ago after its initial release as a tool primarily focused on testing the Apache Tomcat web/application server. It was a bit rough around the edges and poorly documented in those days so I was looking forward to a book that would re-familiarize me with JMeter in its current form. This book clearly targets itself at the testing community and doesn't require any programming (or even much testing) knowledge.

Apache JMeter starts off with a not particularly convincing overview of why one would want to automate testing and goes off on a tangent trying to prove the monetary savings this leads too. Any testing will depend very much on the type of software being tested, the skills of the tester, technology stack in use etc. so trying to come up with a general formula proving that testing will save money is probably impossible and pointless. It would have been far more useful to include some practical examples where testing saved time, effort, caught bugs early etc. A very brief history of JMeter is provided as well as an overview of its GUI and the the various elements available. For those who haven't used it before — JMeter acts as a client which sends requests to the application being tested and can then act on the responses returned. Overall this isn't the smoothest of introductions with lots of grammatical errors, fragmented text and repeated concepts, which doesn't bode well for the rest of the book.

Installing and setting up JMeter is covered next and this is straightforward and simple. A good overview of what a JMeter test plan consists of is provided and this covers controlling how many simultaneous users a test will use, what logic and timing will be used to issue requests, the type of requests (e.g. HTTP for web sites, FTP for file retrieval etc.), various configuration options, how to assert the contents of responses and so on. The book is a bit dated and the version of JMeter I was using didn't always match up with the text and diagrams but most of the differences were self explanatory so this wasn't really an issue.

The chapter on load and performance testing is the best on offer and provides sensible guidelines on this type of testing. These include tips such as ensuring network bandwidth between the machines under test, running the tests on physically separate machines from the software being tested, running tests for long periods of time and what to monitor. This is mainly common sense but it's good to see them summarized and the book would have benefited from more sections that appear to be informed by the author's practical experiences as a tester. The example given in the book is the load testing of a web site over HTTP and it's left up to the reader to translate the various types of request being made to an example website of their own. The screen shots of setting the various GUI values are clear and useful. Remote testing (i.e. not using a single JMeter GUI but multiple command-line instances of JMeter) is mentioned but sadly not covered which is a shame as any serious load or stress testing usually requires this. Using JMeter as a proxy to quickly generate a test plan by recording HTTP requests from a browser is both neat and useful and explained well.

JMeter is not just limited to load testing but can also be used to do simple functional tests as it can inspect the values returned by requests and perform assertions on these responses (e.g. checking that the returned HTML contains some text). Unfortunately functional testing is covered very poorly with far too little detail and no explanation of how to run the examples yourself. The author should have stuck to one simple use case (ideally that the reader could follow along with) which would show how to add one's own custom values to requests and to assert the results returned. In the end I could figure it out for myself, but I'd expect a book to guide me through this.

Advanced features are up next and the reader is pointed towards the sample code included with the book (a .rar file inside a .zip file, why?) but absolutely no explanation is given as to what one should actually do with the bunch of PHP and SQL files included in it. Using regular expressions and configuring JMeter to run tests using loops is covered but this doesn't make much sense as there is no context for the example used in setting this all up. Fortunately the sections on using JMeter to test a database and an FTP server are introduced with clear setup steps that are easy to follow. I wouldn't classify most of this material as advanced, it just gives the reader the knowledge that JMeter can be used to test more than just HTTP sites and provides a few very simple examples which they can build on.

Finally the book wraps up by stressing once again that it's just an introduction to JMeter and a concluding table clearly showing that more is not covered than actually covered. The appendices consist of definitions of nearly every JMeter element that can be accessed in the GUI (a good quick reference), some pointers to material for readers interested in learning more, and a glossary of testing terms, the vast majority of which are never used in the book itself. Unfortunately the latter is yet more evidence of the biggest weakness of this book — the appalling editing that doesn't even remove sentences which are completely incorrect. 'You can too contribute.' (the closing sentence of Chapter 1) is just one of many examples of poor writing that somehow survived into print.

On the whole the book does give one an overview of how to get started with JMeter and the section on load testing a website is a useful introduction to various JMeter concepts. This is the only printed book on the topic out there so if you learn best reading from print then you don't have many options. This is a shame as a niche topic like this could do with an interesting, well-informed and authoritative guide. For everyone else I would suggest reading the User Manual on the JMeter website as it covers all the material here (and much more) and is far more readable.

You can purchase Apache JMeter from Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.


This discussion has been archived. No new comments can be posted.

Book Review: Apache JMeter

Comments Filter:
  • The problem is Packt (Score:5, Informative)

    by stonecypher ( 118140 ) <stonecypher@gmai ... m minus language> on Wednesday May 04, 2011 @02:18PM (#36027604) Homepage Journal

    I bought a Spring book from Packt which was full of wrong information, code examples that were garbage, et cetera. Packt is still selling the book, errors in place, and attempted to bribe me to remove my public requests to them to fix the book, instead of just fixing the book.

    It's a shovel-ware scum publisher from India. They don't edit. Many of their books are essentially whole-sale theft of manuals.

    Never buy Packt.

    • Are you sure they are from India? Looking at their careers page, they seem to be based in Birmingham. []
      • by Anonymous Coward on Wednesday May 04, 2011 @02:53PM (#36028024)

        All of the contacts I've ever had with them (as a technical editor and a prospective author) were people with Indian names. After they failed to come up with a contract for several weeks, while nagging me about sending in chapters according to the schedule we'd agreed on, I gave up on writing a useful book on the application of my choice. I have too many things to do to want to work with such a disorganized, unprofessional organization. The book I edited was written by an Indian developer who clearly has no real experience with the application, and his second edition which had Indian technical editors who also obviously knew nothing about the application is full of mistakes and just plain wrong information. They want me to post a review on my website which is dedicated to articles and demos of the application, but about all I could say would be "don't bother", so I won't.

        • by xaxa ( 988988 )

          All of the contacts I've ever had with them (as a technical editor and a prospective author) were people with Indian names


          Birmingham is the most populous British city outside London, with 1,028,700 inhabitants ... The ONS estimates that, in 2007, 62.1% of the population was White British, 2.4% White Irish, 2.2% Other White, 21% Asian, 6.7% Black, 1.2% Chinese, 3.2% of mixed race and 1.2% of other ethnic heritage.

          So it's entirely possible those people were in Birmingham, although hidden on the website is a tiny mention of their second office in Mumbai. I suspect the real work is done in India, and the marketing/accounting in England.

          • So it's entirely possible those people were in Birmingham, although hidden on the website is a tiny mention of their second office in Mumbai. I suspect the real work is done in India, and the marketing/accounting in England.

            It's called global capitalism, all the gung ho free market cheerleaders can't really complain when this happens. Contrary to popular belief, it's not quality that always wins out in the end.

          • although hidden on the website is a tiny mention of their second office in Mumbai

            That's actually their main office, where almost all of their staff are. Their Birmingham office has two people.

            Please stop injecting guesses as data.

            and the marketing/accounting in England.

            The England address is just a secretary, there to fool people like you into thinking anything happens in England other than mail forwarding.

            • by xaxa ( 988988 )

              Please stop injecting guesses as data.

              Please take the time to read the comment you reply to, like this bit I suspect the real work is done in India. That's a guess, but with the word "suspect" I'm not presenting it as data.

              The England address is just a secretary, there to fool people like you into thinking anything happens in England other than mail forwarding.

              People like me? I'm the one who isn't convinced they do any writing in England ;-)

      • They acquired that "office" once I started telling people where they were. It's what an American would think of as a tax drop-box (some people might call it a safety deposit address).

        Their real address is

        Sagbag Lane, Off.Andheri Kurla Road, Saki Naka,
        Andheri East
        MUMBAI, Maharashtra, India 400001

        Their phone number is


        On their various job postings for English technical editors, they mention that they will teach you English as part of your job ... verifying ... the quality of English technical writing.

        Generally, their code samples don't even compile.

        Don't buy Packt. They're just scammers.

        • by cultiv8 ( 1660093 ) on Wednesday May 04, 2011 @03:42PM (#36028534) Homepage
          The only good thing I can say about Packt is that they pay book royalties to open source projects []. Other than that, yeah, don't buy from them.
    • by Lunix Nutcase ( 1092239 ) on Wednesday May 04, 2011 @03:00PM (#36028102)

      What's funny is if you follow the Amazon link you find a guy named Vamseedhar R. Sane who is the only one to give this book a 5 star review and he apparently gives every Packt book 5 star reviews []. And people still think Packt doesn't clearly pay shills to advertise their books around?

    • by Dynedain ( 141758 ) <.moc.nilcmynohtna. .ta. .2todhsals.> on Wednesday May 04, 2011 @03:07PM (#36028160) Homepage

      Some of their authors also like to copy/paste online tutorials (which I've seen done from my own website). Basically they're a cheap clearing house and don't do any real editing or verification of their publishing. Stick with O'Reily.

    • I bought a YUI book from Packt and it wasn't very good either. Never bought another book from them.
  • by prgrmr ( 568806 ) on Wednesday May 04, 2011 @03:25PM (#36028356) Journal
    Looking at the author's bio on Pact's web site: [] it would appear that English may not be her first language, and given that she's worn 6 different IT hats in 12 years, she's obviously not spent enough time doing any one thing to become an expert at anything. And now she's a consultant, which affirms the old saying "those who cannot do, teach".
    • by Anonymous Coward

      You do realise English is a common language in Malaysia right? And they speak it a fair bit at California State too (more or less).

      • by prgrmr ( 568806 )
        Yes, hence the "may not". The reviewer mentioned poor writing and grammar, and I would hope that English as a second language would be a much more forgivable excuse for that than simply being under-educated and/or sloppy.
    • given that she's worn 6 different IT hats in 12 years, she's obviously not spent enough time doing any one thing to become an expert at anything.

      Isn't Malcom Gladwell's notion that you need 10,000 hours doing something to become an expert in it? If she worked ten hours a day fifty weeks a year at each of those jobs, that's 10*5*50*2=5,000 hours so she's half-expert in 6 different things, which isn't bad.

  • It's been a while since I used JMeter, but I had good luck using a web capture/replay tool called Badboy as a functional input to JMeter.

    I created the functional tests with Badboy, then export/imported them into JMeter. JMeter ran the Badboy functional tests with my desired testing characteristics. I got a pretty good overview of the performance of the application under test (an XML service that front-ended a database).

    The problem with using load testing tools like JMeter for finding web site performance

  • one of their recruiters approached me last year to write a book on numpy. which was curious to me since while i've used it (and posted some very minor public code using it), i'm not a contributor, nor involved in the community in any way.

    some googling led to some fairly consistent stories:
    very little editing work
    very low sales (rep told me 1000 copies would be considered successful for a sequel)
    don't expect more than your initial front (~$3500, which isn't even a front; they pay it out over the different c

    • I don't think you know what the term "vanity press" means.
      Clue: they don't pay you anything, you pay them for the privilege of seeing your name in print.
      • by deander2 ( 26173 ) *

        i don't think you know what "isn't much more than" means.
        clue: it includes "a little more", as in "packt is a little more than a vanity press (but not much)".


  • Stop it with the Packit book reviews. These books are uniformly bad and overpriced. I made the mistake of buying the one on Tapestry and it was full of incorrect information and didn't address any topics beyond the Hello World level.

    The book actually hindered my efforts to get up to speed on this framework.

    -1 Overrated on this book, review, the editor who posted it and the shill who reviewed it.

    • > the shill who reviewed it.

      Is this really a shill review? I mean, I wouldn't expect to see the words "shoddy editing, poor writing and very little content" in a shill review, nor would I expect to see this in the conclusion: "For everyone else I would suggest reading the User Manual on the JMeter website as it covers all the material here (and much more) and is far more readable."

      I mean, I'd be pretty disappointed with that shill review if I were packt.

      There's another packt book that was reviewed here a

      • Thanks @ajo_arctus. I don't consider myself a "shill" as my reviews are my own honest opinion and Packt have no influence on what I say about their books. This is only the second Packt book I've read, the other one (Solr 1.4 Enterprise Server) was actually pretty good so I'm not sure I'd write off *all* their other books. I haven't read the Postgres book you mention, the title sounds interesting though and I'd be curious to know opinions of anyone else has read it.
  • I use jmeter at work and it took all of about a couple of days to come up to speed on it. I've written some plugins for it now. Everything I learned was from their user manual and the source code. I'm not sure you need a book for it, but it kind of sounds like I could do a better job of writing one in any event. Hmm...

A triangle which has an angle of 135 degrees is called an obscene triangle.