[Bug 59723] New: Use jmeter.properties when testing whenever possible

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=59723

            Bug ID: 59723
           Summary: Use jmeter.properties when testing whenever possible
           Product: JMeter
           Version: 3.0
          Hardware: PC
                OS: Mac OS X 10.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: sebb@apache.org

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 59723] Use jmeter.properties for testing whenever possible

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=59723

Sebb <se...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Use jmeter.properties when  |Use jmeter.properties for
                   |testing whenever possible   |testing whenever possible

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 59723] Use jmeter.properties for testing whenever possible

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=59723

--- Comment #1 from Sebb <se...@apache.org> ---
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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 59723] Use jmeter.properties for testing whenever possible

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=59723

Sebb <se...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Sebb <se...@apache.org> ---
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

-- 
You are receiving this mail because:
You are the assignee for the bug.