Skip to content
Snippets Groups Projects
New look: Off

Separator argument missing 2.6.1

    • Closed Issue created by raducc @raducc

    Target file: SOL003/VNFFaultManagement-API/FaultManagement-APIKeyword.robot

    ${schema} = Catenate ${input} .schema.json

    should be

    ${schema} = Catenate SEPARATOR= ${input} .schema.json

    ~"2.6.1" ~"Plu-2021"

    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • raducc changed title from Separator argument missing ~2.6.1 to Separator argument missing

      changed title from Separator argument missing ~2.6.1 to Separator argument missing

    • raducc changed title from Separator argument missing to Separator argument missing{+ ~"2.6.1"+}

      changed title from Separator argument missing to Separator argument missing{+ ~"2.6.1"+}

    • raducc changed the description

      changed the description

    • raducc changed title from Separator argument missing {-~"2.6.1"-} to Separator argument missing 2.6.1

      changed title from Separator argument missing {-~"2.6.1"-} to Separator argument missing 2.6.1

    • raducc
      raducc @raducc ·
      Author

      art

      Label asignment combo box doesn't show when creating an issue.

    • Giacomo Bernini added 2.6.1 Plu-2021 labels

      added 2.6.1 Plu-2021 labels

    • Elian Kraja
      Elian Kraja @kraja ·
      Maintainer

      Hi @raducc Are you using the 2.6.1-fix-plu branch for your tests? If not, can you please use that?

      The fixes merged yesterday include this fix as well.

    • raducc
      raducc @raducc ·
      Author

      Pulled the branch now.

      There is a new issue related, both alarms.schema.json and Alarms.schema.json are expected to be found (from FaultManagement-APIKeyword.robot) , but only Alarms.schema.json exists. Only one of these files should be expected.

    • Elian Kraja
      Elian Kraja @kraja ·
      Maintainer

      Hi @raducc I see only 2 Keywords using the alarms for the validation.

      The "Check Postcondition VNF fault management alarms Exists" which requires for Alarms (and Alarms.schema.json exists) The other one is the "Check Postcondition VNF fault management individual alarm Exists" which requires alarm (and alarm.schema.json exists as well)

      If I'm missing any other keyword, can you please provide some more details?

    • raducc
      raducc @raducc ·
      Author

      The problematic file was Alarms.robot, FaultManagement-APIKeyword.robot was just a dependency.

      GET information about multiple alarms with fields attribute selector

      GET Alarms Task with fields attribute selector Check HTTP Response Status Code Is 200 Check HTTP Response Body Json Schema Is alarms (alarms.schema.json doesn't exist, but Alarms.schema.json does)

      GET information about multiple alarms with "all_fields" attribute selector

      GET Alarms Task with all_fields attribute selector Check HTTP Response Status Code Is 200 Check HTTP Response Body Json Schema Is alarms (alarms.schema.json doesn't exist, but Alarms.schema.json does)

      Edited by raducc
    • Elian Kraja mentioned in commit 7cd1d95b

      mentioned in commit 7cd1d95b

    • Elian Kraja mentioned in commit d9c4a223

      mentioned in commit d9c4a223

    • Elian Kraja
      Elian Kraja @kraja ·
      Maintainer

      A fix has been pushed for 2.6.1 and 2.7.1 (branches 2.6.1-fix-plu and 2.7.1-fix-plu)

    • Elian Kraja closed

      closed

    • Elian Kraja mentioned in commit 5554547c

      mentioned in commit 5554547c

    Please register or sign in to reply