Summary: | Use jmeter.properties for testing whenever possible | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Sebb <sebb> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Mac OS X 10.1 |
Description
Sebb
2016-06-19 21:39:57 UTC
URL: http://svn.apache.org/viewvc?rev=1749211&view=rev Log: Use jmeter.properties for testing whenever possible Fix unit tests Bugzilla Id: 59723 Removed: jmeter/trunk/bin/testfiles/jmetertest.properties Modified: jmeter/trunk/build.xml jmeter/trunk/test/src/org/apache/jmeter/junit/JMeterTestCase.java jmeter/trunk/test/src/org/apache/jmeter/junit/JMeterTestCaseJUnit3.java URL: http://svn.apache.org/viewvc?rev=1749212&view=rev Log: Use jmeter.properties for testing whenever possible Fix unit tests Bugzilla Id: 59723 Modified: jmeter/trunk/xdocs/changes.xml 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 issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4007 |