[INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Bitrepository Reference Pillar 1.7-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-reference-pillar --- [INFO] [INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack-shared-sqlscripts) @ bitrepository-reference-pillar --- [INFO] Unpacking /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-service/target/bitrepository-service-1.7-SNAPSHOT.jar to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes with includes "**/*.sql" and excludes "" [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-reference-pillar --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 10 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-reference-pillar --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 44 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-reference-pillar --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 12 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-reference-pillar --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 70 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-reference-pillar --- [INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running TestSuite Configuring TestNG with: TestNG652Configurator Starting test project Reference Pillar Test Suite: Surefire suite Starting testcase ArchiveDirectoryTest Test starting: testArchiveDirectoryExistingFile Description: Test the ArchiveDirectory when the file exists Step: Setup Step: Validate the existence of the file Step: Delete the file. Test success: testArchiveDirectoryExistingFile Test starting: testArchiveDirectoryMissingFile Description: Test the ArchiveDirectory when the file is missing. Step: Setup Step: Validate the existence of the file Step: Delete the file. Test success: testArchiveDirectoryMissingFile Test starting: testArchiveDirectoryMoveFileToArchive Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory. Step: Setup Step: Moving file from tmp to archive Step: Create file in both tmp and archive. Step: Moving file from tmp to archive Step: Remove the file from archive and try again Test success: testArchiveDirectoryMoveFileToArchive Test starting: testArchiveDirectoryNewFile Description: Testing the ArchiveDirectory handling of a new file. Step: Setup Step: Retrieve tmp file Step: Request a new file for the tmp dir Step: Retrieve tmp file Step: Request another new file with the same name Step: Move the file from tmp to archive Test success: testArchiveDirectoryNewFile Test starting: testArchiveDirectoryRemoveFile Description: Testing the error scenarios when removing files from the archive. Step: Setup Step: Remove nonexisting file from archive Step: Remove nonexisting file from tmp Step: Create file in both tmp, archive and retain directories. Step: Remove the file from archive and tmp Test success: testArchiveDirectoryRemoveFile Starting testcase ChecksumEntryTest Test starting: testExtendedTestCase Description: Test the ChecksumEntry Step: Create a ChecksumEntry Step: Change the value of the checksum Step: Change the value of the calculation date Test success: testExtendedTestCase Starting testcase ChecksumPillarModelTest Test starting: testPillarModelBasicFunctionality Description: Test the basic functions of the full reference pillar model. Step: Check the pillar id in the pillar model Step: Ask whether it can handle a file of size 0 Step: Ask whether it can handle a file of maximum size Step: Check the ChecksumPillarSpec Step: Checkum whether the checksum pillar should download Test success: testPillarModelBasicFunctionality Test starting: testPillarModelHasFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and retrieve it. Step: Check whether file exists. Step: Ask for the checksum data for the file with different checksum specs Step: Ask for the checksum entry for the file with different checksum specs Step: Ask for the checksum for the file with different checksum specs Step: Check extraction of checksum result set Step: Check retrieval of non-default checksum Step: Check retrieval of non-default checksum result set Step: Test retrieval of single checksum result set Test success: testPillarModelHasFile Test starting: testPillarModelNoFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and try to retrieve it. Step: Verify that anexceptions are thrown when verifying file existance. Test success: testPillarModelNoFile Starting testcase GetFileIDsTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the identify request message. 02:25:17.095 WARN o.b.p.m.IdentifyPillarsForGetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseIdentification' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@6b5966e1[correlationID=e171911b-fcf5-402d-9409-2bc6dbe75bec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@65e61854[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1568159[fileID=DefaultFilebadCaseIdentification, allFileIDs=], timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoFile Description: Tests the GetFileIDs functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for not having the file Step: Create and send the actual GetFileIDs message to the pillar. 02:25:18.955 WARN o.b.p.m.GetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@52eacb4b[correlationID=2083e5d8-670e-4cc1-bd12-915542b1e62d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5528a42c[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2a551a63[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=], resultingFileIDs=, partialResult=] Step: Retrieve the FinalResponse for the GetFileIDs request Test success: badCaseOperationNoFile Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a GetFileIDs operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@19542407[correlationID=85c98821-9fd4-417f-a357-7b5069660c60, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6f95cd51[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@c7a977f[fileID=DefaultFilegoodCaseIdentification, allFileIDs=], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@55caeb35[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Starting testcase MediatorTest Test starting: testMediatorRuntimeExceptionHandling Description: Tests the handling of a runtime exception Step: Setup create and start the mediator. Step: Send a request to the mediator. 02:25:25.246 WARN o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught. java.lang.RuntimeException: I am supposed to throw a RuntimeException at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122) ~[test-classes/:na] at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113) ~[test-classes/:na] at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:80) ~[classes/:na] at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101) [bitrepository-service-1.7-SNAPSHOT.jar:1.7-SNAPSHOT] at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT] at org.bitrepository.protocol.messagebus.SimpleMessageBus$$Lambda$1/1533547487.accept(Unknown Source) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT] at java.lang.Iterable.forEach(Iterable.java:75) [na:1.8.0_11] at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73) [bitrepository-core-1.7-SNAPSHOT.jar:1.7-SNAPSHOT] at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84) [test-classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_11] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_11] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_11] at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_11] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng-6.8.8.jar:na] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng-6.8.8.jar:na] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng-6.8.8.jar:na] at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng-6.8.8.jar:na] at org.testng.TestRunner.run(TestRunner.java:617) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305) [testng-6.8.8.jar:na] at org.testng.SuiteRunner.run(SuiteRunner.java:254) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng-6.8.8.jar:na] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng-6.8.8.jar:na] at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng-6.8.8.jar:na] at org.testng.TestNG.run(TestNG.java:1057) [testng-6.8.8.jar:na] at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112) [surefire-testng-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) [surefire-booter-2.17.jar:2.17] at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) [surefire-booter-2.17.jar:2.17] Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@6edaa77a[correlationID=044c6e1f-89a7-4697-87cc-bebc7faad5e2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1e63d216[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=] 02:25:25.256 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@16c3ca31[origDateTime=2016-01-29T02:25:25.254+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=, collectionID=] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2d195ee4[correlationID=446aa75a-88b4-4652-903b-599c74568d60, collectionID=, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@16c3ca31[origDateTime=2016-01-29T02:25:25.254+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=, collectionID=]] Test success: testMediatorRuntimeExceptionHandling Starting testcase RecalculateChecksumWorkflowTest Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection Test starting: testWorkflowDoesNotRecalculateWhenNotNeeded Description: Test that the workflow does not recalculates the workflows, when the maximum age has not yet been met. Step: Create and run workflow Test success: testWorkflowDoesNotRecalculateWhenNotNeeded Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection Test starting: testWorkflowRecalculatesChecksum Description: Test that the workflow recalculates the workflows, when the maximum age has been met. Step: Create and run workflow Test success: testWorkflowRecalculatesChecksum Starting testcase ReplaceFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a ReplaceFile operation on the pillar for the failure scenario, when the file does not exist. Step: Set up constants and variables. Step: Setup for not having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@27a2a089[correlationID=41d5ea53-69c8-4132-8230-a845556aa752, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@54657dd2[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationMissingFile Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for not having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationMissingFile-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@9fc9f91[correlationID=b9708df1-8611-4c82-a617-8658e58261c5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1fac1d5c[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] Step: Retrieve the FinalResponse for the ReplaceFile request Test success: badCaseOperationMissingFile Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoDestructiveChecksum Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the destructive action, but though is required. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@7b306b9f[correlationID=293771f9-584a-4f21-badf-62b829d6927b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@142213d5[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for file to be deleted during the replacing operation is required.], pillarID=Pillar-badCaseOperationNoDestructiveChecksum, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:25:30.743 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@934b52f[origDateTime=2016-01-29T02:25:30.743+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@2630dbc4[correlationID=1fec323f-44fe-44b0-92ce-a02cb9bb8ff1, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@934b52f[origDateTime=2016-01-29T02:25:30.743+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationNoDestructiveChecksum Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoValidationChecksum Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the new file, but though is required. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@7add838c[correlationID=802aeb30-28f1-4ec1-981c-3c38fb2e48fa, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3662bdff[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for new file in the replacing operation is required.], pillarID=Pillar-badCaseOperationNoValidationChecksum, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:25:31.221 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1bb15351[origDateTime=2016-01-29T02:25:31.221+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4fa822ad[correlationID=a2824758-1922-4225-a949-1e09ac29ee35, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@1bb15351[origDateTime=2016-01-29T02:25:31.221+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationNoValidationChecksum Added fixture: Initialize a new Pillar. Test starting: badCaseOperationWrongDestructiveChecksum Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the checksum for the destructive action is different from the one in the cache. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. 02:25:31.615 WARN o.b.p.m.ReplaceFileRequestHandler - Failed to handle replace operation on file 'DefaultFile' since the request had the checksum '1234cccccccc4321' where our local file has the value '1234cccccccc4322'. Sending alarm and respond failure. Result: Received message on TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@57545c3f[correlationID=a7a68a9c-d97d-4d1e-afe4-060b5ddd618a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@326e0b8e[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum.], pillarID=Pillar-badCaseOperationWrongDestructiveChecksum, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] 02:25:31.617 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@36baa049[origDateTime=2016-01-29T02:25:31.617+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@41184371[correlationID=886a0e47-4aa6-4595-ab96-9c2c4e7f4647, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@36baa049[origDateTime=2016-01-29T02:25:31.617+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the ReplaceFile request Step: Pillar should have sent an alarm Test success: badCaseOperationWrongDestructiveChecksum Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a ReplaceFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@441fbe89[correlationID=220baccd-7d08-4250-9c17-825ee2815755, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6088451e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@45ab3bdd[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Added fixture: Initialize a new Pillar. Test starting: goodCaseOperation Description: Tests the ReplaceFile operation on the pillar for the success scenario. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@39de9bda[correlationID=07d847bf-338f-4826-bbcc-4339ea0af96b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@47148f3f[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@6dee8ae6[correlationID=07d847bf-338f-4826-bbcc-4339ea0af96b, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5af64ce0[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=, checksumDataForNewFile=] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the ReplaceFile request Test success: goodCaseOperation Added fixture: Initialize a new Pillar. Test starting: goodCaseOperationWithChecksumsReturn Description: Tests the ReplaceFile operation on the pillar for the success scenario, when requesting both the cheksums of the file returned. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@7f4596d0[correlationID=997acbc1-cb80-41f3-8ad3-9cb123c2c7b7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6002e944[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@588545ac[correlationID=997acbc1-cb80-41f3-8ad3-9cb123c2c7b7, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2b08772d[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=, fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@78a8978a[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@f171912[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2016-01-29T02:25:34.788+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@7d4d8579[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@159424e2[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:25:34.789+01:00]] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the ReplaceFile request Test success: goodCaseOperationWithChecksumsReturn Starting testcase ChecksumDatabaseMigrationTest Test starting: testMigratingDatabaseChecksumsTable Description: Tests that the checksums table can be migrated from version 1 to 2, e.g. getting the column collectionid, which should be set to the default in settings. Step: Validate setup Step: Ingest a entry to the database without the collection id Step: Perform migration 02:25:40.856 WARN o.b.service.database.DatabaseUtils - Migrating the checksums table from version 1 to 2 in the ChecksumDatabase. 02:25:41.082 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 2 to 3. Step: Validate the entry Test success: testMigratingDatabaseChecksumsTable Starting testcase ChecksumDatabaseTest Test starting: testChecksumDatabaseExtraction Description: Test the extraction of data from the checksum database. Step: Check whether the default entry exists. Step: Extract calculation date Step: Extract the checksum Step: Extract the whole entry Step: Extract all entries Test success: testChecksumDatabaseExtraction Test starting: testDeletion Description: Test that data can be deleted from the database. Step: Check whether the default entry exists. Step: Remove the default entry Test success: testDeletion Test starting: testExtractionOfMissingData Description: Test the handling of bad arguments. Step: Try to get the date of a wrong file id. Step: Try to get the date of a wrong file id. Step: Try to remove a bad file id Test success: testExtractionOfMissingData Test starting: testGetFileIDsRestrictions Description: Tests the restrictions on the GetFileIDs call to the database. Step: Instantiate database with appropriate data. Step: Test with no time restrictions and 10000 max_results Step: Test with minimum-date earlier than first file Step: Test with maximum-date earlier than first file Step: Test with minimum-date set to later than second file. Step: Test with maximum-date set to later than second file. Step: Test with minimum-date set to middle date. Step: Test with maximum-date set to middle date. Step: Test with both minimum-date and maximum-date set to middle date. Step: Test the first file-id, with no other restrictions Step: Test the second file-id, with no other restrictions Step: Test the date for the first file-id, while requesting the second file-id Test success: testGetFileIDsRestrictions Test starting: testReplacingExistingEntry Description: Test that an entry can be replaced by another in the database. Step: Check whether the default entry exists. Step: Replace the checksum and date Test success: testReplacingExistingEntry Test starting: testSpecifiedEntryExtraction Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch. Step: Instantiate database with appropriate data. Step: Extract with out restrictions Step: Extract with a maximum of 1 entry Step: Extract all dates older than this tests instantiation Step: Extract all dates newer than this tests instantiation Step: Extract all dates older than the newest instance Step: Extract all dates newer than the oldest instantiation Test success: testSpecifiedEntryExtraction Starting testcase FullPillarModelTest Test starting: testPillarModelBasicFunctionality Description: Test the basic functions of the full reference pillar model. Step: Check the pillar id in the pillar model Step: Ask whether it can handle a file of size 0 Step: Ask whether it can handle a file of maximum size Step: Check the ChecksumPillarSpec Test success: testPillarModelBasicFunctionality Test starting: testPillarModelHasFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and retrieve it. Step: Verify that no exceptions are thrown when verifying file existance. Step: Check retrieval of non-default checksum Test success: testPillarModelHasFile Test starting: testPillarModelNoFile Description: Test that the file exists, when placed in the archive and cache Step: Setup Step: Check whether file exists and try to retrieve it. Step: Verify that anexceptions are thrown when verifying file existance. 02:26:13.634 WARN o.b.pillar.store.FileStorageModel - The file 'DefaultFile' has been requested, but we do not have that file in collection 'TwoPillarCollection'! Test success: testPillarModelNoFile Starting testcase GetAuditTrailsTest Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsMaximumNumberOfResults Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a limited number of audit trails are requested. Step: Set up constants and variables. Step: Send the request for the limited amount of audit trails to the pillar. Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@6a3a56de[correlationID=14767aa8-2dc9-4d0a-b4fc-911ac306e66a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2ed84be9[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@7cf66cf9[correlationID=14767aa8-2dc9-4d0a-b4fc-911ac306e66a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@38f63756[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@3d7caf9c[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4e26040f[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@1782896[sequenceNumber=1, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2016-01-29T02:26:14.246+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@8bde368[sequenceNumber=2, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2016-01-29T02:26:14.247+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@5065bdac[sequenceNumber=3, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2016-01-29T02:26:14.247+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@2e9dcdd3[sequenceNumber=4, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2016-01-29T02:26:14.247+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@6e617c0e[sequenceNumber=5, fileID=fileID1454030774246, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2016-01-29T02:26:14.247+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=true] Step: Validate the final response Test success: checksumPillarGetAuditTrailsMaximumNumberOfResults Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsSpecificRequests Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a specific audit trail are requested. Step: Set up constants and variables. Step: Send the identification request Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@60b4c754[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2c846d55[responseCode=IDENTIFICATION_POSITIVE, responseText=]] Step: Retrieve and validate the response. Step: Make and send the request for the actual GetAuditTrails operation Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@67689c81[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@21a0795f[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@2ec156fb[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@56d742ad[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@75784062[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@5730b513[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@73e25780[sequenceNumber=1, fileID=fileID1454030774582, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2016-01-29T02:26:14.582+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Step: Make another request, where both ingested audit trails is requested Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@1f4cb17b[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@280099a0[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@7aca299e[correlationID=b22f6d32-6cda-4b2e-80ac-b988b452e285, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1bf52f10[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@6148827c[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4da9da6c[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@73e25780[sequenceNumber=1, fileID=fileID1454030774582, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2016-01-29T02:26:14.582+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@66048c9e[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2016-01-29T02:26:14.582+01:00, info=badInfo, operationID=operationID, certificateID=certificateid, auditTrailInformation=WrongAuditTrail]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Test success: checksumPillarGetAuditTrailsSpecificRequests Added fixture: Initialize a new Pillar. Test starting: checksumPillarGetAuditTrailsSuccessful Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where all audit trails are requested. Step: Set up constants and variables. Step: Send the identification request Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@1820f274[correlationID=bb7c3c0b-7f43-40da-8fc9-74ad11ebf1a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@221cdd87[responseCode=IDENTIFICATION_POSITIVE, responseText=]] Step: Make and send the request for the actual GetAuditTrails operation Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@4d66cb[correlationID=bb7c3c0b-7f43-40da-8fc9-74ad11ebf1a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@7c79f2cf[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=] Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@63551c66[correlationID=bb7c3c0b-7f43-40da-8fc9-74ad11ebf1a8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2761156e[responseCode=OPERATION_COMPLETED, responseText=], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@4cf15477[resultAddress=, auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@7fad28ac[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@3450bd13[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2016-01-29T02:26:14.715+01:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false] Step: Receive and validate the progress response. Step: Receive and validate the final response Test success: checksumPillarGetAuditTrailsSuccessful Starting testcase GetChecksumsTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a GetChecksums operation on the pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@67e1a5fd[correlationID=eba12064-ce96-4227-bd58-4d552c2da060, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4b9dc62f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6cb3463b[fileID=DefaultFilebadCaseIdentification, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2f9236d8[checksumType=MD5, checksumSalt=, otherChecksumType=], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoFile Description: Tests the GetChecksums functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for not having the file Step: Create and send the actual GetChecksums message to the pillar. 02:26:16.361 WARN o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@634d3439[correlationID=ca4e7636-50a3-4f1e-962f-b7f60af5ebc5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@44e0c3d[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71891d6b[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] 02:26:16.395 WARN o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2259d54f[correlationID=ca4e7636-50a3-4f1e-962f-b7f60af5ebc5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1b82f62a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71891d6b[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] Step: Retrieve the FinalResponse for the GetChecksums request Test success: badCaseOperationNoFile Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2259d54f[correlationID=ca4e7636-50a3-4f1e-962f-b7f60af5ebc5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1b82f62a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71891d6b[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] 02:26:17.414 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2259d54f[correlationID=ca4e7636-50a3-4f1e-962f-b7f60af5ebc5, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1b82f62a[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@71891d6b[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=, partialResult=] Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a GetChecksums operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@53b7f08[correlationID=5f4da59b-ae1e-4191-af26-19bfccd3ee25, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@24536f07[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@32430075[fileID=DefaultFilegoodCaseIdentification, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1a45e29f[checksumType=MD5, checksumSalt=, otherChecksumType=], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@44580de0[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Added fixture: Initialize a new Pillar. Test starting: goodCaseOperationAllFiles Description: Tests the GetChecksums operation on the pillar for the successful scenario, when requesting all files. Step: Set up constants and variables. Step: Setup for having the file and delivering result-set Step: Create and send the actual GetChecksums message to the pillar. Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@7bb3294c[correlationID=f6b3cbd0-9990-45bb-a07a-c64e1b56f883, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@f391e52[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5857d723[fileID=, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4b518645[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@4fea9f19[correlationID=f6b3cbd0-9990-45bb-a07a-c64e1b56f883, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@37a14aa1[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4b518645[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@6ac4f31d[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@106f2425[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:26:19.152+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@b666366[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1454030779141, checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=1970-01-01T01:00:00.000+01:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: goodCaseOperationAllFiles Added fixture: Initialize a new Pillar. Test starting: goodCaseOperationSingleFile Description: Tests the GetChecksums operation on the pillar for the successful scenario when requesting one specific file. Step: Set up constants and variables. Step: Setup for having the file and delivering result-set Step: Create and send the actual GetChecksums message to the pillar. Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@2d1f9ec3[correlationID=af7b9540-478c-4ea1-82af-fd47340987fc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@148f94dc[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2f11d889[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d1973e8[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@5ca10d0e[correlationID=af7b9540-478c-4ea1-82af-fd47340987fc, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@34604b32[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@d1973e8[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@159408a7[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@5354bfce[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:26:19.618+01:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: goodCaseOperationSingleFile Added fixture: Initialize a new Pillar. Test starting: testRestrictions Description: Tests that the restrictions are correctly passed on to the cache. Step: Set up constants and variables. Step: Setup for only delivering result-set when the correct restrictions are given. Step: Create and send the actual GetChecksums message to the pillar. Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@b4c89b6[correlationID=f61102e7-57d4-45df-b9da-e35e7f8f9e01, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@54f62ac6[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7be86438[fileID=, allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5fe4848[checksumType=MD5, checksumSalt=, otherChecksumType=], resultAddress=] Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@6a906078[correlationID=f61102e7-57d4-45df-b9da-e35e7f8f9e01, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@fd5c7f6[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5fe4848[checksumType=MD5, checksumSalt=, otherChecksumType=], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@3724ab90[resultAddress=, checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@40ef1934[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:26:19.952+01:00]}], partialResult=false] Step: Retrieve the ProgressResponse for the GetChecksums request Step: Retrieve the FinalResponse for the GetChecksums request Test success: testRestrictions Starting testcase PutFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a PutFile operation on the pillar for the failure scenario, when the file already exists. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@281028ce[correlationID=267a2bd7-a1c5-4324-8623-9ff8e3d14b70, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@46ef7340[responseCode=DUPLICATE_FILE_FAILURE, responseText=], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=, checksumDataForExistingFile=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@75caecf7[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationFileAlreadyExists Description: Tests the PutFile operation on the pillar for the failure scenario, when the file already exists. Step: Set up constants and variables. Step: Setup for already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@7be85f15[correlationID=55e42ea9-9fbc-479e-a7d5-e38dc2eb54ba, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@48619f15[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=, fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=, checksumDataForExistingFile=] Step: Retrieve the FinalResponse for the PutFile request Test success: badCaseOperationFileAlreadyExists Added fixture: Initialize a new Pillar. Test starting: badCasePutOperationNoValidationChecksum Description: Tests the PutFile operation on the pillar for the failure scenario, when no validation checksum is given but required. Step: Set up constants and variables. Step: Setup for not already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@1b897ffb[correlationID=d3f4ebc3-566b-4c90-ab66-8da2563dabd9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2ec258f1[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=, fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=, checksumDataForExistingFile=] 02:26:22.489 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@3074575a[origDateTime=2016-01-29T02:26:22.489+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@7e4bbda4[correlationID=5ca78d2b-8de3-4c62-9c1c-c1bd5e6ef4dc, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@3074575a[origDateTime=2016-01-29T02:26:22.489+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the PutFile request Step: Pillar should have sent an alarm Test success: badCasePutOperationNoValidationChecksum Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a PutFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for not already having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@2c56e044[correlationID=d60d6b3a-1687-46a9-bee7-397f899ba3d6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@d970881[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=, checksumDataForExistingFile=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@153cf928[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Added fixture: Initialize a new Pillar. Test starting: goodCaseOperationWithChecksumReturn Description: Tests the PutFile operation on the pillar for the success scenario, when requesting the cheksum of the file returned. Step: Set up constants and variables. Step: Setup for not already having the file and delivering pillar id, and delivering an answer for the checksum request Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileProgressResponse@2898c70d[correlationID=c841123d-33a0-4a99-ba24-519b7badb063, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@ec67be1[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=, fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt] Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@347f0950[correlationID=c841123d-33a0-4a99-ba24-519b7badb063, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5ab1107d[responseCode=OPERATION_COMPLETED, responseText=], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=, fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@671561b9[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3aebdb4[checksumType=MD5, checksumSalt=, otherChecksumType=], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2016-01-29T02:26:24.557+01:00], checksumDataForExistingFile=] Step: Retrieve the ProgressResponse for the GetFileIDs request Step: Retrieve the FinalResponse for the PutFile request Test success: goodCaseOperationWithChecksumReturn Starting testcase ReferenceArchiveTest Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection Test starting: testReferenceArchive Description: Test the ReferenceArchive. Step: Setup Step: test 'hasFile' Step: Test 'getFile' Step: Test getAllFileIDs Step: Test 'getFileAsInputstream' Step: Delete, recreate and delete again Step: Try to delete missing file. Step: Replace a file, which does not exist in the filedir. Step: Copy a file into the tmpDir and then use replace. Step: Try performing the replace, when the file in the tempdir has been removed. Test success: testReferenceArchive Starting testcase DeleteFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a DeleteFile operation on the checksum pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@2ef5df8f[correlationID=cc652d04-3776-49da-84a4-5f5f238142f4, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@708f238f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=, timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationMissingVerification Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for delivering pillar id and having the file Step: Create and send the actual DeleteFile message to the pillar. Result: Received message on TEST-TOPIC-badCaseOperationMissingVerification-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@39bd07fe[correlationID=f89b003f-04e3-44fb-99b0-04b835225f64, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5ca896af[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=] 02:26:27.278 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@324ee3ca[origDateTime=2016-01-29T02:26:27.276+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection] Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@639d808a[correlationID=3021fecf-c5ac-4679-9ee7-26536e20eb82, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@324ee3ca[origDateTime=2016-01-29T02:26:27.276+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]] Step: Retrieve the FinalResponse for the DeleteFile request Step: Pillar should have sent an alarm Test success: badCaseOperationMissingVerification Added fixture: Initialize a new Pillar. Test starting: badCaseOperationNoFile Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file. Step: Set up constants and variables. Step: Setup for delivering pillar id and not having the file Step: Create and send the actual DeleteFile message to the pillar. Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@b89cbf9[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2f318251[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@5e352e3a[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1b26f006[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@797dd7ef[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@ece7204[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Step: Retrieve the FinalResponse for the DeleteFile request Test success: badCaseOperationNoFile Result: The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@5e352e3a[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1b26f006[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@797dd7ef[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@ece7204[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] 02:26:28.493 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@5e352e3a[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1b26f006[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@797dd7ef[correlationID=9207916b-e422-464f-b121-bddf0613b1ec, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@ece7204[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=] Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a DeleteFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForDeleteFileResponse@2591477f[correlationID=324286fc-1406-4560-8df0-ef54581806a6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@761d3c20[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@172f2717[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Test starting: componentIDTest Test success: componentIDTest Test starting: getPillarCollectionsTest Test success: getPillarCollectionsTest Starting testcase GeneralMessageHandlingTest Added fixture: Initialize a new Pillar. Test starting: testPillarMessageHandler Description: Test the handling of the PillarMessageHandler super-class. Step: Setup Step: Test the pillar ID Test success: testPillarMessageHandler Starting testcase GetFileTest Added fixture: Initialize a new Pillar. Test starting: badCaseIdentification Description: Tests the identification for a GetFile operation on the checksum pillar for the failure scenario, when the file is missing. Step: Set up constants and variables. Step: Setup for throwing an exception when asked to verify file existence Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@2ae92511[correlationID=ae23cdec-ccd3-48ac-978b-986f5c8cdfee, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@582ce329[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=] Step: Retrieve and validate the response getPillarID() the pillar. Test success: badCaseIdentification Added fixture: Initialize a new Pillar. Test starting: goodCaseIdentification Description: Tests the identification for a GetFile operation on the pillar for the successful scenario. Step: Set up constants and variables. Step: Setup for having the file and delivering pillar id Step: Create and send the identify request message. Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@7f9ebcfe[correlationID=2b2d0b0e-995c-4021-aaac-6afbb0b5b6f8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=28, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3d577add[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@712adc04[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]] Step: Retrieve and validate the response getPillarID() the pillar. Test success: goodCaseIdentification Finished testcase Finished suite Finished project Tests run: 57, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 81.97 sec - in TestSuite Results : Tests run: 57, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT.jar [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar [INFO] [INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar --- [INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-reference-pillar --- [INFO] Reading assembly descriptor: src/main/assembly/assembly.xml [INFO] Reading assembly descriptor: src/test/assembly/assembly.xml [INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml [INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz [WARNING] Entry: bitrepository-reference-pillar-1.7-SNAPSHOT/lib/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar longer than 100 characters. [WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz [INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-pillar --- [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT.pom [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-tests.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-sources.jar [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-distribution.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-deploy.tar.gz [INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.7-SNAPSHOT/bitrepository-reference-pillar-1.7-SNAPSHOT-acceptance-test-deploy.tar.gz [JENKINS] Archiving disabled