The unit tests generally use a separate version of jmeter.properties - testfiles/jmetertest.properties.
This was done originally to fix up some issues that applied only to tests.
However there is a problem with this, as changes to the standard properties may not be picked up in unit tests.
It would be better to rely on the standard default properties, and only override specific properties for tests if actually needed (e.g. logging level might need to be adjusted).
Similarly for batch tests; these use jmeter-batch.properties.
It would be better to use jmeter.properties and override as necessary using the -q command-line flag.

It's slightly tricky to fix the batch tests because these rely on the log file being empty. However only the initial property file is loaded before the settings are checked and logging started.
URL: http://svn.apache.org/viewvc?rev=1749218&view=rev
Log:
Use jmeter.properties for testing whenever possible
Fix batch tests
Bugzilla Id: 59723
Modified:
jmeter/trunk/build.xml

This is ASF Bugzilla: the Apache Software Foundation bug system. In case
of problems with the functioning of ASF Bugzilla, please contact
bugzilla-admin@apache.org.
Please Note: this e-mail address is only for reporting problems
with ASF Bugzilla. Mail about any other subject will be silently
ignored.