Reuse Extractors? - jmeter

I've used a Module Controller to invoke a Test Fragment. This is a great way to reuse Controllers and Samplers across multiple Thread Groups.
I have a set of about a dozen Extractors (CSS and RegEx) that I'd like to reuse for different HTTP Samplers. (The Samplers would be different, but the Extractors I'd run against each would be the same.)
Is there a way I can accomplish this?

You have 2 options:
You can use scopes if it applies , see http://jmeter.apache.org/usermanual/test_plan.html#scoping_rules
Otherwise put you CSS expressions in Variables and use them in extractor

Related

JMeter : Define Test Fragment Inputs

I'm trying to define fragment inputs, which are variables that should be defined to have the fragment execute successfully (I'm trying to achieve something similar to method arguments in programming languages)
I have tried to use test plan variables in the fragment like so :
But when the fragment is included in another test plan and with looking to the Debug PostProcessor output, those variables are completely ignored.
Please is there official JMeter documentation that mention test plan variables are ignored in this case ?
What is the cleanest way to define variables for a fragment with a scope local to the fragment or at least local to current thread ? My purpose to make a fragment clearly defined what are the variable it uses, so it can be easily reused by other developers
Thank you
If you need to declare the variables to be used in the test fragment - go for User Defined Variables configuration element like:
When you call a Test Fragment from a separate Test Plan the variables defined in that Test Plan will be available for usage.
Alternative option is using JMeter Properties which are global for the whole JVM

Use Beanshell Assertion inside a Critical Section Controller

I'm trying to use Beanshell Assertion inside a Critical Section Controller, but it seems to be ignored. Does someone know why is this behaviour? have I missed something?
JMeter Assertions are executed only in context of the Sampler, if there is no sampler which generates a SampleResult in the Assertion's scope - it will not be executed.
Also be aware that since JMeter 3.1 you should be using JSR223 Test Elements and Groovy language for scripting so consider migrating to JSR223 Assertion on next available opportunity
assertions apply to all samplers which are in their scope
Assertion, for instance, is hierarchical in the test tree. If its parent is a request, then it is applied to that request. If its parent is a Controller, then it affects all requests that are descendants of that Controller.

difference between simple controller and module controller in jmeter

I am using Jmeter and I saw simple controller and module controller and I could not understand the difference between them.
I tried adding them both but I don't know how to use them more efficiently.
Can anyone please help me?
Module Controller can be used to run other Logic Controllers, for example if you have a Transaction Controller which implements Login and you are creating a test assuming different groups of users which need to be logged in - you can call the aforementioned "Transaction Controller" using the Module Controller in 2 different Thread Groups instead of copying and pasting it.
See Using JMeter Module Controller article for more information.
Simple Controller actually does nothing apart from grouping Samplers. You might use Simple Controller in the Module Controller or apply a single Post-Processor, Assertion, Pre-Processor, etc. to all Simple Controller's children. Apart from these two use cases it doesn't add any value.
Simple Controller is just a container to group samplers in it and apply some scoping rules for example:
http://jmeter.apache.org/usermanual/component_reference.html#Simple_Controller
Module Controller is a way to reuse code accross your test:
http://jmeter.apache.org/usermanual/component_reference.html#Module_Controller
Module controller can be used to choose between Simple Controllers see example
Module controller will allow me to run only selected simple controller's requests.

JMeter assertion modularity (can I re-use assertions?)

I am working on a test plan for our REST web application and we have several common test types which have common criteria we want to test for. For example, when creating entities through the API we have a common set of expectations for the JSON response; id should be set, created date should be set, etc.
Now, I would like to model my plans like this:
Thread Group
Users (Simple Controller)
User Create Tests (Simple Controller)
Create Test 1 (Sampler)
Create Test 2 (Sampler)
Create Test 3 (Sampler)
Common Creation Asserts (Module Controller)
User Delete Tests (Simple Controller)
Samplers...
Common Delete Asserts (Module Controller)
Events (Simple Controller)
Event Create Tests (Simple Controller)
Samplers...
Common Creation Asserts (Module Controller)
Event Delete Tests (Simple Controller)
Samplers...
Common Delete Asserts (Module Controller)
Thread Group for common assertions (disabled)
Common Creation Assertions (Simple Controller)
BSF Assertion 1
BSF Assertion 2
BSF Assertion 3
Common Delete Assertions (Simple Controller)
Asserts...
Now, I understand how the scoping works and that if I placed assertions where the BOLDed module controllers are they would be invoked for each sampler. However, I'd rather not have to copy-paste-maintain numerous copies of the same assertions in each of these locations. Hence, why I want a way to define assertions once, and invoke where appropriate.
However, with this approach, the ACCENTed assertions placed in the common simple controllers are never invoked (confirmed by using a BSF assertion with logging messages). If I place an additional sampler in the common assertions simple controller it is invoked. But only a single time.
I'm using JMeter 2.12 but have confirmed that JMeter 2.8 behaves the same way.
So, how can I use JMeter to define assertions once, and re-use them anywhere?
Thanks!
There is no way to do this.
You can try factoring by using Variables within Assertions, thus if it's a Response Assertion you will factor out this.
I ended up getting creative.
Using JSR223 assertions in Javascript I've accomplished what I wanted. This is a natural fit because all the response data I want to test is in JSON, YMMV.
In User Defined Variables I define the tests I want to perform using Javascript.
Tests like:
TEST_JSON:
try
{
eval('var obj = ' + prev.getResponseDataAsString());
} catch(e)
{
setFailed();
}
TEST_RESULT_SUCCESS
if(obj.status != "success")
{
setFailed();
}`
Then in the assertion(s) I can do something like:
eval(vars.get("TEST_JSON"));
eval(vars.get("TEST_RESULT_SUCCESS"));
And I don't have to re-write tests over and over and over.
I even have some a some utility functions that I can add to my assertion by doing
eval(vars.get("TEST_UTIL"));
which allows me to print additional logging from my assertions if I desire.

Defining scope based user defined variables under different thread group

I have multiple thread group for a test plan in jmeter. I want to define user defined value's to a particular thread group, the variable name can be repeated in another thread group for its user defined values.
When I tried doing the above it was picking up the last value of the same variable name across thread groups and not using it scope wise.
Using for jdbc requests with queries
I answere this "old" question for everyone who has the same Problem and is looking for a working solution. At least in JMeter 5.11 the answer of Dmitri T is not always true.
From the JMeter Documentation:
Note that the values defined by the Test Plan and the User Defined
Variables configuration element are made available to the whole test
plan at startup. If the same variable is defined by multiple UDV
elements, then the last one takes effect. Once a thread has started,
the initial set of variables is copied to each thread. Other elements
such as the User Parameters Pre-Processor or Regular Expression
Extractor Post-Processor may be used to redefine the same variables
(or create new ones). These redefinitions only apply to the current
thread.
A good and working solution for using local variables, that are only visible in the actual Thread Group, is to use the User Parameters Pre-Processor instead of the User Defined Variables configuration element.
Happy load testing ...
JMeter Variables have scope limited to current Thread Group only. To make JMeter variables visible for all Thread Groups you need to convert them to JMeter Properties. See How to Use Variables in Different Thread Groups guide for details on how to do it.
I got the solution. Example: If you have some test cases under a random order controller and like that you have multiple random controllers. The test case's contain a variable name for a jdbc request connection then you can add user defined variable inside the random order controller which will be used by only those test case's under it.
Like this you can scope the variable name to a particular random order controller

Resources