GitHub user benbenw opened a pull request:

    https://github.com/apache/jmeter/pull/85

    Bug 58897 : part 1

    - Move jorphan class finder to a more flexible solution when searching for 
classes (visitor / filter pattern)
    - Use it as preparatory step in Jorphan AllTests
    - Explicitly exclude JMeterTest and TestMenuFactory in headless mode
    - remove commented code & outdated comments
    
    No change in the number of executed tests *
    
    * in headless mode TestMenuFactory is now excluded, it was previously
    running as a side effect of the *strange* exception management, but it
    need a graphics environment.
    
    Jorphan AllTests is a stinky monkey.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/benbenw/jmeter classfinder

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jmeter/pull/85.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #85
    
----
commit cb516529c7bed237be1d4c2a8134df48366ba19f
Author: benoit <[email protected]>
Date:   2016-01-18T10:03:42Z

    - Move jorphan class finder to a more flexible solution when searching
    for
    classes (visitor / filter pattern)
    - Use it as preparatory step in Jorphan AllTests
    - Explicitly exclude JMeterTest and TestMenuFactory in headless mode
    - remove commented code & outdated comments
    
    No change in the number of executed tests *
    
    * in headless mode TestMenuFactory is now excluded, it was previously
    running as a side effect of the *strange* exception management, but it
    need a graphics environment.
    
    Jorphan AllTests is a stinky monkey.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to