[jira] [Closed] (CONTINUUM-2751) Build fails due to test interactions: data not being cleaned consistently

["Brent N Atkinson (JIRA)" <ji...@apache.org>]

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

Brent N Atkinson closed CONTINUUM-2751.
---------------------------------------
    Resolution: Fixed

In r1673303 the acute issue (failing build) was fixed by adding a tear-down method to {{AbstractDao}}  which cleared its database, leaving it clean for the subsequent tests.

In r1673317 the non-working (but verbose) db-per-test-method scheme implemented in {{AbstractContinuumTest}} and {{AbstractPurgeTest}} were fixed. There should be little performance penalty since the exact same setup was being performed, but now it is actually used. Now subclasses of these test cases will have a new database for each test method invocation.

> Build fails due to test interactions: data not being cleaned consistently
> -------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2751
>                 URL: https://issues.apache.org/jira/browse/CONTINUUM-2751
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Brent N Atkinson
>            Assignee: Brent N Atkinson
>             Fix For: 1.5.0
>
>
> Very similar in spirit to CONTINUUM-2736, tests are not well-behaved which is leading to build instability. On continuum-ci.a.o, I noticed the builds were consistently failing despite the full test suite comprehensively passing locally.
> The problem is visible in the build results as the test failure: 
> {noformat}
> Results :
> Failed tests:   testRemoveRepository(org.apache.continuum.repository.DefaultRepositoryServiceTest): check # repositories expected:<1> but was:<2>
> Tests run: 150, Failures: 1, Errors: 0, Skipped: 0
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)