Re: xPath assertion: No nodes matched but did not error out

Dmitri T <[email protected]> Tue, 12 Nov 2024 15:48:27 +0000
Newsgroups gmane.comp.jakarta.jmeter.user
Message-ID <[email protected]>
I cannot reproduce your issue using latest JMeter 5.6.3, see the 
attached image.



In order to get more comprehensive help you should either provide a test 
plan which reproduces the issue or jmeter.log file 
<https://jmeter.apache.org/usermanual/get-started.html#logging> with 
JMeter logging level set to DEBUG 
<https://www.blazemeter.com/blog/jmeter-logging> so we could see what 
prevents the sampler from being marked as failed.

Do you have by any chance a Response Assertion 
<https://jmeter.apache.org/usermanual/component_reference.html#Response_Assertion> 
which is set to "Ignore Status" somewhere

Jun Zhuang wrote:
> When I test my xpath against the response there was no problem. But 
> the failureMessage column of the view results tree log shows "No Nodes 
> matched for .... but that did not fail the request. With Report errors 
> and Show warnings checked, they don't seem to make any difference.
>
>
> Inline image
>
>
> Can someone explain the behavior?
>
> thanks,
> Jun
> On Friday, February 23, 2024 at 03:17:55 AM EST, Dmitri T 
> <[email protected]> wrote:
>
>
> Jun Zhuang wrote:
> > Hi,
> >
> > I am trying to create variable throughput using throughput controller
> > with a variable like this
> >
> > Inline image
> >
> > but it keeps throwing the following exception, just wonder if it's not
> > designed to be used like that? But using variable with a loop
> > controller works without any problem.
> >
> > Inline image
> >
> > *
> > *
> > *Following is how I set the variable:*
> > importjava.util.Random
> >
> > intiRand=newRandom().nextInt(3);
> > vars.putObject('sRandomThroughput',(float)iRand);
> >
> >
> >
> > Thanks,
> > Jun
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:[email protected]
> > For additional commands, e-mail:[email protected]
> It should be "designed to be used like that", according to JMeter Test
> Elements Execution Order
> <https://jmeter.apache.org/usermanual/test_plan.html#executionorder>:
>
> Logic Controllers and Samplers are processed in the order in which they
> appear in the tree.
>
> So despite the warning in the log it will apply the throughput you
> calculate beforehand
>
> If you want to get rid of the warning you can decrease logging verbosity
> for the Throughput Controller, it can be done by adding the next line to
> log4j2.xml file:
>
> <Logger name="org.apache.jmeter.control.ThroughputController"
> level="info" additivity="false"/>
>
> You might also want to raise an improv
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] 
> <mailto:[email protected]>
> For additional commands, e-mail: [email protected] 
> <mailto:[email protected]>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Untitled.jpg (image/jpeg, 302.2 KB) - not displayed