[jira] [Commented] (JCS-114) Test failures under Java 7 caused by different order of tests

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961771#comment-13961771 ] 

Sebb commented on JCS-114:
--------------------------

The test failure:
org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCachePoolAccessManagerUnitTest#testConfigurePoolAccessAttributes_Simple ComparisonFailure
is caused by failure to call JDBCDiskCachePoolAccessManager.setProps in both methods.
However see bug JCS-115 as the class design is currently broken


> Test failures under Java 7 caused by different order of tests
> -------------------------------------------------------------
>
>                 Key: JCS-114
>                 URL: https://issues.apache.org/jira/browse/JCS-114
>             Project: Commons JCS
>          Issue Type: Bug
>            Reporter: Sebb
>
> ON Java 7 under WinXP I get several test failures. These do not occur with Java 6. The failures are:
> {code}
>  org.apache.commons.jcs.access.SystemPropertyUnitTest#testSystemPropertyInValueDelimiter AssertionFailedError
>  org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCachePoolAccessManagerUnitTest#testConfigurePoolAccessAttributes_Simple ComparisonFailure
>  org.apache.commons.jcs.engine.memory.lru.LHMLRUMemoryCacheUnitTest#testGetStatsThroughHub AssertionFailedError
>  org.apache.commons.jcs.engine.SystemPropertyUsageUnitTest#testSystemPropertyUsage_inactive AssertionFailedError
>  org.apache.commons.jcs.engine.SystemPropertyUsageUnitTest#testSystemPropertyUsage AssertionFailedError
> {code}
> AFAICT these failures occur because Java 7 runs tests in a different order from Java 6.
> In each case, the test class has 2 tests.
> Either the Unit tests are wrong - e.g. the second test relies on something set up by an earlier test, or the second test fails to clear up afterwards so causes a problem when the test order is reversed.
> Otherwise there must be a problem in the code under test - e.g. the code caches a value that it should not.



--
This message was sent by Atlassian JIRA
(v6.2#6252)