[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integrity Service 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integrity-service ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integrity-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 10 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 63 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integrity-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-integrity-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 21 source files to /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integrity-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Integration Service Test
Suite: Surefire suite
Starting testcase BasicIntegrityReporterTest
Test starting: checksumIssuesTest
Description: Verifies that missing files are reported correctly
Step: Report a checksum issue
Step: Report another checksum issue on the same pillar
Step: Report a checksum issue on another pillar
Test success: checksumIssuesTest
Test starting: deletedFilesTest
Description: Verifies that the hasIntegrityIssues() reports deleted files correctly
Step: Report a delete file for a new Reporter
Test success: deletedFilesTest
Test starting: missingChecksumTest
Description: Verifies that missing checksums are reported correctly
Step: Report a missing checksum
Step: Report another missing checksum on the same pillar
Step: Report a missing checksum on another pillar
Test success: missingChecksumTest
Test starting: missingFilesTest
Description: Verifies that missing files are reported correctly
Step: Report a missing file
Step: Report another missing file on the same pillar
Step: Report a missing file on another pillar
Test success: missingFilesTest
Test starting: noIntegrityIssuesTest
Description: Verifies that missing files are reported correctly
Step: Create a clean reporter
Test success: noIntegrityIssuesTest
Test starting: obsoleteChecksumTest
Description: Verifies that obsolete checksums are reported correctly
Step: Report a obsolete checksum
Step: Report another obsolete checksum on the same pillar
Step: Report a obsolete checksum on another pillar
Test success: obsoleteChecksumTest
Starting testcase IntegrityAlerterTest
Test starting: testIntegrityFailed
Description: Test the IntegrityFailed method for the IntegrityAlerter
Step: Call the function for integrity failure.
02:20:41.772 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5f049ea1[origDateTime=2015-10-15T02:20:41.767+02:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4c163e3[correlationID=b6cc3c51-140a-4a0f-a8f0-59e4af47bd1f, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5f049ea1[origDateTime=2015-10-15T02:20:41.767+02:00, alarmCode=INTEGRITY_ISSUE, alarmRaiser=IntegrityAlerterTest, alarmText=Testaintegrity alarm, fileID=<null>, collectionID=TwoPillarCollection]]
Test success: testIntegrityFailed
Test starting: testOperationFailed
Description: Test the OperationFailed method for the IntegrityAlerter
Step: Call the function for integrity failure.
02:20:42.856 WARN o.b.i.a.IntegrityAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@563e4951[origDateTime=2015-10-15T02:20:42.856+02:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4066c471[correlationID=6570544e-17fb-4aea-a781-c30a32b740ea, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-IntegrityAlerterTest-cibuild01-contributor, from=IntegrityAlerterTest, to=<null>, version=28, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@563e4951[origDateTime=2015-10-15T02:20:42.856+02:00, alarmCode=FAILED_OPERATION, alarmRaiser=IntegrityAlerterTest, alarmText=Testing the ability to fail., fileID=<null>, collectionID=TwoPillarCollection]]
Test success: testOperationFailed
Starting testcase IntegrityDatabaseTest
Test starting: initialStateExtractionTest
Description: Tests the initial state of the IntegrityModel. Should not contain any data.
Step: Test the 'findChecksumsOlderThan'
Step: Test the 'findMissingChecksums'
Step: Test the 'findMissingFiles'
Step: Test the 'getAllFileIDs'
Step: Test the 'getFileInfos'
Step: Test the 'getNumberOfFiles'
Test success: initialStateExtractionTest
Test starting: instantiationTest
Description: Tests that the connection can be instantaited.
Test success: instantiationTest
Test starting: testDeletingEntry
Description: Tests the deletion of an FileID entry.
Step: Create data
Step: Delete the entry
Test success: testDeletingEntry
Test starting: testIngestOfChecksumsData
Description: Tests the ingesting of checksums data
Step: Create data
Step: Extract the data
Test success: testIngestOfChecksumsData
Test starting: testIngestOfFileIDsData
Description: Tests the ingesting of file ids data
Step: Create data
Step: Extract the data
Test success: testIngestOfFileIDsData
Starting testcase UpdateFileIDsStepTest
Test starting: testAbortWorkflowWhenNegativeReply
Description: Test the step for updating the file ids will throw an WorkflowAbortedExceptionwhen AbortOnFailedContributor is set to true and a FAILED event is received.
02:21:12.133 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:21:12.134 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testAbortWorkflowWhenNegativeReply
Test starting: testContinueWorkflowWhenNegativeReply
Description: Test the step for updating the file ids will continue when getting an FAILED operation event when AbortOnFailedContributor is set to false
02:21:12.391 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:21:12.392 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Operation failed
Test success: testContinueWorkflowWhenNegativeReply
Test starting: testIngestOfResults
Description: Test the step for updating the file ids can ingest the data correctly into the store.
Test success: testIngestOfResults
Test starting: testPartialResults
Description: Test that the number of partial is used for generating more than one request.
Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time
Test success: testPartialResults
Test starting: testPositiveReply
Description: Test the step for updating the file ids can handle COMPLETE operation event.
Test success: testPositiveReply
Starting testcase FileInfoTest
Test starting: testFileInfo
Description: Tests the FileInfo element. Adds all data and extracts it again.
Step: Setup the file info.
Step: Change the checksum
Step: Change the date for last file id check
Step: Change the date for last checksum check
Test success: testFileInfo
Starting testcase HandleChecksumValidationStepTest
Test starting: testAuditTrailsForChecksumErrors
Description: Test audit trails for checksum errors. Verify that a pillar with a single checksum will be pointed out as the possible cause.
Step: Test step on data without checksum error
Step: Test step on data where only two pillars have the file and they disagree about the checksum.
number of files in the collection2
number of fileinfos: 3
Step: remove the last auditinfo
Step: Test step on data where two pillars have one checksum and the last pillar has a different one
Test success: testAuditTrailsForChecksumErrors
Test starting: testChecksumMajority
Description: Test the checksum integrity validator when two pillars have one checksum and the last pillar has another checksum.
Step: Add data to the cache
Step: Perform the checksum validation step
Step: Validate the file ids
Test success: testChecksumMajority
Test starting: testMissingAtOnePillar
Description: Test the checksum integrity validator when one pillar is missing the data.
Step: Update the cache with identitical data for both pillars.
Step: Perform the step
Step: Validate the file ids
Test success: testMissingAtOnePillar
Test starting: testNoData
Description: Test the checksum integrity validator without any data in the cache.
Step: Validate the file ids
Test success: testNoData
Test starting: testSimilarData
Description: Test the checksum integrity validator when all pillars have similar data.
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testSimilarData
Test starting: testThreeDisagreeingChecksums
Description: Test the checksum integrity validator when all pillars have different checksums.
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testThreeDisagreeingChecksums
Test starting: testTwoDisagreeingChecksums
Description: Test the checksum integrity validator when only two pillar has data, but it it different.
Step: Add data to the cache
Step: Perform the step
Step: Validate the file ids
Test success: testTwoDisagreeingChecksums
Starting testcase IntegrityDBToolsTest
Test starting: testAddCollectionSuccess
Description: Tests that a new collection can be added to the integrity database
Step: Extract initial list of collections
Step: Add the new collection
Test success: testAddCollectionSuccess
Test starting: testAddExistingCollection
Description: Tests that an existing collectionID cannot be added to the integrity database.
Step: Extract initial list of collections.
Step: Attempt to add the new collection.
Test success: testAddExistingCollection
Test starting: testRemoveNonExistingCollection
Description: Tests that a non existing collection can't be removed from the integrity database.
Step: Extract initial list of collections.
Step: Attempt to remove the non-existing collection.
Test success: testRemoveNonExistingCollection
Starting testcase MaxChecksumAgeProviderTest
Test starting: testNoPillarSpecificSetting
Description: Test the MaxChecksumAge when no settings are defined for the specific pillar
Step: Create a MaxChecksumAgeProvider with settings containing a default MaxAge of 10 and no pillar specific settings
Test success: testNoPillarSpecificSetting
Test starting: testNoSettings
Description: Test the MaxChecksumAge when no settings are defined
Step: Create a MaxChecksumAgeProvider with null settings and a default MaxAge of 100
Test success: testNoSettings
Test starting: testPillarSpecificSetting
Description: Test the MaxChecksumAge when a value has been defined for specific pillars
Step: Create a MaxChecksumAgeProvider with settings containing a default MaxAge of 10, pillar1MaxChecksumAge of 1001 and pillar2 MaxChecksumAge of 1002
Test success: testPillarSpecificSetting
Starting testcase IntegrityWorkflowManagerTest
Test starting: collectionSpecificWorkflows
Description: Verifies that the IntegrityWorkflowManager loads correctly for workflows configured for specific collection.
Step: Create a IntegrityWorkflowManager based on a workflow with different schedules for collection 1 and 2 (daily and hourly)
Test success: collectionSpecificWorkflows
Test starting: noWorkflowPackage
Description: Verifies that the IntegrityWorkflowManager loads correctly for at workflow configuration with a workflow class name without a package scope (located in the deafult workflow package).
Step: Create a IntegrityWorkflowManager based on a single Testworkflow with a daily schedule in a to collection system, where the className is just the simplename
Test success: noWorkflowPackage
Test starting: noWorkflowSettings
Description: Verifies that the IntegrityWorkflowManager loads correctly for missing reference settings a workflow settings element.
Step: Create a IntegrityWorkflowManager based on a workflowsettingsless configuration
Test success: noWorkflowSettings
Test starting: normalWorkflowSettings
Description: Verifies that the IntegrityWorkflowManager loads correctly for at normally defined workflow.
Step: Create a IntegrityWorkflowManager based on a single Testworkflow with a daily schedule in a to collection system
Test success: normalWorkflowSettings
Test starting: startWorkflow
Description: Verifies that the that it is possible to manually start a workflow.
Step: Call the startWorkflow with a workflow defined in the configuration
Test success: startWorkflow
Test starting: unscheduledWorkflow
Description: Verifies that the IntegrityWorkflowManager loads workflow correctly for workflows without a defined schedule meaning they are never run automatically.
Step: Create a IntegrityWorkflowManager based on a single Testworkflow without a schedule
Test success: unscheduledWorkflow
Starting testcase UpdateChecksumsStepTest
Test starting: testAbortWorkflowWhenNegativeReply
Description: Test the step for updating the checksums will abort the workflow in case of FAILURE operation event and AbortOnFailedContributor = true .
02:21:38.974 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:21:38.975 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testAbortWorkflowWhenNegativeReply
Test starting: testCallForChangingChecksumStates
Description: Test the step for updating the checksums delivers the results to the integrity model.
Test success: testCallForChangingChecksumStates
Test starting: testContinueWorkflowNegativeReply
Description: Test the step for updating the checksums will continue the workflow in case of FAILURE operation event and AbortOnFailedContributor = false .
02:21:39.221 WARN o.b.i.c.IntegrityCollectorEventHandler - Component failure for 'test-pillar-1'.
02:21:39.221 WARN o.b.i.c.IntegrityCollectorEventHandler - Failure: null: null: FAILED: , Problem encountered
Test success: testContinueWorkflowNegativeReply
Test starting: testFullChecksumCollection
Description: Test that the full list of checksums is requested.
Test success: testFullChecksumCollection
Test starting: testIncrementalChecksumCollection
Description: Test that only the list of new checksums is requested.
Test success: testIncrementalChecksumCollection
Test starting: testIngestOfResults
Description: Test the step for updating the checksums delivers the results to the integrity model.
Test success: testIngestOfResults
Test starting: testPartialResults
Description: Test that the number of partial is used for generating more than one request.
Step: Setup the collector mock to generate a isPartialResult=true event the first time and a isPartialResult=false the second time
Test success: testPartialResults
Test starting: testPositiveReply
Description: Test the step for updating the checksums can handle COMPLETE operation event.
Test success: testPositiveReply
Starting testcase IntegrityInformationCollectorTest
Test starting: testCollectorGetChecksums
Description: Tests that the collector calls the GetChecksumsClient
Step: Define variables
Step: Setup a GetChecksumsClient for test purpose.
Step: Call the getChecksumsClient on the collector.
Step: Call the getChecksumsClient on the collector four times more.
Test success: testCollectorGetChecksums
Test starting: testCollectorGetFileIDs
Description: Tests that the collector calls the GetFileClient
Step: Define variables
Step: Setup a GetFileIDsClient for test purpose.
Step: Call the getFileIDs on the collector.
Step: Call the getFileIDs on the collector four times more.
Test success: testCollectorGetFileIDs
Test starting: testCollectorHandleChecksumClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Setup variables for the test
Step: Setup a FailingGetChecksumClient for test purpose.
Step: Verify that the collector does not fail, just because the GetChecksumClient does so
02:21:41.079 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: My purpose is to die!
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest$DyingGetChecksumClient.getChecksums(IntegrityInformationCollectorTest.java:151) ~[test-classes/:na]
at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getChecksums(DelegatingIntegrityInformationCollector.java:77) ~[classes/:na]
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleChecksumClientFailures(IntegrityInformationCollectorTest.java:144) [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]
Test success: testCollectorHandleChecksumClientFailures
Test starting: testCollectorHandleGetFileIDsClientFailures
Description: Test that the IntegrityInformationCollector works as a fault-barrier.
Step: Setup variables for the test
Step: Setup a FailingGetChecksumClient for test purpose.
Step: Verify that the collector does not fail, just because the GetChecksumClient does so
02:21:41.083 ERROR o.b.i.c.DelegatingIntegrityInformationCollector - Unexpected failure!
java.lang.RuntimeException: My purpose is to die!
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest$DyingGetFileIDsClient.getFileIDs(IntegrityInformationCollectorTest.java:179) ~[test-classes/:na]
at org.bitrepository.integrityservice.collector.DelegatingIntegrityInformationCollector.getFileIDs(DelegatingIntegrityInformationCollector.java:66) ~[classes/:na]
at org.bitrepository.integrityservice.collector.IntegrityInformationCollectorTest.testCollectorHandleGetFileIDsClientFailures(IntegrityInformationCollectorTest.java:171) [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]
Test success: testCollectorHandleGetFileIDsClientFailures
Starting testcase IntegrityDAOTest
Test starting: initialStateExtractionTest
Description: Tests the initial state of the IntegrityModel. Should not contain any data.
Test success: initialStateExtractionTest
Test starting: instantiationTest
Description: Testing the connection to the integrity database.
Test success: instantiationTest
Test starting: reinitialiseDatabaseTest
Description: Testing the connection to the integrity database.
Step: Setup manually.
Step: Close the connection and create another one.
Test success: reinitialiseDatabaseTest
Test starting: testDeletingEntry
Description: Tests the deletion of an FileID entry from a collection. Checks that it does not effect another collection with a fileID equal to the deleted
Step: Create data
Step: Ensure that the data is present
Step: Delete the entry for the first pillar
Step: Delete the entry for the second pillar
Step: Check that the data in the extra collection is still present
Test success: testDeletingEntry
Test starting: testDeletingNonExistingEntry
Description: Tests the deletion of an nonexisting FileID entry.
Step: Create data
Step: Delete a nonexisting entry
Test success: testDeletingNonExistingEntry
Test starting: testExtractCollectionFileSize
Description: Tests that the accumulated size of the collection can be extracted
Step: Insert test data into database
Step: Check the reported size of the first pillar in the collection
Step: Check the reported size of the second pillar in the collection
Step: Check the reported size of the whole collection
Test success: testExtractCollectionFileSize
Test starting: testExtractingAllKnownFilesForPillars
Description: Tests that known files can be extracted for specific pillars.
Step: Insert two files into database for a pillar
Step: Insert a file to the extra collection for the common pillar
Step: Extract all the existing file ids for the pillar for collection 'TwoPillarCollection'
Step: Extract the single fileID for the extra collection
Step: Extract all the existing file ids for another pillar
Test success: testExtractingAllKnownFilesForPillars
Test starting: testExtractingAllKnownFilesForPillarsLimits
Description: Tests the limits for extracting files for specific pillars.
Step: Insert two files into database for a pillar
Step: Extract with a maximum of 1
Step: Extract with a minimum of 1 and maximum of infinite
Test success: testExtractingAllKnownFilesForPillarsLimits
Test starting: testExtractingAllMissingFilesForPillars
Description: Tests that missing files can be extracted for specific pillars.
Step: Insert two files into database for a pillar and mark them as missing
Step: Check the number of files in collection and on pillars
Step: Extract missing files from the first pillar
Step: Extract missing files from the second pillar
Test success: testExtractingAllMissingFilesForPillars
Test starting: testExtractingAllMissingFilesForPillarsLimits
Description: Tests the limits for extracting missing files for specific pillars.
Step: Insert two files into database for a pillar and set them to missing
Step: Extract with a maximum of 1
Step: Extract with a minimum of 1 and maximum of infinite
Test success: testExtractingAllMissingFilesForPillarsLimits
Test starting: testFindInconsistentChecksum
Description: Testing the localization of inconsistent checksums
Step: Update the database with 2 inconsistent files and one consistent file.
Step: Find the files with inconsistent checksums
Test success: testFindInconsistentChecksum
Test starting: testFindOrphanFiles
Description: Tests the ability to find orphan files.
Step: Create data
Test success: testFindOrphanFiles
Test starting: testGetLatestChecksumDateEntryForCollection
Description: Tests that checksum date entries can be retrieved and manipulated.
Step: Create data
Test success: testGetLatestChecksumDateEntryForCollection
Test starting: testGetLatestFileDateEntryForCollection
Description: Tests that checksum date entries can be retrieved and manipulated.
Step: Create data
Test success: testGetLatestFileDateEntryForCollection
Test starting: testIngestOfChecksumsData
Description: Tests the ingesting of checksums data
Step: Create data
Step: Extract the data
Step: Check that the extra collection is untouched by the ingest
Test success: testIngestOfChecksumsData
Test starting: testIngestOfFileIDsData
Description: Tests the ingesting of file ids data
Step: Create data
Step: Extract the data
Step: Check that the extra collection is untouched by the ingest
Test success: testIngestOfFileIDsData
Test starting: testMissingChecksums
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
Step: Update the database with 1 file, missing its checksum on one pillar.
Step: Finding the files with inconsistent checksums
Test success: testMissingChecksums
Test starting: testMissingChecksumsChecksumNotUpdated
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
Step: Update the database with 1 file, no missing checksums.
Step: Finding the files with inconsistent checksums
Step: Updating the checksum for one pillar, and checking that the other pillars checksum is now missing
Step: Finding the files with inconsistent checksums
Test success: testMissingChecksumsChecksumNotUpdated
Test starting: testNoChecksums
Description: Testing the checksum validation, when no checksums exists.
Step: Update the database with 2 inconsistent files and one consistent file.
Step: Finding the files with inconsistent checksums
Test success: testNoChecksums
Test starting: testOutdatedChecksums
Description: Testing the checksum validation, when only one pillar has a checksum for a file.
Step: Update the database with one file, one pillar having an outdated checksum.
Step: Finding the files with inconsistent checksums
Test success: testOutdatedChecksums
Finished testcase
Finished suite
Finished project
Tests run: 70, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 97.892 sec - in TestSuite
Results :
Tests run: 70, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-integrity-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-integrity-service] in [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/src/main/webapp]
[INFO] Webapp assembled in [279 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integrity-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-integrity-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integrity-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-sonar/bitrepository-integrity-service/target/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integrity-service/1.6-SNAPSHOT/bitrepository-integrity-service-1.6-SNAPSHOT-distribution.tar.gz
[JENKINS] Archiving disabled