commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TestSuiteReductionResearch <>
Subject [GitHub] commons-lang pull request #171: Removing test redundant for org.apache.commo...
Date Fri, 15 Jul 2016 17:32:50 GMT
GitHub user TestSuiteReductionResearch opened a pull request:

    Removing test redundant for org.apache.commons.lang3.ClassUtilsTest.testWrapperToPrimitiveNoWrapper

    We are researchers working on identifying redundant tests in a test suite. Our analysis
of finding redundant tests involve each test's dynamic code coverage and their potential fault-detection
    Through our analysis, we found that the tests org.apache.commons.lang3.ClassUtilsTest.testWrapperToPrimitiveNoWrapper,
org.apache.commons.lang3.ClassUtilsTest.testWrapperToPrimitiveNull are redundant with respect
to one another. In this pull request, we are proposing to keep only the test org.apache.commons.lang3.ClassUtilsTest.testWrapperToPrimitiveNoWrapper
while adding @Ignore annotations to the remaining test. However, as we believe these tests
are identical, any one of them can be kept while skipping the remaining test.
    If you do not believe any of these tests should be ignored, we would greatly appreciate
it if you could follow up on this pull request and let us know your reasons.

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

    $ git pull redundant0

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

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

    This closes #171
commit ed27ea4132fbe36d0aec804f21b960c9505f80b0
Author: TestSuiteReductionResearch <>
Date:   2016-07-15T17:31:14Z

    Ignoring test that is redundant for org.apache.commons.lang3.ClassUtilsTest.testWrapperToPrimitiveNoWrapper


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 or file a JIRA ticket
with INFRA.

View raw message