commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Vandahl (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCS-114) Test failures under Java 7 caused by different order of tests
Date Mon, 21 Apr 2014 17:17:16 GMT

     [ https://issues.apache.org/jira/browse/JCS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Vandahl resolved JCS-114.
--------------------------------

       Resolution: Fixed
    Fix Version/s: jcs-2.0.0
         Assignee: Thomas Vandahl

The tests in question have been run successfully under Windows 7 with JDK 1.7u51 after the
lifecycle of CompositeCacheManager has been fixed.

> 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
>            Assignee: Thomas Vandahl
>             Fix For: jcs-2.0.0
>
>
> 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)

Mime
View raw message