jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 56816] Assigning null to a BeanShell variable in a JSR223 sampler does not work as expected
Date Fri, 27 Jan 2017 09:42:22 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=56816

--- Comment #4 from Graham Russell <jmeter@ham1.co.uk> ---
In the latest trunk 3.2-SNAPSHOT all of the following match x == void but do
NOT match x == null in the JSR223 sampler:

var x;
var x = null;
Object x = null;
String x = null;

Not sure if it's a bug, but it looks like expected BeanShell behaviour looking
at the BeanShell docs (http://www.beanshell.org/manual/bshmanual.html):


unset
void unset ( String name ) 
"Undefine" the variable specifed by 'name' (So that it tests == void).
Note: there will be a better way to do this in the future. This is currently
equivalent to doing namespace.setVariable(name, null);


Maybe we should document this in our JSR223 sampler as this is different to the
BeanShell sampler which seems to display the opposite behaviour i.e. all the
above tests only match == null not == void - this looks more like a bug to me,
but is perhaps less intuitive when mixed with Java code.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message