AnsweredAssumed Answered

Tests failing on fresh checkout

Question asked by ashish on Feb 22, 2008
Latest reply on Feb 25, 2008 by janv
We just started on a project where we have decided to use Alfresco as the CMS tool. As we might be making some modifications, and adding some features specific to our requirement, I was trying to do an initial checkout and run all the tests to ensure that we started from a clean base. But we hit a roadblock with some of the tests failing.
First one which failed was RegistryServiceImplTest.testProperUsage. We had some issue with these assertions:

assertNull("Missing key should return null value. Returned: " + registryService.getProperty(KEY_A_B_C_0), registryService.getProperty(KEY_A_B_C_0));
assertNull("Missing key should return null value. Returned: " + registryService.getProperty(KEY_A_B_C_D_0), registryService.getProperty(KEY_A_B_C_D_0));
assertNull("Missing key should return null value. Returned: " + registryService.getProperty(KEY_X_Y_Z_0), registryService.getProperty(KEY_X_Y_Z_0));


To find out if everything else was ok, we commented those three lines, then we got another failing test - ADMLuceneTest. The test result snippet here:
<failure message="expected:<1> but was:<0>" type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: expected:<1> but was:<0> at org.alfresco.repo.search.impl.lucene.ADMLuceneTest.runBaseTests(ADMLuceneTest.java:3765) at org.alfresco.repo.search.impl.lucene.ADMLuceneTest.testSortIssue_AR_1515__AND__AR_1466(ADMLuceneTest.java:481)</failure>


I am wondering what we could be missing in the setup, as we haven't made any changes yet to cause the tests to fail.

Outcomes