commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (JCS-114) Test failures under Java 7 caused by different order of tests
Date Mon, 07 Apr 2014 10:43:15 GMT


Sebb commented on JCS-114:

The test failure:
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:
>             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
>  org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCachePoolAccessManagerUnitTest#testConfigurePoolAccessAttributes_Simple
>  org.apache.commons.jcs.engine.memory.lru.LHMLRUMemoryCacheUnitTest#testGetStatsThroughHub
>  org.apache.commons.jcs.engine.SystemPropertyUsageUnitTest#testSystemPropertyUsage_inactive
>  org.apache.commons.jcs.engine.SystemPropertyUsageUnitTest#testSystemPropertyUsage AssertionFailedError
> {code}
> AFAICT these failures occur because Java 7 runs tests in a different order from Java
> 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

View raw message