Home Home Archive Archive



JAN 4TH, 2011
Making your JMeter Test modular

(This article is part of the JMeter Series) As tests get larger, or as steps need to be repeated you’ll want to structure your tests into distinct entities - these seem to be called “Modules” in JMeter. However, there is no “Module” element JMeter. As a “Module” you can however use the “Simple Controller”. It allows you to drop other elements into it and to name them as a whole. I don’t know whether it has additional features such as providing scoping of any kind. Read on


JAN 4TH, 2011
Some words on overall usefulnes of JMeter

(This article is part of the JMeter Series) Purpose of JMeter JMeter is a testing tool. It comes accross as a graphical tool, where you can half visually half through text define your test. Its roots seem to lie in web testing - that means testing a website on how long it takes to return pages, how well it does under stress, how well it scales with increasing numbers of parallel requests etc. Read on


JAN 4TH, 2011
The JMeter "Workbench", a trapdoor for the newbie

(This article is part of the JMeter Series) Upon starting JMeter you’ll see two branches: “Test Plan” and “WorkBench”. “Test Plan” is the place where your tests will live. What the purpose of “WorkBench” is, is not really clear. It seems to be meant to be a place to do your throw-away experimentation. The really crucial “trap” of the “WorkBench” is however, that JMeter will throw away whatever you put into the “WorkBench” upon exit. Read on


JAN 4TH, 2011
Waiting for a page change in JMeter

(This article is part of the JMeter Series) While testing a Rails application there was a situation where a background worker (DJB or background task) would get an order to execute and eventually the completed order would appear on a page. Thus we needed to wait for the page to be updated and continue the test after. User Defined Variables I’m predefining used variables here - see “We set up our variables” in the Extracting text from a page and using it somewhere else in JMeter article for an exaplanation why. Read on


JAN 4TH, 2011
Working with big files/calling external scripts in JMeter

(This article is part of the JMeter Series) JMeter’s “HTTP Request Sampler” will read the whole input (the downloaded page, pdf, movie etc.) into its main memory. That means that working with larger (f.ex. movies) files will bring JMeter, the JVM and/or many machines to their memory limits. If you do not not need to do more than making sure that something gets downloaded, then you can “offload” the download work to an outside process, f. Read on
← Older Blog Archives Newer →

    Recent Posts

  • The map after the course: why QGIS training is adding web publishing
  • FOSS4G 2026 Hiroshima
  • FOSS4G Europe 2026 in Timișoara
  • Multi-User Editing in QGIS Cloud

    Archive

  • 2026 5
  • 2025 8
  • 2024 5
  • 2023 7
  • 2022 6
  • 2021 8
  • 2020 6
  • 2019 10
  • 2018 3
  • 2017 3
  • 2016 4
  • 2015 7
  • 2014 9
  • 2013 17
  • 2012 13
  • 2011 29
  • 2010 26
  • 2009 17
  • 2008 9
  • 2007 4
  • 2006 18
  • 2005 2
  • 2004 8
  • 2003 22
  • 2002 5
  • 2001 6

    Categories

  • geo 113
  • linux 74
  • programming 36
  • qgis 71
  • qgiscloud 17

Copyright © 2001-2026 Sourcepole AG