Home Home Archive Archive



JAN 4TH, 2011
Extracting text from a page and using it somewhere else in JMeter

(This article is part of the JMeter Series) In the following we’ll do these things: we go to a form submit page we order something we get that something we ordered In more detail: We use a “Cookie Manager” to carry forward cookies between calls We set up our variables The idea here being that we predefine the variables, so they would show up in the “Debug Sampler” which makes debugging easier, because you see at each step, whether the variable has the correct value or not. Read on


JAN 4TH, 2011
JMeter Series

This is a short series of howtos for and a critique of JMeter v2.4. The following articles have been done: Some words on overall usefulnes of JMeter The JMeter “Workbench”, a trapdoor for the newbie Debugging JMeter Tests Making your JMeter Test modular Working with big files/calling external scripts in JMeter Extracting text from a page and using it somewhere else in JMeter Waiting for a page change in JMeter Tomáš Pospíšek, 4. Read on


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
← Older Blog Archives Newer →

    Recent Posts

  • Qgiscloud Db Connection Error
  • How to configure unattended-upgrades of packages from third party deb package repos
  • Updating company-wide and your own hosts with apt-dater
  • Executing Tasks in docker-compose Containers From ansible

    Archive

  • 2025 5
  • 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 105
  • linux 74
  • postgis 2
  • programming 36
  • qgis 69
  • qgiscloud 15

Copyright © 2001-2025 Sourcepole AG