You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by TestSuiteReductionResearch <gi...@git.apache.org> on 2016/07/21 20:41:40 UTC
[GitHub] commons-lang pull request #175: Removing test redundant for org.apache.commo...
GitHub user TestSuiteReductionResearch opened a pull request:
https://github.com/apache/commons-lang/pull/175
Removing test redundant for org.apache.commons.lang3.StringUtilsTest.testIsEmpty
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.StringUtilsTest.testIsEmpty, org.apache.commons.lang3.StringUtilsTrimEmptyTest.testIsEmpty are redundant with respect to one another. In this pull request, we are proposing to keep only the test org.apache.commons.lang3.StringUtilsTest.testIsEmpty 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 redundant0
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/commons-lang/pull/175.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 #175
----
commit cced83d0affc0328b85dce74c97bb3a9be54dfb9
Author: TestSuiteReductionResearch <te...@gmail.com>
Date: 2016-07-21T20:39:53Z
Ignoring test that is redundant for org.apache.commons.lang3.StringUtilsTest.testIsEmpty
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] commons-lang issue #175: Removing test redundant for org.apache.commons.lang...
Posted by coveralls <gi...@git.apache.org>.
Github user coveralls commented on the issue:
https://github.com/apache/commons-lang/pull/175
[](https://coveralls.io/builds/7109864)
Coverage decreased (-0.02%) to 93.418% when pulling **cced83d0affc0328b85dce74c97bb3a9be54dfb9 on TestSuiteReductionResearch:redundant0** into **bd9adbb637a8a4aa5eb61c6fde2c576d0ab3c4fa on apache:master**.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] commons-lang pull request #175: Removing test redundant for org.apache.commo...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/commons-lang/pull/175
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] commons-lang issue #175: Removing test redundant for org.apache.commons.lang...
Posted by PascalSchumacher <gi...@git.apache.org>.
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-lang/pull/175
Thanks for identifying the redundant tests.
Dead code should be removed, so I deleted the tests.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---