GitHub user TestSuiteReductionResearch opened a pull request:

    https://github.com/apache/commons-lang/pull/177

    Removing test redundant for 
org.apache.commons.lang3.builder.DefaultToStringStyleTest.testLongArrayArray

    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 capability.
    
    Through our analysis, we found that the tests 
org.apache.commons.lang3.builder.DefaultToStringStyleTest.testLongArrayArray, 
org.apache.commons.lang3.builder.RecursiveToStringStyleTest.testLongArrayArray 
are redundant with respect to one another. In this pull request, we are 
proposing to keep only the test 
org.apache.commons.lang3.builder.DefaultToStringStyleTest.testLongArrayArray 
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 https://github.com/TestSuiteReductionResearch/commons-lang 
redundant2

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

    https://github.com/apache/commons-lang/pull/177.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 #177
    
----
commit 364fb4be30e12fed7a1ede793af5a56ad15c5961
Author: TestSuiteReductionResearch <[email protected]>
Date:   2016-07-21T20:44:36Z

    Ignoring test that is redundant for 
org.apache.commons.lang3.builder.DefaultToStringStyleTest.testLongArrayArray

----


---
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