Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-3975

Unit tests with conflicting output folder, resulting in intermittent build errors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Kohn Release
    • Istanbul Release, Jakarta Release
    • SDC
    • None

      org.openecomp.sdc.asdctool.impl.validator.utils.ReportManagerTest and org.openecomp.sdc.asdctool.impl.validator.tasks.artifacts.ArtifactValidationUtilsTest uses the same output folder for reports, resulting in intermittent errors during the build tests execution, for example: 

      [ERROR] Failures: 
[ERROR]   ArtifactValidationUtilsTest.testValidateArtifactsNotInCassandra:130->lambda$testValidateArtifactsNotInCassandra$1:142 expected: <Artifact testEsInCassandra is in Cassandra> but was: <Task: testTaskName>
[ERROR]   ReportManagerTest.testPrintValidationTaskStatus:125 expected: <-----------------------Validation Tool Results:-------------------------> but was: <>
[ERROR]   ReportManagerTest.testReportValidatorTypeSummary:155 expected: <-----------------------ValidatorExecuter testValidatorNamed Validation Summary-----------------------> but was: <>
[ERROR] Errors: 
[ERROR]   ReportManagerTest.testWriteReportLineToFile:133 » Runtime java.nio.file.NoSuch...

            andre.schmid andre.schmid
            andre.schmid andre.schmid
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: