> On Jan 6, 2016, at 7:33 AM, Chris Pike <[email protected]> wrote: > > I made the change and submitted a pull request on github, however I got an > error when trying to run the junit tests. I reverted the code and still get > the same error when running the test so it is not an issue with something I > changed. I put the error in the github comment.
Yes I saw this comment on the pull request: > On Jan 5, 2016, at 12:47 PM, pike1212 <[email protected]> wrote: > > I renamed the duplicate set methods. My junit tests don't work even before I > made the change, so not sure how to propertly test. This is the error I get > when running "mvn test -Dtest=FortressJUnitTest" > > > Tests run: 141, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 228.481 > sec <<< FAILURE! - in > org.apache.directory.fortress.core.impl.FortressJUnitTest > testSearchBinds(org.apache.directory.fortress.core.impl.AuditMgrImplTest) > Time elapsed: 0.022 sec <<< FAILURE! > junit.framework.AssertionFailedError: > org.apache.directory.fortress.core.impl.AuditMgrImplTestsearchBinds failed > search for successful authentication user [jtsUser1] > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at > org.apache.directory.fortress.core.impl.AuditMgrImplTest.searchBinds(AuditMgrImplTest.java:426) > at > org.apache.directory.fortress.core.impl.AuditMgrImplTest.testSearchBinds(AuditMgrImplTest.java:399) Which prolly means your audit isn’t enabled to log events. I recently changed the flags in the build.properties to address this issue of audit being inadvertently disabled in the Jenkins build tests. This is the old flag: enable.audit=true which has been inverted to: disable.audit=false And the default for disable.audit is (was intended to be) ‘false’. Please make sure that it has been added to your build.properties and run the regression tests again. Thanks, Shawn
